From c-level-agents
/cs:cmo-review <plan> — Narrative-first interrogation of positioning, ICP, message house, and channel mix.
How this skill is triggered — by the user, by Claude, or both
Slash command
/c-level-agents:cmo-reviewThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
**Command:** `/cs:cmo-review <plan>`
Command: /cs:cmo-review <plan>
The narrative-first strategist pressure-tests positioning before debating tactics.
Name one real person in your ICP. Company, title, what they do daily, what they hate.
What job is the customer hiring this product to do, and what's the alternative they use today?
One sentence: For [ICP], who needs [job], we are [category] that [differentiator] unlike [alternative].
Where does the customer first hear your name — and is it inbound or outbound at this stage?
Per channel: what's CAC, what's payback in months, and is it improving?
If a well-funded competitor copies your messaging tomorrow, what's still yours?
python ../../../skills/cmo-advisor/scripts/marketing_budget_modeler.py
python ../../../skills/cmo-advisor/scripts/growth_model_simulator.py
# CMO Review: <plan>
**Date:** YYYY-MM-DD
## Positioning
One-sentence statement: <here>
## ICP
- Named persona: <name, title, company>
- JTBD: <one sentence in their words>
## Channel Mix
- Primary: <channel> | CAC $X | Payback Ym
- Secondary: <channel> | CAC $X | Payback Ym
## Verdict
🟢 / 🟡 / 🔴
## Next Steps
[3 concrete actions]
/cs:cro-review — pipeline contribution check/cs:cpo-review — product ↔ positioning alignment/cs:decide — log the verdictcs-cmo-advisorcmo-advisor../../../../marketing-skill/Version: 1.0.0
npx claudepluginhub bensitaud-hash/claude-skills --plugin c-level-agentsGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.
18plugins reuse this skill
First indexed Jun 3, 2026
Showing the 6 earliest of 18 plugins