cold-email-copywriting
Skill2 starsChanged 4 months agoMITView on GitHub
Writes and reviews cold email copy — no fluff, hook-bridge-CTA structure, mobile-optimized length, curiosity-driven tone, low-friction CTAs. Use when drafting, editing, or critiquing cold emails, outbound messaging, sales emails, or prospecting copy.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- manypicom/sales-skillstheir own version, first seen Nov 15, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- manypicom/sales-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- cold-email-deliverabilitySkill
- gtm-outreachSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 54
Every cold email follows four parts.
- Distinctive: line 86
Prefer CTAs they can answer with "Sure" or "Yes, please":
- Distinctive: line 99
Always give an easy out — permission-based, "by the way" energy, not a calendar demand.
- Distinctive: line 103
Only when the prospect would immediately recognize urgent need.
- Distinctive: line 120
Run the Copy QA checklist below.
- Distinctive: line 169
Default copy assumes plain text, no links.
- Distinctive: line 171
When reviewing copy, cross-check cold-email-deliverability constraints.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cold Email Copywriting
Cold email copy must be relevant, not relational. The prospect is a stranger — they do not care about small talk, shared alumni networks, or geographic coincidence. Value must be obvious in seconds.
Core Principle: The Stain Remover Pen
Imagine standing next to someone in an elevator who has a food stain on their white shirt they cannot see. You have a stain remover pen. You say:
"I noticed a stain on your shirt. I have a stain remover pen that'll take it out right now — want to try it?"
They immediately understand the pain, the fix, and the low effort to accept. No rapport required. Cold email works the same way — spot a real problem, offer a clear fix, make saying yes effortless.
What Never to Write
Reject and rewrite copy that includes:
- "I hope this email finds you well"
- "I love what you're doing at [company]"
- "Your profile is amazing"
- "I noticed we both went to [university]"
- "I'll be in your area next week"
- Generic compliments with no tied value
- Long paragraphs or essay-style pitches
- Obvious sales pressure — if they feel sold to, defenses go up
Merge Tags (Variables)
Merge tag syntax is tool-specific. Wrong casing means tags will not render and prospects see literal {{firstName}} in the inbox.
Default: camelCase — matches Instantly and most modern sequencers:
| Field | Tag |
| First name | {{firstName}} |
| Last name | {{lastName}} |
| Company | {{companyName}} |
| Sender first name | {{senderFirstName}} |
Before drafting or reviewing copy, confirm which sequencer or ESP the user sends from (e.g. Instantly, Smartlead, Lemlist, Outreach). Use that tool's exact tag names and casing. If unknown, default to camelCase and flag for the user to verify against their platform docs.
Never use snake_case (e.g. {{first_name}}) unless the user's tool explicitly requires it.
Email Structure
Every cold email follows four parts. Keep the full message short and mobile-optimized — readable on a phone without scrolling.
1. Greeting
Simple and human:
Hi {{firstName}},2. Hook (opening sentence)
One sentence. Extremely relevant to their situation. Catches attention because it reflects something true about their world — role, pain, trigger event, industry constraint.
The hook buys time to keep reading.
3. Bridge (body)
Connect the hook to the value proposition. This is not filler — it leads logically into what you offer and why they should believe you.
The bridge typically includes:
- Brief articulation of the problem or opportunity (1–2 sentences max)
- Proof — a case study, outcome, or credible reference (specific but honest; use user-provided facts only)
- Why this is insightful or beneficial to them, not why your product is great
Goal: pique curiosity — they should want to know more without feeling pitched.
4. Call to Action (CTA)
Low friction. This person does not know you. Do not default to asking for a meeting unless urgency is obvious and the offer is an obvious must-have.
Prefer CTAs they can answer with "Sure" or "Yes, please":
- "If I could send you a quick video showing what that looks like for [their context], would that be useful?"
- "If I could put together a short example of how [outcome] would work for [company], would you be open to me sharing it?"
- "Would it be helpful if I sent over [specific asset] — no call needed?"
- "Mind if I send that over?"
Patterns that work:
- "If I could provide you [X], would that be valuable?"
- "Would you be open to me sharing [personalized thing]?"
- "Do you mind if I send that right over?"
Always give an easy out — permission-based, "by the way" energy, not a calendar demand.
Meeting asks
Only when the prospect would immediately recognize urgent need. Otherwise earn the meeting through a low-friction first step.
Tone and Length
| Rule | Guidance |
| Length | Aim for 50–125 words total |
| Sentences | Short. One idea per sentence. |
| Jargon | Only what the ICP uses naturally |
| Curiosity | Lead with insight, not inventory |
| Honesty | No fabricated stats or fake case studies |
Agent Workflow
- Confirm sequencer/ESP and use correct merge tag casing (default: camelCase —
{{firstName}}for Instantly). - Gather from user: ICP, pain point, offer, proof (real case study/outcomes), desired next step.
- Draft using Hook → Bridge → CTA structure.
- Run the Copy QA checklist below.
- Present 1–2 variants if useful (different hooks or CTAs).
- Confirm deliverability skill constraints — no links in v1 unless user opts in.
Copy QA Checklist
- [ ] Merge tags use correct casing for user's sequencer (default: camelCase / {{firstName}})
- [ ] No small talk or empty flattery
- [ ] Hook is specific to recipient context (role, company, industry, trigger)
- [ ] Bridge connects hook to value without a pitch dump
- [ ] Includes proof or credibility (user-supplied, not invented)
- [ ] CTA is low friction — easy to reply "yes"
- [ ] Under ~125 words; mobile-scannable
- [ ] Curiosity-driven, not salesy
- [ ] No links/images (unless deliverability opt-in)
- [ ] Reads naturally aloud — not template-stiffTemplate (fill from user context)
Hi {{firstName}},
{{hook — one sentence, their situation}}
{{bridge — problem/opportunity + brief proof}}
{{low-friction CTA — permission-based}}
{{sign-off}}
{{senderFirstName}}Anti-Patterns
| Bad | Why | Better |
| "We help companies scale revenue" | Generic, no hook | "[Specific pain] at [company type] usually means [concrete issue]…" |
| "Do you have 15 minutes Tuesday?" | High friction for a stranger | "Mind if I send a 2-min walkthrough?" |
| 4 paragraphs of product features | Novel, self-centered | One outcome + one proof point |
| "Just checking in" follow-up | No new value | New insight, asset, or angle |
Examples
See examples.md for full before/after samples.
Relationship to Deliverability
Default copy assumes plain text, no links. If the CTA references a video or asset, the send pattern is: offer in email → send asset after positive reply — not a link in email 1.
When reviewing copy, cross-check cold-email-deliverability constraints.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

