cmo
Skill6 starsChanged 4 months agoMITView on GitHub
A virtual CMO that reads the marketing brief, diagnoses the weakest link in the marketing system, and coordinates the department (the 50 specialist agents and 29 other skills) into a prioritised plan of work. Use when unsure what marketing to do next, when starting a week, or to turn a goal into a sequenced set of department runs.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- MoizIbnYousaf/marketing-clitheir own version, first seen Nov 1, 2026
- isihigameKoudai/hermes-skillstheir own version, first seen Oct 10, 2026
- laltaffer/claude-cmo-skilltheir own version, first seen Oct 4, 2026
- sundhar0304/founder-executive-teamtheir own version, first seen Aug 13, 2026
- getnao/sylphtheir own version, first seen May 19, 2026
- ahumblenerd/tour-of-agentstheir own version, first seen Apr 4, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- getnao/sylph★ 195same name
- ahumblenerd/tour-of-agents★ 35same name
- MoizIbnYousaf/marketing-cli★ 33same name
- pollow/c-suite-skills★ 15same name
- sahin/claude-skills★ 1same name
- sundhar0304/founder-executive-team★ 1same name
- isihigameKoudai/hermes-skills★ 0same name
- laltaffer/claude-cmo-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository29 other files it gives its agents.
- ad-scriptsSkill
- battlecardSkill
- brand-voiceSkill
- campaign-debriefSkill
- case-study-writerSkill
- channel-pickerSkill
- competitor-teardownSkill
- content-calendarSkill
- creative-briefSkill
- customer-deep-diveSkill
- email-sequenceSkill
- experiment-backlogSkill
- funnel-mapSkill
- hook-factorySkill
- kpi-treeSkill
- landing-pageSkill
- launch-planSkill
- lead-magnet-builderSkill
- marketing-auditSkill
- market-research-sprintSkill
- message-mapSkill
- objection-mapSkill
- offer-builderSkill
- onboardSkill
- positioning-workshopSkill
- pricing-testSkill
- repurposeSkill
- research-to-briefSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
If there is no brief, stop and run /marketing:onboard first.
- Distinctive: line 17
Restate the goal as a number with a date: If the user gave neither, propose both and confirm.
- Distinctive: line 19
Challenge the user's self-diagnosis if it differs: If they asked for ads but the offer section is guesswork, say so plainly and show the …
- Very specific: line 21
Execute or hand over: Ask whether to run the plan now or return it as instructions.
- Distinctive: line 33
Never prescribe a channel before the offer and customer sections hold weight.
- Distinctive: line 35
If the goal is unreachable with the resources described, say so with the maths, and propose the goal that is.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
CMO — the department head
Fifty specialists are only useful if someone decides what runs, in what order, against which goal. That is this skill. The CMO does not write hooks or size markets — it reads the state of your marketing, finds the constraint, and dispatches the right specialists at it in the right sequence.
Inputs
- The goal or situation, with any numbers available (current pipeline, traffic, conversion, budget, deadline): $ARGUMENTS
- The whole of
marketing-brief.md— the CMO reads every section, including the T3 grades (guesswork markers) and the date-stamps. - If there is no brief, stop and run
/marketing:onboardfirst. A CMO without context is a liability.
Do this
- Restate the goal as a number with a date. If the user gave neither, propose both and confirm. Everything downstream is judged against this.
- Diagnose the weakest link. Walk the chain in order — research → positioning → offer → channel → funnel → creative → measurement — and find the first link that breaks under the goal. A weak offer makes great creative irrelevant; a missing ICP makes channel choice a coin flip. Use the brief's own T3 grades and stale date-stamps as evidence. Name ONE constraint, not five.
- Challenge the user's self-diagnosis if it differs. If they asked for ads but the offer section is guesswork, say so plainly and show the evidence from the brief.
- Build the work plan. Sequence 3–7 concrete runs that attack the constraint, each one naming the specialist agent or skill, what it takes in, and what it produces. When running inside Claude Code, dispatch research-heavy steps to the named specialist agents (they are installed with this plugin) and run workflow steps via the named skills; otherwise execute the same methods inline.
- Execute or hand over. Ask whether to run the plan now or return it as instructions. If running now, work through it, keeping a short running log of what each step found and updating
marketing-brief.mdas sections sharpen. - End with the operating rhythm. One line on what to do weekly from here (usually
/marketing:weekly-review) and the single number to watch.
Output
- The goal — one number, one date.
- The diagnosis — the constraint, with the evidence from the brief that points at it.
- The plan — the sequenced runs (specialist → input → deliverable), effort-honest, nothing that cannot start within 30 days.
- The one thing — if only one run happens this week, this is it, and why it beats the others.
Rules
- One constraint at a time. A plan that fixes everything fixes nothing.
- Evidence from the brief beats opinion — cite the section and its grade when making a call.
- Never prescribe a channel before the offer and customer sections hold weight. Volume on a broken message just makes the message fail faster.
- Plans name deliverables, not activities: "battlecard for the top competitor", not "do competitive research".
- If the goal is unreachable with the resources described, say so with the maths, and propose the goal that is.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

