adapto-content-createlisted
Install: claude install-skill adaptocms/adapto-cms-agent-skills
# adapto:content-create
The third pipeline step ([content-pipeline.md](../../shared/content-pipeline.md)). It executes the briefs
from the cycle plan into **complete Markdown drafts** — on-brand, with SEO/AEO/GEO metadata, JSON-LD, and
internal links baked into the frontmatter — for you to **review as files** before anything reaches Adapto. It
uses `adapto-writer` to draft and `adapto-editor` to critique, and writes nothing to the CMS.
> **Autonomous-safe** ([studio.md](../../shared/studio.md) §4): local, no CMS writes — an autonomous cycle can
> run this unattended; the cycle parks at the human gate before `adapto:content-upload`.
## When to use
- "Write the planned content", "draft these pieces", "create the articles from the plan".
- After `adapto:content-plan` has produced briefs (status `briefed` in the ledger).
## When not to use
- Choosing what to write → `adapto:content-plan`.
- Pushing approved drafts to Adapto → `adapto:content-upload`.
- Translating existing content → `adapto:translate`.
## Inputs
- The **approved briefs** in the latest `.adapto/plans/<date>-cycle.md` (and their ledger rows).
- **The brain** — `voice.md`, `glossary.md`, `identity.md`, `audience.md`, `inventory.md` (for internal links).
- **The standards** — [seo-standards.md](../../shared/seo-standards.md),
[prose-standards.md](../../shared/prose-standards.md) (the anti-slop rules the editor hard-gates on),
and the frontmatter contract (content-pipeline.md §2).
## Outputs
- A **dated Mark