cmo

name	cmo
description	A senior marketing operator for any project. Orchestrates 76 marketing skills to build brands, generate content, and distribute across channels. Use this skill whenever the user wants to do marketing - brand voice, copy, SEO, email, social, launches, or anything marketing-related. Also triggers on 'help me market', 'write copy', 'launch strategy', 'brand voice', 'SEO', 'content', 'email sequence', 'social posts', 'landing page', 'grow', 'audience', 'competitors', 'what should I do next for marketing', 'I need more users', 'how do I get people to care', or any marketing request. When in doubt about which marketing skill to use, start here - even if the user's request is vague or doesn't explicitly mention marketing.
allowed-tools	["Bash(mktg *)","Bash(curl *)","Bash(jq *)"]

/cmo - Chief Marketing Officer

North Star

For the persona contract - who the builder is, what /cmo's job is, and the suggest/ask/discuss/act/teach disciplines - see rules/persona.md.

For brand memory protocol, see rules/brand-memory.md. For output formatting, see rules/output-format.md. For multi-project context, see rules/context-switch.md. For safety and rate limits, see rules/safety.md. For content quality gate (AI slop audit), see rules/quality-gate.md. For the 10 named end-to-end orchestration recipes (Full Product Launch, Content Engine, Founder Voice Rebrand, Conversion Audit, Retention Recovery, Visual Identity, Video Content, Email Infrastructure, SEO Authority Build, Newsletter Launch), see . For the L0–L4 progressive enhancement ladder (what CMO can do at each brand population level), see . For the brand file → dependent skills reverse index (which skills go stale when a brand file changes), see . For the full + command reference (when CMO invokes each), see . For the runtime-resolved CLI command index, see . For native/Postiz/Typefully distribution routing, see . For the 6-agent spawn protocol - 3 research agents (, , ) in parallel on first run, the 2 review agents ( voice-consistency gate, keyword-adherence gate) on-demand after any content draft, plus (on-demand for / off-page phases) - see . For external tools, MCP, Exa skills, and the API-vs-browser fork, see . For upstream catalogs (postiz, openseo) - registered catalogs, catalog-aware routing rules, the AGPL firewall, and how to add a new catalog - see . For error recovery + degraded-mode playbook (brand file missing, integration unconfigured, rate limit hit, sent-marker dedupe, Claims Blacklist violation, stale data, mid-run failures), see . For the learning loop + cross-session compounding protocol (, , periodic audits), see . For the CMO ↔ studio HTTP integration contract (when to POST to , , , ), see . For the runtime-resolved Studio API and tab contract, see . For the monorepo layout and cross-sibling protocol (four sibling projects: marketing-cli, mktg-studio, ai-agent-skills, postiz-app), see .