cold-email
Skill0 starsChanged todayMITView on GitHub
Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling. Use when the user mentions "cold email," "cold outreach," "outbound," "prospecting email," "SDR emails," "follow-up sequence," "nobody's replying," "email deliverability," "sending domains," "warm up inboxes," "LinkedIn outreach," "connection request message," "multichannel sequence," "cadence," "cold call," "voicemail," "handle replies," "AI SDR," "teardown outreach," or "product-led outbound." Send from secondary domains, verify lists first, turn off open tracking, and stop every channel when a prospect replies. Copy avoids AI tells like 'it's not X, it's Y' reveals. For building the list and account research, see prospecting. For lifecycle email, see emails. For call scripts and sales collateral, see sales-enablement.
101 other projects use a version of this, 71 of them edited.
Adopted by
Most recently taken up by
- JulyLay/cold-emailedited, first seen Nov 16, 2026
- martinbattaglia-commits/Claude-skillsedited, first seen Nov 16, 2026
- AlejandroGodius/claude-skillsedited, first seen Nov 16, 2026
- yotamwiesel/claude-skillsedited, first seen Nov 16, 2026
- revnu-app/revnu-plugintheir own version, first seen Nov 8, 2026
- darkweb19/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use free-tools, popups and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CesarjoquinSkillfree-tools
When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.
Also in 25 projects that use this
CesarjoquinSkillpopups
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.
Also in 23 projects that use this
coreyhaines31Skillmarketing-council
When the user wants several expert takes on a marketing decision, or asks what a famous marketer would say about it: a simulated board (Seth Godin, David Ogilvy, April Dunford, Byron Sharp, and more), each grounded in their documented frameworks, where they disagree, and a recommendation. To execute, hand off to the relevant skill.
Also in 18 projects that use this
Hussain-ElfalahSkillandreessen
Also in 4 projects that use this
Hussain-ElfalahSkillbusiness-investment-advisor
Also in 4 projects that use this
roerohanSkillemails
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
Also in 24 projects that use this
- +5 more from Cesarjoquin
- +1 more from Hussain-Elfalah
Other versions101 projects use a version of this.
Word for word · 0
None found.
Edited · 71
- coreyhaines31/marketingskills★ 61k96% same
- LeoYeAI/openclaw-marketing-skills★ 1k83% same
- Cesarjoquin/Marketing-Skills★ 19085% same
- b1rdmania/ghostclaw★ 9183% same
- open-fox/agents★ 5585% same
- mia-ppp/PMM-Skills★ 5471% same
- SZcalligrapher/slash-skills-subscription★ 3285% same
- roerohan/skills★ 2983% same
- ukunal91app/Marketing-Skills-by-Corey-Haines★ 2683% same
- wpgaurav/WordPress-skills★ 1980% same
61 more not listed
Wrote their own version · 30
- LOGIN-TB/claude-skills★ 82same name
- Mikefluff/skills★ 26same name
- GTMify/aigtm★ 25same name
- Hassaan146/claude-skills★ 18same name
- scayver/marketing-skills★ 8same name
- bereach-ai/linkedin-prospecting-skills★ 6same name
- oncesylvia/fundraising-skills★ 4same name
- cmj-hub/claude-cold-email★ 3same name
- AgentlyLabs/founder-skills★ 2same name
- DariuszCiesielski/polish-agent-skills★ 2same name
20 more not listed
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 repository72 other files it gives its agents.
- animate-expoSkill
- animateSkill
- animation-performanceSkill
- animation-vocabularySkill
- apple-designSkill
- ask-emilSkill
- ask-mattSkill
- ask-sonnerSkill
- better-typographySkill
- break-uiSkill
- chief-of-staffSkill
- choreographSkill
- claritySkill
- claude-handoffSkill
- codebase-designSkill
- code-reviewSkill
- content-strategySkill
- copywritingSkill
- croSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- emil-design-engSkill
- find-animation-opportunitiesSkill
- frontend-designSkill
- gesturesSkill
- git-guardrails-claude-codeSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- implement-specSkill
- improve-animationsSkill
- improve-codebase-architectureSkill
- learn-tasteSkill
- loop-meSkill
- marketing-psychologySkill
- migrate-to-shoehornSkill
- mobile-nativeSkill
- persuasionSkill
- pick-ui-librarySkill
- prisma-client-apiSkill
- programmatic-seoSkill
- prototypeSkill
- prototype-variantsSkill
- prSkill
- remove-animationsSkill
- researchSkill
- retroSkill
- review-animationsSkill
- scaffold-exercisesSkill
- seo-auditSkill
- setup-matt-pocock-skillsSkill
- setup-pre-commitSkill
- setup-ts-deep-modulesSkill
- Skillpack Self-testSkill
- software-factorySkill
- supabase-postgres-best-practicesSkill
- tddSkill
- teachSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 4 are common, 0 are distinctive, and 1 is very specific to this project.
4
Common
Most of the 94 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older …
- Common: line 39
If you remove the personalized opening and the email still makes sense, the personalization isn't working.
- Common: line 92
Should look like it came from a colleague ("reply rates," "hiring ops," "Q2 forecast")
- Common: line 93
No product pitches, no urgency, no emojis, no prospect's first name
- Common: line 183
Use this data to inform your writing — not as a checklist to satisfy.
“Common” is measured: kept by at least 6 in 10 of the 94 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cold Email Writing
You are an expert in cold outbound. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template — and to make sure they reach the inbox, work alongside the other channels, and turn replies into meetings.
Before Writing
Check for product marketing context first:
If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.
Understand the situation (ask if not provided):
- Who are you writing to? — Role, company, why them specifically
- What do you want? — The outcome (meeting, reply, intro, demo)
- What's the value? — The specific problem you solve for people like them
- What's your proof? — A result, case study, or credibility signal
- Any research signals? — Funding, hiring, LinkedIn posts, company news, tech stack changes
Work with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger.
Writing Principles
Write like a peer, not a vendor
The email should read like it came from someone who understands their world and isn't trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.
Every sentence must earn its place
Cold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer.
Personalization must connect to the problem
If you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out.
See personalization.md for the 4-level system and research signals.
Lead with their world, not yours
The reader should see their own situation reflected back. "You/your" should dominate over "I/we." Don't open with who you are or what your company does.
One ask, low friction
Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.
Voice & Tone
The target voice: A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.
Calibrate to the audience:
- C-suite: ultra-brief, peer-level, understated
- Mid-level: more specific value, slightly more detail
- Technical: precise, no fluff, respect their intelligence
What it should NOT sound like:
- A template with fields swapped in
- A pitch deck compressed into paragraph form
- A LinkedIn DM from someone you've never met
- An AI-generated email (avoid the telltale patterns: "I hope this email finds you well," "I came across your profile," "leverage," "synergy," "best-in-class")
Structure
There's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.
Common shapes that work:
- Observation → Problem → Proof → Ask — You noticed X, which usually means Y challenge. We helped Z with that. Interested?
- Question → Value → Ask — Struggling with X? We do Y. Company Z saw [result]. Worth a look?
- Trigger → Insight → Ask — Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious?
- Story → Bridge → Ask — [Similar company] had [problem]. They [solved it this way]. Relevant to you?
For the full catalog of frameworks with examples, see frameworks.md.
Subject Lines
Short, boring, internal-looking. The subject line's only job is to get the email opened.
- 2-4 words, lowercase, no punctuation tricks
- Should look like it came from a colleague ("reply rates," "hiring ops," "Q2 forecast")
- No product pitches, no urgency, no emojis, no prospect's first name
See subject-lines.md for the full data.
Follow-Up Sequences
Each follow-up should add something new — a different angle, fresh proof, a useful resource. "Just checking in" gives the reader no reason to respond.
- 3-5 total emails, increasing gaps between them
- Each email should stand alone (they may not have read the previous ones)
- The breakup email is your last touch — honor it
See follow-up-sequences.md for cadence, angle rotation, and breakup email templates.
Before You Send
Copy only matters if it reaches the inbox. Before the first send:
- Send from secondary domains, never your primary one, with SPF, DKIM, and DMARC set up and mailboxes warmed for 3–4 weeks.
- Verify every list right before upload and keep bounces under 2%.
- Turn off open and click tracking. Measure replies.
- Include a plain-text opt-out line and your postal address in every email.
Domain and mailbox math, the Google, Yahoo, and Microsoft rules, monitoring, and stop-loss thresholds are in deliverability.md.
Beyond Email
Most outbound that works in 2026 runs on more than one channel:
- LinkedIn: profile, limits, the engage-then-connect sequence, message copy, and the automation decision. See linkedin-outreach.md.
- Cadence: how email, LinkedIn, calls, video, and ads fit together by tier, and the rule that a reply on any channel stops all of them. See multichannel-cadence.md. Call scripts are in the sales-enablement skill.
- Plays: value-first teardowns for services, product-led outbound for self-serve SaaS, problem-led outbound with a free sample, and founder-led outreach. See outbound-plays.md.
When They Reply
Classify every reply (positive, information request, objection, not now, referral, out of office, unsubscribe), answer positive replies within minutes, and book with two proposed times plus a link. What an agent can handle alone and what needs a human is in reply-handling.md.
Quality Check
Before presenting, gut-check:
- Does it sound like a human wrote it? (Read it aloud, and check for the AI tells below)
- Would YOU reply to this if you received it?
- Does every sentence serve the reader, not the sender?
- Is the personalization connected to the problem?
- Is there one clear, low-friction ask?
What to Avoid
- Opening with "I hope this email finds you well" or "My name is X and I work at Y"
- Jargon: "synergy," "leverage," "circle back," "best-in-class," "leading provider"
- Feature dumps. One proof point beats ten features
- AI tells, which prospects spot in the first line and delete:
- Contrast reveals ("It's not about X, it's about Y") and "no X, no Y, no Z" lists
- A claim followed by a comma and more restating clauses
- Self-answered questions ("The result? 40% more meetings.") and colon reveals. A real question you want them to answer is fine
- Stock phrases: "Here's the thing," "I'll be honest," "Quick question" as an opener, "Say goodbye to," "Unlock," "Take it to the next level"
- Em dashes
- For the full blacklist, use the copywriting skill's AI-tells reference
- HTML, images, or multiple links
- Fake "Re:" or "Fwd:" subject lines
- Identical templates with only {{FirstName}} swapped
- Asking for 30-minute calls in first touch
- "Just checking in" follow-ups
Data & Benchmarks
The references contain performance data if you need to make informed choices:
- benchmarks.md — Reply rates, conversion funnels, expert methods, common mistakes
- deliverability.md — Sending domains, mailboxes, mailbox-provider rules, warmup, monitoring, stop-loss rules
- linkedin-outreach.md — LinkedIn profile, limits, sequence, copy, automation risk
- multichannel-cadence.md — Cadences by tier, cross-channel rules, calls, video, direct mail, ads
- outbound-plays.md — Value-first teardown, product-led, problem-led, and founder-led plays
- reply-handling.md — Reply types, speed, booking, early objections, agent permissions
- personalization.md — 4-level personalization system, research signals
- subject-lines.md — Subject line data and optimization
- follow-up-sequences.md — Cadence, angles, breakup emails
- frameworks.md — All copywriting frameworks with examples
Use this data to inform your writing — not as a checklist to satisfy.
Tool Integrations
For setup, see the tools registry, including its sales outbound quick start. Tools most used with this skill:
| Job | Tools | Guides |
| Email sending and sequences | Instantly, lemlist, Outreach | instantly.md, lemlist.md, outreach.md |
| LinkedIn steps | HeyReach, lemlist (both carry LinkedIn terms-of-service risk) | heyreach.md |
| Verification before send | Truelist, Hunter | truelist.md, hunter.md |
| CRM and reply logging | HubSpot, Attio, Close | attio.md, close.md |
| Booking | Calendly, SavvyCal | calendly.md, savvycal.md |
Instantly's webhooks (reply received, lead interested, bounced, unsubscribed) are the simplest way to drive the cross-channel stop and reply triage from an agent.
Related Skills
- prospecting: For building and qualifying the prospect list, signals, enrichment, verification, and account research — the natural upstream step before cold-email
- copywriting: For landing pages and web copy
- emails: For lifecycle/nurture email sequences (not cold outreach)
- social: For LinkedIn and social posts
- product-marketing: For establishing foundational positioning
- revops: For lead scoring, routing, pipeline management, and the outbound stage model
- sales-enablement: For cold call scripts, voicemails, and deal-stage objections
- marketing-loops: For running outbound on a schedule (signal sweeps, reply triage, domain health, sequence reviews)
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.

