$npx -y skills add JasonColapietro/suede-creator-skills --skill suede-copyWrite conversion copy that earns the click: landing sections, email, microcopy, buttons, headlines, CTAs, variants, and anti-slop edits.
| 1 | # Suede Copy |
| 2 | |
| 3 | ## Gate policy — advisory, not blocking |
| 4 | |
| 5 | Every claim-verification step, check, quality gate, and ship verdict in this |
| 6 | skill is a **recommendation to the user, not a control on the agent**. This |
| 7 | policy governs every gate, check, verdict, and "do not ship / publish / |
| 8 | proceed" line elsewhere in this skill: |
| 9 | |
| 10 | - Run every check and report the results honestly. Verdicts (`ship`, |
| 11 | `ship-with-caveats`, `hold`, letter grades, BLOCKED or OPEN items) are |
| 12 | advice attached to the work, not orders that change it. |
| 13 | - Never block, delay, skip, rewrite, or refuse the action the user asked for |
| 14 | because a check failed or a gate said hold. Complete the requested action |
| 15 | as asked, and deliver the gate output alongside it as a clearly labeled |
| 16 | recommendation. |
| 17 | - A failed gate changes what you report, never what you do. |
| 18 | - Single exception: if a finding is extremely risky — data loss, security or |
| 19 | credential exposure, legal or rights violations, payment mistakes, or |
| 20 | irreversible public damage — pause, tell the user exactly what the risk is |
| 21 | and what the options are, and let them pick. Their choice is final. |
| 22 | |
| 23 | |
| 24 | ## When to use this skill instead of related skills |
| 25 | - **suede-copy** (this skill): standalone conversion email, landing page copy, CTAs, microcopy, button labels |
| 26 | - **johnny-suede-write**: full writing stack (copy + SEO + AI Engine Optimization) |
| 27 | - Multi-email campaign sequences and campaign performance reporting: (private Suede Labs companion, not in this pack: suede-growth) |
| 28 | - Post-production pass to strip AI writing patterns from already-written copy: (private Suede Labs companion, not in this pack: suede-deslop) |
| 29 | |
| 30 | Write conversion copy, page copy, GitHub docs, email, and social posts that are specific, proof-backed, and free of AI boilerplate. Default voice: Suede. Supply a company brief to override everything. |
| 31 | |
| 32 | **Core principle:** every claim is verifiable or it gets cut, and nothing ships below its score threshold. |
| 33 | |
| 34 | ## Company Brief |
| 35 | |
| 36 | Supply a brief and all copy, voice, and claim logic applies to your company. Use natural language or this form: |
| 37 | |
| 38 | ```text |
| 39 | Company: |
| 40 | Product or offer: |
| 41 | Audience: |
| 42 | Voice: |
| 43 | Terms to use: |
| 44 | Terms to avoid: |
| 45 | Proof: |
| 46 | Allowed claims: |
| 47 | Forbidden claims: |
| 48 | Primary CTA: |
| 49 | ``` |
| 50 | |
| 51 | ## Before Writing |
| 52 | |
| 53 | Read any available context files before asking questions: `PRODUCT.md`, `README.md`, `AGENTS.md`, `AI_HANDOFF.md`, `DESIGN.md`, product marketing or brand notes, task-specific docs. |
| 54 | |
| 55 | If context is missing after reading, ask only for what blocks accurate copy: |
| 56 | |
| 57 | - page or doc type |
| 58 | - primary reader |
| 59 | - one action the reader should take |
| 60 | - product or skill being offered |
| 61 | - proof that is safe to claim |
| 62 | - claims, pricing, partners, or metrics that are not approved |
| 63 | - traffic source or publication surface |
| 64 | |
| 65 | ## Core Rules |
| 66 | |
| 67 | Name the outcome, not the feature. |
| 68 | - Weak: "Suede supports multiple metadata formats." |
| 69 | - Strong: "Export ISRC, ISWC, and split data in one command." |
| 70 | |
| 71 | Write buttons as actions with a result. |
| 72 | - Weak: "Learn more" |
| 73 | - Strong: "Read how rights routing works" |
| 74 | - Weak: "Get started" |
| 75 | - Strong: "Register your first release" |
| 76 | |
| 77 | Replace vague claims with artifacts. |
| 78 | - Weak: "Suede makes rights management easy." |
| 79 | - Strong: "Paste your folder path. Suede outputs your ISRC, split sheet, and licensing flags in under 10 seconds." |
| 80 | |
| 81 | No invented proof. Do not write stats, testimonials, partner names, pricing, or legal clearance that has not been confirmed. If proof is unavailable, write around the gap or flag it for the human to supply. |
| 82 | |
| 83 | No em dashes. No exclamation points. No rhetorical questions that answer themselves. |
| 84 | |
| 85 | ## Persuasion Frameworks |
| 86 | |
| 87 | Match framework to surface and reader temperature: |
| 88 | |
| 89 | - Reader arrives cold, no prior awareness: **AIDA** (Awareness → Interest → Desire → Action). Lead with the category problem, build specificity, make the outcome concrete, drive a single action. |
| 90 | - Reader has a named pain and is actively searching: **PAS** (Problem → Agitate → Solution). Name the problem, surface the cost of inaction, position the product as the specific relief. |
| 91 | - Hero section, social post, launch email: **Before-After-Bridge**. Describe life before the product, paint life after, bridge with the product as the mechanism. |
| 92 | - Product page, onboarding, in-app copy: **JTBD**. Write around what the reader is trying to accomplish: the job they hired the product to do, not around features. |
| 93 | - Homepage, About, long-form brand page: **StoryBrand 7-Part**. Character (customer) → Problem → Guide (your brand) → Plan → CTA → Avoid failure → Achieve success. |
| 94 | |
| 95 | State the chosen framework and reader temperature before drafting. If multiple frameworks could apply, pick one and note why. |
| 96 | |
| 97 | ## Headline Formulas |
| 98 | |
| 99 | 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. |
| 100 | |
| 101 | | # | Formula | |