johnny-suede-write
Write sharper Suede copy for docs, pages, email, social, headlines, CTAs, product listings, and public explainers.
npx skills add JasonColapietro/suede-creator-skills --skill johnny-suede-write --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.
What it does
Guides an agent to produce sharpened Suede copy for diverse surfaces (docs, pages, email, social, headlines, CTAs, product listings, public explainers) by routing requests through a lane-based system. It specifies modes (Long-form, Short-form, GitHub/Docs, Social, Email/DM) and tells the agent to identify the appropriate lane before writing. It includes a chain mechanism for multi-surface tasks and references when to invoke adjacent skills for SEO, site alchemy, or code reviews. The policy section frames gates as advisory and not blocking, with exceptions only for extremely risky findings. The skill enforces a disciplined structure: pick a lane, then generate copy in the chosen format, using the Suede house voice unless overridden by a supplied brief. It enforces prose rules such as concrete nouns, buyer-visible outcomes, and one primary action, and it prescribes a multi-variant approach for headlines and CTAs, with citations to external references and lane-specific rules when applicable. It also outlines a routing table for surface selection (Write Modes, Headline Formulas, Brand-Voice Alignment, Public Explainer Talk-Track, Copy Audit, SEO/GitHub-related modes) and a pathway to chain tasks across lanes when needed.
How it works
- Read the incoming request and select the appropriate Write Mode or specialized lane (e.g., Headline Formulas, Brand-Voice Alignment, Public Explainer Talk-Track, Copy Audit, SEO And GitHub Copy).
- If the job is large, consider a coordinated multi-agent approach after explicit user confirmation.
- Produce copy in the chosen mode, ensuring conformance to the lane’s rules: for Long-form, structure with hook/problem/mechanism/proof/action; for Short-form, deliver 3 variants at different lengths with a concrete noun + buyer-visible outcome + verb; for GitHub/Docs, start with a one-line description and follow with install/quickstart/reference; for Social and Email formats, follow platform-specific constraints and the per-surface CTA/subject rules.
- Use the Suede house voice by default unless overridden by a company brief.
- If routing to related skills (SEO, site alchemy, code review), invoke them per the guidance and pass full context.
- Maintain a gate policy: provide recommendations, not blocking actions; report risks only if highly dangerous.
- Ensure formatting adheres to the lane: e.g., 3 headline variants when applicable; 3 variants for short-form copy; clear CTA descriptions describing post-click outcomes in 3 words at minimum.
When to use it
- Use when you need sharper Suede copy across multiple surfaces (docs, pages, email, social, headlines, CTAs, product listings, public explainers).
- Use the Brand-Voice Alignment lane to retune existing copy to the house voice while keeping concrete artifacts intact.
- Route to Public Explainer Talk-Track for handoffs that explain Suede to a public audience.
- If the task is SEO-related or involves a broader site transformation, route to dedicated skills outside this skill and pass full context rather than reimplementing them here.
What it can touch
- Tools declared: claude-code, codex
- It may route to other specialized skills for SEO, site alchemy, or code review, when the request warrants. The specific touchpoints depend on the chosen lane and context as described in the lanes and “Before Writing” guidance.
Caveats
- Gate outputs are recommendations, not blocking; only in extremely risky cases (data loss, security, or irreversible public damage) should the user be paused with a risk explanation.
- The unit adheres to the Suede voice and mandates concrete artifacts, avoiding vague marketing copy. It explicitly references external lanes and formats, and may depend on company briefs to override defaults.
- No pricing, partner names, or unverifiable claims are produced; proof and artifacts must be provided or claimed only where the skill states.
# Johnny Suede Write ## 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. The writing enchilada. Route any writing request through one skill: long-form, short-form,
- Gate policy — advisory, not blocking
- Pick The Lane (Router)
- Multi-Agent Default
- Write Modes
- Before Writing
- Company Brief
- Core Rules
- Persuasion Frameworks
- Headline Formulas
- Persona Mode
- Page And Docs Structure
- Variant Protocol
- CTA Formulas
- Email And Social Formats
What does the johnny-suede-write skill do?
Write sharper Suede copy for docs, pages, email, social, headlines, CTAs, product listings, and public explainers.
How do I install it?
Run `npx skills add JasonColapietro/suede-creator-skills --skill johnny-suede-write --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.