JasonColapietro/suede-creator-skills / skills/suede-copy
suede-copy
VerifiedUse when asked "rewrite this landing page" or to write, sharpen or retune conversion copy, public explainers and agent-facing docs across surfaces. Suede applies voice, frameworks, labeled variants, answer-first SEO/AEO, evidence boundaries and a 70-point ship score. NOT FOR: a standalone anti-slop pass (use suede-deslop), high-stakes research orchestration (use suede-ship-copy), visual design (use suede-design), or scored SEO audits (use suede-seo-audit).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.3 KB |
| SKILL.md | skill md | 16.3 KB |
| agents/openai.yaml | config | 422 B |
| references/edit-passes.md | markdown | 3.1 KB |
| references/email-and-social-formats.md | markdown | 4.9 KB |
| references/frameworks-and-personas.md | markdown | 2.8 KB |
| references/headline-and-cta-formulas.md | markdown | 3.5 KB |
| references/usage-contract.md | markdown | 864 B |
| references/writing-for-agents.md | markdown | 6.4 KB |
references/headline-and-cta-formulas.md
View on GitHub# Headline and CTA Formulas
Formula banks for headlines and calls to action, with the failure mode each formula tends to produce when overused.
## Headline Formulas
Generate 3 headline candidates minimum for any hero or email subject. Pick the formula that matches the reader's state and the page's job.
| # | Formula | Structure | Example |
|---|---------|-----------|---------|
| 1 | Curiosity gap | [Intriguing partial claim] | "Most release folders fail the first licensing check, usually on the same field." |
| 2 | Number-led specificity | [#] [specific thing] [timeframe/condition] | "12 rights fields missing from your release. Suede finds them in 60 seconds." |
| 3 | How-to outcome | How to [achieve outcome] [without/with condition] | "How to package a release folder that licensing teams can actually use" |
| 4 | Because | [Result] because [mechanism] | "Agents can read your music rights because Suede structures the provenance first." |
| 5 | Specificity anchor | [Exact number or name] + [claim] | "One linter checks all 47 release fields before you pitch." |
| 6 | Before-After | [Before state] → [After state] | "Scattered files and a split sheet in a Google Doc → a machine-readable rights package" |
| 7 | Question (real, not rhetorical) | [Question reader actually asks] | "What does a licensing team check before they sign?" |
| 8 | Objection flip | [Common objection] + [reframe] | "Rights metadata sounds like legal work. It's a 10-minute audit." |
| 9 | If-then conditional | If [specific situation], then [specific outcome] | "If your release goes to a sync library, this is the metadata they'll reject first." |
| 10 | Direct claim with proof hook | [Bold claim] + [verifiable detail] | "Suede reads your folder. You get ISRC, split, and flags before you pitch." |
| 11 | Problem named exactly | [Specific failure mode the reader fears] | "Your ISRC is assigned. Your split sheet is a PDF. Neither is machine-readable." |
| 12 | Authority + specificity | [Who trusts this] + [for what exact task] | "The metadata structure sync licensing teams check on day one." |
Test: swap your product name for a competitor's. If the headline still works, it is not specific enough.
## CTA Formulas
CTAs fail when they describe the button, not the outcome. Every CTA answers: "What happens the moment I click this?"
**Formula A: Verb + immediate result**
[Action verb] + [what they get or see right now]
- "Run the audit. Get your grade in 60 seconds."
- "Fork the skill. Live in your Codex in under a minute."
- "Paste your folder path. See your rights gaps."
**Formula B: Verb + object + benefit**
[Verb] + [specific object] + [value gained]
- "Register a release. Make it readable to licensing agents."
- "Install the skill. Audit any repo from your terminal."
- "Download the schema. Stop building it by hand."
**Formula C: Low-commitment framing** (skeptic / discovery stage)
[Passive discovery verb] + [what they'll see, not what they'll do]
- "See how rights routing works"
- "Read the spec"
- "Open the repo"
- "Watch a 90-second demo"
**Formula D: Stakes-aware framing** (decision-maker)
[Verb] + [outcome in their language]
- "Start the audit before the pitch"
- "Get the split sheet the label actually needs"
- "Ship the release with provenance attached"
**Anti-patterns to cut:**
- "Get started" (started what?)
- "Learn more" (more about what?)
- "Sign up" (for what, exactly?)
- "Try for free" without naming what they're trying
- Any CTA with an exclamation point
The 3-word test: describe what happens after clicking in 3 words. If you cannot, the CTA is too vague.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |