<p align="center"> <img src="https://raw.githubusercontent.com/MoizIbnYousaf/marketing-cli/main/banner.svg" alt="marketing-cli: agent-native marketing playbook" width="100%"> </p>

<p align="center"> <a href="https://github.com/MoizIbnYousaf/marketing-cli/blob/main/LICENSE"><img src="https://img.shields.io/badge/license-MIT-10b981" alt="MIT License"></a> <img src="https://img.shields.io/badge/skills-64-10b981" alt="64 Skills"> <img src="https://img.shields.io/badge/agents-5-10b981" alt="5 Agents"> <a href="https://www.npmjs.com/package/marketing-cli"><img src="https://img.shields.io/npm/v/marketing-cli?color=10b981" alt="npm"></a> <img src="https://img.shields.io/badge/tests-2,624-10b981" alt="2,624 tests"> <img src="https://img.shields.io/badge/TypeScript-strict-3178c6" alt="TypeScript Strict"> </p>

<p align="center"> <b>One package. One install. CLI for the agent, Studio for the human. 64 skills, 6 research agents, brand memory that compounds.</b> </p>

---

`marketing-cli` ships the playbook, the agents, the runtime schemas, and the `/cmo` routing rules so Claude, Codex, OpenCode, and any shell-capable agent run the same marketing system. Install once. Your project picks up where the last session left off.

## What's in this repo

One npm package, two surfaces. The CLI is the agent surface, the Studio dashboard is the human surface, and `mktg studio` launches the dashboard from inside the same install.

| Surface | What it is | Path | |---|---|---| | `mktg` CLI | 64 skills, 6 agents, brand memory, `/cmo` orchestration | (root) | | Studio dashboard | Local Next.js + Bun API: pulse, signals, brand visualizer, publish queue | [`studio/`](studio/) |

`npm i -g marketing-cli` installs both. The repo uses a bun workspace because Studio is a Next.js app with its own build, but at install time it is one package, one tarball.

## The Problem

You ask your agent for marketing help. It writes generic copy and forgets your audience by tomorrow. The skills it