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/email-and-social-formats.md
View on GitHub# Email and Social Formats
Structures for email sequences and per-platform social posts, including length and opening constraints.
## Email Copy
### Subject Line Formulas
Subject lines win opens on three mechanics: curiosity, self-interest, or specificity. Pick one per subject line.
**Curiosity:**
- "[Specific thing most people miss]"
- "The [category] rule that [counterintuitive result]"
- "What happens when [specific scenario]"
**Self-interest:**
- "[Outcome] in [time] without [obstacle]"
- "How [audience segment] [achieved result]"
- "Your [specific thing] is [state]. Here's the fix."
**Specificity anchor:**
- "[#] [specific mistakes/fields/steps] in your [thing]"
- "[Exact name of thing]: [what it becomes]"
**Avoid:**
- Rhetorical questions ("Are you ready to take your music to the next level?")
- All-caps words
- "Re:" faking a reply thread
- Emojis in subject lines for B2B or technical audiences
**Compliance that changes the copy:** commercial email in the US needs a working unsubscribe link and the sender's physical postal address (CAN-SPAM, https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business). Gmail and Yahoo require one-click unsubscribe (RFC 8058) for bulk senders. Subject lines must not mislead about the content.
### Preview Text
Preview text is a second subject line. Write it to add information, not echo the subject.
- Subject: "12 metadata fields your release is missing"
- Preview: "The ones sync libraries check before they respond."
Keep preview text under 90 characters. If the client truncates at 40, the first 40 characters must stand alone.
### Body Structure
```text
Hook (1-2 sentences): Name the problem or opportunity at the exact moment the reader is experiencing it.
Proof or evidence (2-4 sentences): Specific, not general. One example beats three claims.
Bridge (1 sentence): Connect the proof to the offer.
CTA (1 sentence + link): One action, one link. No secondary options in the primary CTA block.
P.S. (optional): Use for a single secondary offer or a time constraint. Not both.
```
**Unsubscribe-reduction:**
- Match email content to the opt-in promise. Topic or frequency drift is the primary unsubscribe driver.
- Segment before sending. A technical how-to sent to decision-makers who opted in for strategy reads as list mismanagement.
- Run a re-engagement sequence before suppressing inactive subscribers: three emails over 30 days (one value, one direct question, one break-up). Suppress non-openers after the sequence.
## Social Post Formats
### LinkedIn
**Hook line (first 2 lines before "see more"):**
The hook is the post. If the first two lines do not earn the click to expand, the rest does not matter.
- Works: specific observation, counterintuitive claim, single concrete number, named failure mode.
- Fails: vague industry wisdom, rhetorical questions, inspirational openers, "I'm excited to share."
**Post structure:**
```text
[Hook: one specific claim, observation, or question]
[2-4 line break]
[Insight or story: 3-6 short paragraphs, one idea each]
[Takeaway: what the reader does with this]
[CTA: one, low-friction. "What's your experience?" or a link, not both]
```
**Formatting rules:**
- Short paragraphs: 1-2 sentences maximum.
- No bullet lists longer than 5 items.
- One link maximum (in comments if the algo penalizes in-post links).
- 1-2 targeted hashtags maximum, placed at the end.
### X / Twitter
**Standalone tweet:**
```text
[Specific observation or fact] + [one implication or action]
```
Aim for 240 characters even though standard posts allow 280 (Premium accounts allow longer posts, but the feed truncates them). If it reads like a self-contained thought from someone who knows something, it is working.
**Thread opener:**
```text
[Bold specific claim]
[Thread: number + what the reader gets]
"Here's how it works, step by step:"
```
The thread opener must be the strongest tweet in the thread. Do not save the best point for tweet 5.
**Reply to trend or news:**
```text
[Acknowledge the news in 1 sentence]
[Specific take from your vantage point]
[Optional: link to your related resource]
```
### Instagram
**Caption structure by content type:**
Product / feature reveal:
```text
[Name what it does in one sentence (the hook)]
[Why that matters for this specific audience]
[One specific proof point or use case]
[CTA in bio or link sticker]
```
Behind-the-scenes / process:
```text
[Name the specific moment or decision shown]
[What you learned or chose and why]
[Invitation: "What would you have done?"]
```
Testimonial / social proof:
```text
[Lead with the result, not the quote]
[Quote or paraphrase the proof]
[Bridge to your offer]
[CTA]
```
**Caption rules:**
- First line must read as a complete thought. Instagram shows 1-2 lines before "more."
- Hashtags go in the first comment or at the end after a line break. Never inside body copy.
- Five hashtags maximum: Instagram caps posts and Reels at 5 hashtags (enforced since December 2025). Three to five specific tags beat broad ones.
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 |