suede-ship-copy
Suede Labs copy-only orchestration DAG: intake with a verbatim capture of the published text, five blind research lenses, an audit of agent-generated facts that closes the set of assertable claims, three angles, a section map with one message per section, disjoint section writers, four-lens review, adversarial refutation, a deslop pass, and a publish-readiness gate. Use for one high-stakes piece strangers will read that has to be true: a landing page, launch post, blog post, email, X thread, docs page, README, ad, or store listing. The audit targets what the agents invent, never what the reque
npx skills add JasonColapietro/suede-creator-skills --skill suede-ship-copy --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Suede Ship Copy The copy side of the canonical Suede DAG. One brief in, one publishable draft out, with about thirty agents in between arranged as a graph rather than a chain. `suede-ship` decomposes work by **file ownership**: two lanes may never write the same file. This decomposes by **message ownership**: two sections may never make the same point, and no section may assert a fact an agent invented. Same graph, different collision rule. ## Whose claims get audited **The audit exists to catch agents inventing things. It never runs on the requester.** A research lens that reports "cold start drops to 40ms" is a machine asserting a number, and it gets opened against its source. The requester saying the same thing in the brief is the person who owns the product telling you a fact about it. Those are not the same input and this workflow never treats them as the same input. Anything the requester supplies — the brief, the `given` list, `mustSay` strings — enters the permitted claim set marked `origin: "user"` and is **exempt at every stage**: - Intake transcribes it. It does not verify, source, soften, or flag it. - The audit never sees it. A research fact that merely restates a gi
- Whose claims get audited
- Gate policy — advisory, not blocking
- Choose this, the single pass, or the fleet
- Parse the invocation
- State the cost before launching
- Launch
- The graph
- Thresholds
- What halts it, and what to do
- While it runs
- When it returns
- Verdict is advisory
- Boundaries
- Iterating
What does the suede-ship-copy skill do?
Suede Labs copy-only orchestration DAG: intake with a verbatim capture of the published text, five blind research lenses, an audit of agent-generated facts that closes the set of assertable claims, three angles, a section map with one message per section, disjoint section writers, four-lens review, adversarial refutation, a deslop pass, and a publish-readiness gate. Use for one high-stakes piece strangers will read that has to be true: a landing page, launch post, blog post, email, X thread, docs page, README, ad, or store listing. The audit targets what the agents invent, never what the reque
How do I install it?
Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-ship-copy --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From JasonColapietro/suede-creator-skills, a repository with 165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.