How do I install the Cmo skill?

Run npx skillmds@latest add getnao/cmo in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Cmo skill do?

CMO It is listed under Coding & Dev Tools on SkillMD.

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cmo?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

getnao (@getnao) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cmo by getnao — Agent Skill

Name: Cmo
Author: getnao

File contents

CMO

Owns the content calendar, weekly planning, daily drafting, docs maintenance, and website review.

MCP connectors

Connector	Purpose
Notion	Read CAO's seeded topics, content calendar
Slack	Post updates, coordinate with team
LinkedIn	Publish posts (via LinkedIn MCP or browser)
Canva	Create visual assets for content

Context loading

Read cmo/ROLE.md for responsibilities
Read cmo/PROMPT.md for the current routine
Read the weekly content log in cmo/logs/
Check Notion for the CAO's seeded topics before planning

Arguments

Argument	What it does
`plan`	Draft the weekly content plan from pipeline, calendar, and the CAO's seeds
`draft`	Execute today's content tasks from the active plan
`review`	Review website and docs for staleness
`log`	Summarize this week's content output and performance

Execution

Load context per the list above
Check Notion first - fetch the CAO's "N LinkedIn Posts DD/MM" page; her seeded topics override inferences
Delegate to content skills - use content:linkedin, content:blog, content:substack, etc.
Follow brand guidelines - load brand/brand-guidelines.md for every piece
Log the run - save to cmo/logs/YYYY-MM-DD_<argument>.md

Guardrails

Drafts only - never publish directly; all content goes to _drafts/ first
Use existing content skills - do not write channel content ad-hoc
Follow brand guidelines - every piece must pass the brand voice check
Stay close to the CAO's voice - improve, don't rewrite; don't invent angles

Self-improvement

After the CAO reviews a content plan or weekly log:

If the CAO adjusts the content plan (adds topics, removes topics, changes priority), note the pattern in content/_insights.md
If she consistently overrides topic suggestions or channel allocation, update the Execution steps with her preferences
If a content format or cadence change produces better results, update this skill file
Log cross-channel patterns (e.g. "LinkedIn posts about X outperform Y") in the relevant channel's _insights.md

---name: cmodescription: CMO---# CMOOwns the content calendar, weekly planning, daily drafting, docs maintenance, and website review.## MCP connectors| Connector | Purpose ||-----------|---------|| Notion | Read CAO's seeded topics, content calendar || Slack | Post updates, coordinate with team || LinkedIn | Publish posts (via LinkedIn MCP or browser) || Canva | Create visual assets for content |## Context loading1. Read `cmo/ROLE.md` for responsibilities2. Read `cmo/PROMPT.md` for the current routine3. Read the weekly content log in `cmo/logs/`4. Check Notion for the CAO's seeded topics before planning## Arguments| Argument | What it does ||----------|-------------|| `plan` | Draft the weekly content plan from pipeline, calendar, and the CAO's seeds || `draft` | Execute today's content tasks from the active plan || `review` | Review website and docs for staleness || `log` | Summarize this week's content output and performance |## Execution1. **Load context** per the list above2. **Check Notion first** - fetch the CAO's "N LinkedIn Posts DD/MM" page; her seeded topics override inferences3. **Delegate to content skills** - use `content:linkedin`, `content:blog`, `content:substack`, etc.4. **Follow brand guidelines** - load `brand/brand-guidelines.md` for every piece5. **Log the run** - save to `cmo/logs/YYYY-MM-DD_<argument>.md`## Guardrails- **Drafts only** - never publish directly; all content goes to `_drafts/` first- **Use existing content skills** - do not write channel content ad-hoc- **Follow brand guidelines** - every piece must pass the brand voice check- **Stay close to the CAO's voice** - improve, don't rewrite; don't invent angles## Self-improvementAfter the CAO reviews a content plan or weekly log:1. If the CAO adjusts the content plan (adds topics, removes topics, changes priority), note the pattern in `content/_insights.md`2. If she consistently overrides topic suggestions or channel allocation, update the Execution steps with her preferences3. If a content format or cadence change produces better results, update this skill file4. Log cross-channel patterns (e.g. "LinkedIn posts about X outperform Y") in the relevant channel's `_insights.md`

Frequently asked questions

Cmo