Skip to content

Ken-Technology/cold-email-skills / email-copywriting

email-copywriting

Verified

Write 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".

references/copywriting-guide.md

View on GitHub
# Writing for the campaign's goal

How the funnel type changes the copy. The block-by-block tactics (formatting, hooks, body, social proof, risk reversal, CTAs, signature, PS) live in `references/email-copywriting-tactics.md`, and the hard rules (lint contract, word bands, CTA, signature) in **email-copywriting** itself; both win on any conflict with this file.

## Build outward from the value proposition

Before choosing a technique, start from the one-sentence offer and expand it:

*   What angles can I put on this?
*   Which case studies support it?
*   Which social proof building blocks can I use?
*   Then compress each one back to its fewest words. Expansion finds the material; compression ships it.

## Funnel types

Read the funnel type from the segment's strategy (its **Goal** and **Funnel Type** lines) and apply the matching technique set, length and tone. One sequence follows one funnel type.

### Click-based

The email earns a click on an asset (a lead magnet, a report, a tool, a video).

- Create a curiosity or information gap that the asset resolves
- Future pace the experience ("You'll see...", "Takes about an hour...")
- Frame the asset as frictionless: no commitment, instant access, self-guided
- Lead with the problem the asset solves, not the product
- Links should feel earned, not pushed. The CTA link is the email's one link, so the signature company name stays plain in that email
- Pattern interrupts to stand out from generic outreach

### Reply-based

The email earns a reply that starts a sales conversation.

- Short and conversational: it should feel like a quick personal message
- Lead with the strongest benefit and the strongest ask from Email 1
- Offer positioning: make it feel irresistible and low-risk, without spam-tier words
- Questions that invite a real answer (yes/no or either/or), never rhetorical
- One idea per email; don't overexplain

### Story-based reply (use sparingly)

The sequence tells one true story, usually the founder's, and earns a reply through it.

- A story arc that builds across emails: each email is a chapter
- Vulnerability and peer-to-peer tone over authority
- May sit at the top of the word bands
- Only when there is a truly compelling, true story to tell. Never invent one

## Where to aim inside the word bands

The bands are the same for every funnel type: Email 1 50-80 static words, follow-ups 30-60, one value-stack email up to ~100. Static words exclude the greeting, AI-variable lines and the signature. The funnel type only says where to aim inside them:

| Funnel type | Email 1 | Follow-ups |
|-------------|---------|------------|
| Click-based | 60-80 static words | 40-60 |
| Reply-based | 50-65 | 30-45 |
| Story-based reply | 70-80 | 45-60 |

The full body (greeting through signature and PS) must still land in the lint's 40-180 words.

## Tone

| Funnel type | Tone | Feels like |
|-------------|------|------------|
| Click-based | Informational, educational | A knowledgeable colleague sharing something useful |
| Reply-based | Casual, human, one-to-one | A quick personal message from someone who gets their problem |
| Story-based reply | Personal, vulnerable, narrative | A founder sharing their story peer-to-peer |

Re-voice the tone in the ICP's own words with the Voice Card (`references/sound-human.md`).
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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall