getnao/sylph / .claude/skills/cmo
cmo
Verified| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 2.2 KB |
SKILL.md
View on GitHub# 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`
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |