Ken-Technology/cold-email-skills / email-copywriting
email-copywriting
VerifiedWrite the cold emails for a segment: subject lines, hooks, body, CTAs, signatures and personalization placeholders, following hard copy rules. Use when drafting or rewriting a cold-email sequence. Triggers on "write the emails", "draft the sequence", "rewrite this cold email".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 29.2 KB |
| references/ai-variables-guide.md | markdown | 7.7 KB |
| references/copy-craft.md | markdown | 4.4 KB |
| references/copywriting-guide.md | markdown | 3.2 KB |
| references/email-copywriting-tactics.md | markdown | 17.0 KB |
| references/extra-info.md | markdown | 6.3 KB |
| references/gold-standard.md | markdown | 8.3 KB |
| references/lead-variables.md | markdown | 8.7 KB |
| references/qa.md | markdown | 10.4 KB |
| references/sound-human.md | markdown | 10.1 KB |
| references/spam-words.md | markdown | 8.3 KB |
references/copy-craft.md
View on GitHub# Copy craft
Condensed writing rules for cold email, subject lines, lead magnets, and any client-facing copy. They sit on top of the voice rules in `references/sound-human.md` and the word bands and lint contract in **email-copywriting**. Where they conflict with a hard email constraint (Email 1 at most 80 static words, follow-ups 30-60, subject under 6 words, one CTA, one link), the hard constraint wins. Compress the craft into it.
## Core principle
Write like you're explaining it to a smart, skeptical friend. Back every claim with specifics. Make the transformation clear.
The fundamentals haven't changed. The packaging has to sound like a person wrote it.
## Headlines and subject lines
Headlines do most of the work. Formula: action verb + specific outcome + timeframe or contrast.
Shape: "Ship your startup in days, not weeks."
Write at least five before picking. One will outpull the others.
Cold-email subjects still follow the short-subject rule (under 6 words, ideally 3-4, lowercase except names). Fit the formula inside that length: a verb, a concrete outcome, a contrast or timeframe when it fits. When the subject is `{{Subject Line}}`, keep the existing short-subject prompt. Shape the angle with a verb and a concrete outcome. Do not replace the subject template with a long headline.
## Opening lines
An opening line has one job: get them to read the second sentence.
Lead with one of these:
- a direct challenge
- a scene-setting story
- a specific result
- a confession
Never open with "In today's fast-paced world" or anything in that family ("in today's competitive landscape", "in a world where...").
## Start with them
Outreach dies when every sentence starts with "I."
"I wanted to..."
"I think..."
"I was reaching out..."
That is autobiography. Buyers respond to relevance.
After the draft, go line by line. Ask: can this sentence start with them, their team, their initiative, or a relevant observation? If not, rewrite it.
- "I think..." becomes a specific observation about them. "What I'm seeing in your industry..." only counts when the next words are about this reader. A generic industry line fails the empty-observation rule in `sound-human.md`.
- "I wanted to share..." becomes "Noticed your team is doing X..."
The offer line may still start with "I" or "we" when it names what you will do for them ("I'll build the list, you approve it"). One of those is enough. A body where most sentences start with "I" fails.
## Pain quantification
Vague problems feel unsolvable. Do the math.
"4 hrs for emails + 6 hrs for landing page = 22+ hours of headaches" beats "launching is hard."
Use the prospect's actual numbers when you have them. Invented math is a false claim. If you don't have numbers, use a concrete scene instead of a vague adjective.
## The so-what chain
This is not the "So what?" cut test. That one deletes a line you can't justify. This one finds the line worth keeping.
Most copy dies one level too high. Go three levels deep until you hit something emotional or financial.
"Fast database" → "queries load fast" → "users don't bounce" → "you stop waking up stressed about churn."
Write from the bottom. The email leads with the last link, not the feature.
## Open loops
Tease without revealing. "But that's not even the best part." The next beat has to pay it off. A tease with no payoff is a trick.
On a long page (lead magnet, landing page), use 2-4 loops, no more.
In a cold email, one loop at most, and only if the next sentence or the next email pays it off. A short note with several teases reads like a funnel, not a person.
## Rhythm
Real writing alternates punchy short sentences with longer ones that breathe. Same-length paragraphs read as AI. Same rule as `sound-human.md`: jagged on purpose, not one-word lines stacked into fake punch.
## Testimonials and proof lines
Shape: before state + action + specific outcome + timeframe + emotion.
"I wanna cry" beats "Great product."
A proof line that is only an adjective ("huge win", "game-changer") fails this test. If you don't have the before, the action, the number, and the timeframe, don't fake them. Use a thinner true line or cut the proof.
## Avoid
Never use: "delve", "utilize", "game-changer", "leverage" as a verb, an em dash, a spaced dash standing in for an em dash in prose (the signature line's ` - ` is fine), or anything that starts with "Let's dive in."
Read it out loud. If it sounds like a textbook, rewrite it.
Full banned lexicon: `sound-human.md`.
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: 194k | 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: 194k | 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: 194k | Updated | Claude CodeCodex | Verified | Install |