---
name: CMO
slug: cmo
category: Writing
description: CMO owns the content calendar, weekly planning, daily drafting, docs maintenance, and website review. Use it to plan, draft, review, and log content work with drafts routed through existing content skills.
github: "https://github.com/getnao/sylph/tree/main/.claude/skills/cmo"
language: JavaScript
stars: 195
forks: 57
install: "npx degit https://github.com/getnao/sylph/tree/main/.claude/skills/cmo ~/.claude/skills/cmo"
installs_to: ~/.claude/skills/cmo
source_path: .claude/skills/cmo/SKILL.md
collection_size: 25
category_size: 1227
collection_url: "https://dirskills.com/collections/getnao/sylph"
added: 2026-09-05T05:31:13.328Z
last_synced: 2026-09-05T05:31:13.328Z
canonical_url: "https://dirskills.com/skills/cmo"
---

# CMO

CMO owns the content calendar, weekly planning, daily drafting, docs maintenance, and website review. Use it to plan, draft, review, and log content work with drafts routed through existing content skills.

**Install:**

```bash
npx degit https://github.com/getnao/sylph/tree/main/.claude/skills/cmo ~/.claude/skills/cmo
```

## README

# 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

1. Read `cmo/ROLE.md` for responsibilities
2. Read `cmo/PROMPT.md` for the current routine
3. 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 |

## Execution

1. **Load context** per the list above
2. **Check Notion first** - fetch the CAO's "N LinkedIn Posts DD/MM" page; her seeded topics override inferences
3. **Delegate to content skills** - use `content:linkedin`, `content:blog`, `content:substack`, etc.
4. **Follow brand guidelines** - load `brand/brand-guidelines.md` for every piece
5. **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:

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 preferences
3. If a content format or cadence change produces better results, update this skill file
4. Log cross-channel patterns (e.g. "LinkedIn posts about X outperform Y") in the relevant channel's `_insights.md`