Six roles, one record, and every asset argues something different.
The default failure of an AI content team is six posts repeating one sentence. This pipeline gives six roles written contracts, passes one inspectable campaign record between them, and ends at a distribution stage where each asset has to carry its own argument rather than a shorter draft of the flagship. Use it when content agents come back generic, duplicated, or unsourced, or when one piece has to carry a week.
View skill folder Install options
When to reach for it
The user wants an AI content team or editorial pipeline, their content agents return generic or duplicated work, or one idea has to fill several surfaces without every asset making the same argument.
What's inside
- Step 1 — Put the campaign in a file, not a conversation
- Step 2 — Give each role one decision to own
- Step 3 — Gate every handoff
- Step 4 — Distribute by argument, not by format
- Step 5 — Keep the human at the editorial boundary
- Step 6 — Make performance rewrite the playbooks
- Running it on the host you have
- Start smaller than six roles
- Anti-patterns
- Banned vocabulary
- Boundaries
- Routing
Example prompt
Use $suede-newsroom on [target]. Move the idea through scout, research, angle, and flagship, then build a distribution set where every asset carries its own entryway and passes the collision gate. Hand off through the campaign record and stop at the human approval boundary.Reference material
Loaded on demand, not up front:
Credit
The operating model behind this skill is adapted from a public write-up by @VibeMarketer_. Attribution and adaptation notes are in NOTICE.md.
Install this skill
It ships inside the Suede Creator Skills pack, so one install brings the whole pack and this skill with it. Claude Code takes two commands the first time and one after that; Codex installs the same pack natively.
$ /plugin marketplace add JasonColapietro/suede-creator-skills $ /plugin install suede-skills@suede
$ codex plugin add suede-skills@suede-codex
Cursor, Copilot, and Windsurf install through the skills CLI. Every path is on the install page, and every folder is readable first on GitHub.