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/extra-info.md
View on GitHub## Extra Info
### Exercises
_If you actually do this, it will turn your copy from good to great._
1. **Word Reduction Exercise**
* Try to strip 50% of the words (while maintaining sense)
* You might not hit 50%, but you'll get better, tighter copy
2. **Read Aloud Test**
* Read the entire copy out loud
* Identifies awkward phrasing immediately
3. **Write Without Adjectives/Adverbs**
* Challenge yourself to create compelling copy using only nouns and verbs
* Forces stronger word choices
4. **Objection Handling**
* List top 5 reasons someone might say "no"
* Write 1-2 sentences directly addressing each objection within the copy
5. **"So What?" Test**
* Take every line and ask "So what?"
* If you can't justify it, cut it
6. **Feature-to-Story Transformation**
* Pick a "boring" feature (e.g., "24/7 customer support")
* Rewrite as mini-story: "At 2AM, your system crashes. You're panicked. Within 3 minutes, our engineer is on the line..."
### Tips
#### Writing Techniques
* Use active voice instead of passive voice
* Explain complex products/services using only common, everyday language
* Write entire emails using sentences of 15 words or fewer
* Hierarchy: Pain points > benefits > features
* Start sentences with "You" more often than "I" or "We"
* Use concrete numbers instead of vague terms ("14 days" not "two weeks")
* Replace jargon with simple explanations
* Write at a 6th-8th grade reading level for maximum comprehension
* Use contractions (it's, you'll) to sound more natural
* Include specific timeframes ("3 minutes" vs "quickly")
#### Advanced Copy Techniques
* **Pattern Interrupts:** Break expectations to maintain attention
* **Future Pacing:** Help them visualize success after using your solution
* **Small Yes:** Make the ask easy to say yes to (a reply, a look at a sample), but still ask for the real offer; a diagnostic question is not a CTA
* **Trojan Horse:** Lead with something they want, deliver what they need
* **The Damaging Admission:** Admit a small flaw to build trust
* **Specificity Sells:** "2,847 companies" beats "thousands of companies" - when the number is real
* **Social Proof Stacking:** Layer different types of proof (numbers + names + testimonials), all of them real
#### Psychological Triggers
* **Loss Aversion:** What they'll miss out on
* **Social Proof:** Others are already doing this
* **Authority:** Credentials and expertise
* **Reciprocity:** Give value first
* **Scarcity:** Only when it is true, with the plain reason ("we take 5 clients a quarter"), never "limited spots"
* **Curiosity Gaps:** Tease information they want
* **Identity:** Align with who they want to be
#### Plain Words
Concrete nouns and verbs beat "power words". Hype adjectives fail the review as AI-tells or spam words (`references/sound-human.md`, `references/spam-words.md`).
### What NOT to Do
Don't follow templates blindly. Most cold email templates online range from horrible to average - they sound like obvious cold emails and get ignored.
#### The Offensive Words Rule
**Never use offensive words.** This is both a spam filter issue and a professionalism issue.
**Important distinction:**
* Don't use offensive words does not mean don't offend people
* You can be polite while being controversial
* You can have controversial opinions that are still agreeable
* Be controversial but professional
**The balance:**
* Controversial but agreeable opinions - good
* Challenging conventional thinking politely - good
* Cursing or crude language - bad
* Personal attacks or insults - bad
* Discriminatory language - bad
**Key principle:** You should be controversial enough to stand out, but agreeable enough that 80-90% of your audience won't be turned off.
**Opening Mistakes:**
* Starting with "I hope this email finds you well"
* "Sorry to bother you"
* "I know you're busy, but..."
* "Just following up"
* Company introductions in first line
* Praise or a reaction instead of a fact ("impressive", "caught my attention", "I came across") - see the first-line pairs in `references/qa.md`
* "Congrats on the raise": a funding round is not a buying event; write to what the money pays for
* Weather, restaurant, school, soccer, or holiday references
**Body Mistakes:**
* Walls of text (paragraphs > 3 lines)
* Multiple ideas in one email
* Feature dumps without benefits
* Generic value props that apply to everyone
* Trying to educate before engaging
* Name-dropping without context
* False urgency or fake deadlines
* Obviously templated sections
**CTA Mistakes:**
* Multiple calls to action
* Vague CTAs ("Let me know your thoughts")
* High-commitment first asks ("Can we schedule a 1-hour demo?")
* Calendar links in first email
* Assumptive CTAs ("When can we meet?")
* A time commitment in the CTA line: it makes them check their calendar before they say yes. Cut it, or move it to the body.
* Wrong: "Can I show you how the audience layering works? 15 minutes."
* Right: "Can I show you how the audience layering works?" or, in the body, "I can walk you through it in about 30 minutes. Worth a call?"
* Keyword-trigger CTAs read as spam:
* Wrong: `Reply "ICP" and I'll map out how we'd approach yours.`
* Right: `Curious how we'd approach your ICP? Just reply and I'll map it out.`
**Tone Mistakes:**
* Being too formal/corporate
* Excessive exclamation points!!!
* ALL CAPS for emphasis
* Too many emojis
* Desperate language ("Please, please reply")
* Guilt-trip closers: a final email that opens with "Last email", "Last one" or "This is my last email to you". Start it with its actual content.
* Arrogant or condescending tone
* Being too casual/unprofessional
**Technical Mistakes:**
* Broken personalization tags {FirstName}
* Multiple links
* Attachments in cold emails
* Images that don't load
* Signatures longer than email body
* Colored text or fancy fonts
* A static body over its word band (Email 1 over 80 words, a follow-up over 60)
**Strategic Mistakes:**
* Sending to generic emails (info@, support@)
* Not researching the company
* No follow-up sequence planned
* Same message to different ICPs
* Pitching competitors' clients with same message
* Blaming the copy for a reply drop before checking how replies were classified
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 |