suede-ship-copy

Files (4)

• CARD.md
• SKILL.md
• openai.yaml · agents/
• suede-ship-copy.js · workflows/

SKILL.md (first lines)

# Suede AI Ship Copy Skills

## Compatibility

Requires a workflow host supporting Workflow, phase, subagents, and local draft files; web access supplies live research. A plain chat host must report unavailable orchestration instead of claiming a completed run.

For a concrete input, expected handoff, and failure check, read
[the worked handoff](references/worked-handoff.md).

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-graph-flo-xr` 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.

## Model selection: Fable capped at 4 without asking

Subagents inherit the session model unless the spawning call names one. Nothing in
this skill picks a model, so every agent it fans out lands on whatever the session
happens to be set to. That is how a run sized against one allocation gets billed to
another without anyone choosing it.

**Up to 4 concurrent Fable subagents are allowed without an explicit Fable
instruction. Beyond that, Fable must be specified**: every range this skill offers
(30 at the narrowest) is far beyond 4, so its fan-out never runs on Fable unless the
user named Fable for this run. An inherited session model is not a
specification: "the session was already on it" is not the user asking. Absent an
explicit Fable instruction, do one of two things before launching: name a different
model on the agent calls, or state plainly that the run will bill to the Fable
allocation and get an answer. Silence is not consent to spend it.

## Whose claims get audited

Before intake or any research, review, or gate phase, read
[the complete claim-origin policy](references/claim-origin-policy.md).
It is required for every run: preserve requester givens, audit agent-generated
claims, keep protected strings byte-exact, and retain discarded findings in the
evidence record. The reference preserves the full filtering, proportional-match,
and output-path rules; follow them before launching the bundled workflow.

Invoke `skills/suede-ship-copy/workflows/suede-ship-copy.js` through the host's
`Workflow` API as shown below.

## Gate policy: advisory, not blocking

Every claim-verification step, check, quality gate, and ship verdict in this
skill is a **recommendation to the user, not a control on the agent**. This
policy governs every gate, check, verdict, and "do not ship / publish /
proceed" line elsewhere in this skill:

- Run every check and report the results honestly. Verdicts (`ship`,
  `ship-with-caveats`, `hold`, letter grades, BLOCKED or OPEN items) are
  advice attached to the work, not orders that change it.
- Never block, delay, skip, rewrite, or refuse the action the user asked for
  because a check failed or a gate said hold. Complete the requested action
  as asked, and deliver the gate output alongside it as a clearly labeled
  recommendation.
- A failed gate changes what you report, never what you do.
- Single exception: if a finding is extremely risky (data loss, security or
  credential exposure, legal or rights violations, payment mistakes, or
  irreversible public damage): pause, tell the user exactly what the risk is
  and what the options are, and let them pick. Their choice is final.

**That exception never applies to a claim the requester supplied.** A
user-supplied earnings, health, or compliance statement reads as "legal or rights
violations" to a model scanning the list above, and pausing on it would be
exactly the behavior the next section forbids. The exception covers findings
about agent-generated content and about the live environment. A given is not a
finding.

## What it costs

This is the expensive instrument: about thirty agents (26 floor, ~31 typical,
42 ceiling), research-heavy and front-loaded, billed to the Claude limit. When the
work is genuinely parallel and shallow instead, brute force beats surgery: the
Routing section at the end says where each of those jobs goes.

## Parse the invocation

The argument is free-form. Extract:

- **piece**: required. What to write, in the user's own words, kept verbatim.
  Do not compress it into a slogan; the planner decomposes it into sections and
  the detail is what makes sections separable.
- **surface**: required. Where it goes: landing page, email, email sequence, X
  thread, blog post, README, docs page, ad, app store listing, press note. The
  surface sets hard character limits, so a wrong guess is a rewrite.
- **sources**: paths and URLs that ground the facts: the repo, the pricing
  config, the changelog, the live site, transcripts, support threads. Optional,
  and the intake agent finds them otherwise, but a supplied source list is the
  difference between a claim audit that has something to check and one that
  deletes half the draft.
- **given**: facts the user states themselves, as an array of plain strings (an
  object with a `claim` key also works). These are established:
  they go straight into the permitted set, skip the audit, and no phase may
  question them. Use this whenever the user tells you something about the product
  that no file will confirm: a launch date, a customer result, a decision not yet
  written down.
- **audience**: who reads it. Optional; intake infers it and says what it inferred.
- **liveUrl**: the published surface, if one exists. The baseline capture and the
  drift check both use it.
- **outDir**: where the draft lands. Defaults to a `.suede-copy/<slug>/`
  directory. Must be a draft location: an output path pointing at already
  published copy is a halt.
- **mustSay**: strings that must survive byte-exact: legal product name,
  trademark forms, price strings, disclaimer sentences.
- **wordBudget**: total words. Optional; the surface law supplies limits per field.
- **houseStyle**: optional `{ guidance, emDashes }`. `guidance` is the supplied
  author/company voice brief; `emDashes` is `allow` or `avoid` (Suede default).
  Translate an explicit punctuation preference into this field so prompts and
  deterministic checks agree. Protected source spans remain byte-exact either way.
- **agentBudget**: `light`, `standard`, or `deep`. Required, and you must ask the
  user rather than pick it (see below). Omitting it defaults to `standard`.

If **piece** or **surface** is missing, ask. Do not invent a brief for something
a public audience will read.

From JasonColapietro/suede-creator-skills, MIT.

More from JasonColapietro/suede-creator-skills