JasonColapietro/suede-creator-skills / skills/suede-cold-email
suede-cold-email
VerifiedUse when asked "write a cold email" or to repair B2B outbound to qualified prospects. Suede produces sourced personalization, short subjects, bodies under 75 words, one ask and bounded follow-ups, with current sender-rule checks. NOT FOR: prospect qualification (use suede-prospecting), opted-in lifecycle email (use suede-emails), or broader sales collateral (use suede-sales-enablement).
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.4 KB |
| SKILL.md | skill md | 9.9 KB |
| agents/openai.yaml | config | 558 B |
| evals/evals.json | config | 6.9 KB |
| references/benchmarks.md | markdown | 6.1 KB |
| references/follow-up-sequences.md | markdown | 2.6 KB |
| references/frameworks.md | markdown | 3.8 KB |
| references/personalization.md | markdown | 3.0 KB |
| references/subject-lines.md | markdown | 1.8 KB |
| references/usage-contract.md | markdown | 889 B |
references/subject-lines.md
View on GitHub# Subject Lines
A cold subject line has one job: get the email opened by the right person
without looking like a pitch. Short, plain, and internal-sounding wins.
## Defaults
- **2 to 4 words.** Mobile clients truncate around 30 to 35 characters.
- **Lowercase.** It reads like a note from a colleague, not a campaign.
- **About their world.** A topic, project, or trigger they would recognize:
"reply rates", "hiring ops", "q3 forecast", "new patients", "second location".
- **No first name.** A name in the subject signals a mail merge.
- **No pitch, no numbers, no urgency.** Those patterns read as marketing and
raise spam-filter risk.
## Questions
Only when the question names a specific problem the reader has ("onboarding
backlog?"). Generic questions ("quick question?", "15 minutes?") are filler and
read as automation. Default to a short statement.
## Executives
Senior buyers triage hundreds of emails a day. Go shorter and quieter: the name
of their initiative, a project, or a two-word topic. Nothing that sounds like a
sale.
## Avoid
| Pattern | Why |
|---|---|
| "increase", "boost", "ROI", "revenue" | Reads as a pitch before it is opened |
| "ASAP", "urgent", "last chance" | Fake urgency; spam-filter risk |
| "!!!", "??", ALL CAPS | Looks like spam |
| Percentages and big numbers | Reads as an ad claim |
| Emojis | Off-tone for B2B cold outreach |
| Product name in the subject | Signals a pitch |
| Fake "Re:" or "Fwd:" | Deceptive; destroys trust and can violate CAN-SPAM's honest-header rule |
| Empty subject | Gets opens from curiosity and replies from nobody |
## Testing
Test subject lines on reply rate, not open rate. Open tracking is distorted by
privacy proxies, and the tracking pixel itself can hurt deliverability. Change
one variable per test and keep the body constant.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |