C

cold-email

Verified

by coreyhaines31 · Updated Apr 16, 2026

opus
97in10.6Kout
$0.584m 32s

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see email-sequence. For sales collateral beyond emails, see sales-enablement.

cold-emailsalescopywritingoutreachemailb2b

See It In Action

1 turns·claude
The project codebase is in your current working directory. Explore the files to understand the code before making changes. need cold outreach for 12 CTOs from our webinar today — personalized first emails + 3 followups each so sales can load them before EOD

Let me read the key files to get exact details for writing these emails.

I have all the context I need. Let me write all 12 sequences — 48 emails total. I'll write them to a file sales can work from directly.

All 48 emails are written and saved to cold-outreach-sequences.md. Here's what sales is getting:

12 CTOs x 4 emails each (first touch + 3 follow-ups on Day 3/7/14 cadence)

Every email is personalized to the CTO's specific webinar behavior and signals:

CTOCompanyHook
Wei ZhangCanopy Insurance2 days/sprint lost to code review → Ramp's 62% reduction
Chris NakamuraPulsePoint Media"Alert fatigue" tweet + on-call question → Lattice MTTR
Priya SharmaNovaPayIncident ROI question + Series C timing → Lattice + Ramp
Rachel OkonkwoLoopHealth30-person acquisition + Jira/GitHub question → Vanta onboarding
Marcus JohnsonGreenline Analytics3-hour deploys + platform hires → pipeline automation ROI
Daniel KimVaultStreamSOC 2/VPC/data residency questions → security architecture
Aisha PatelTrueNorth CRMJenkins→GitHub Actions migration → marketplace as migration add-on
Tomas RiveraFidelio FinanceAudit logging + public company compliance → regulated fintech angle
Sofia ReyesBrightPathLinkedIn "developer toil" post → small-team automation
Elena VolkovMosaic DesignGitLab compatibility question → native GitLab support
James ThorntonPackwise LogisticsLow engagement → general value prop + webinar recording
Lisa BrennanMeadow RoboticsEmbedded background → code review for hardware/software teams

The file also includes a priority tier ranking (Tier 1-3 by signal strength) and a timing calendar so sales knows which emails to load first and when each follow-up fires.

Claude Sonnet 4.6

Permissions

ScopeDescription
filesystem:read

SKILL.md

Cold Email Writing

You are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template.

Before Writing

Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md 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):

  1. Who are you writing to? — Role, company, why them specifically
  2. What do you want? — The outcome (meeting, reply, intro, demo)
  3. What's the value? — The specific problem you solve for people like them
  4. What's your proof? — A result, case study, or credibility signal
  5. 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 — not someone 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 — not to sell.

  • 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.


Quality Check

Before presenting, gut-check:

  • Does it sound like a human wrote it? (Read it aloud)
  • 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
  • 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:

Use this data to inform your writing — not as a checklist to satisfy.


Related Skills

  • copywriting: For landing pages and web copy
  • email-sequence: For lifecycle/nurture email sequences (not cold outreach)
  • social-content: For LinkedIn and social posts
  • product-marketing-context: For establishing foundational positioning
  • revops: For lead scoring, routing, and pipeline management

FAQ

What does cold-email do?

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see email-sequence. For sales collateral beyond emails, see sales-enablement.

When should I use cold-email?

Use it when you need a repeatable workflow that produces text report.

What does cold-email output?

In the evaluated run it produced text report.

How do I install or invoke cold-email?

Ask the agent to use this skill when the task matches its documented workflow.

Which agents does cold-email support?

Agent support is inferred from the source, but not explicitly declared.

What tools, channels, or permissions does cold-email need?

It uses no extra tools; channels commonly include text; permissions include filesystem:read.

Is cold-email safe to install?

Static analysis marked this skill as low risk; review side effects and permissions before enabling it.

How is cold-email different from an MCP or plugin?

A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.

Does cold-email outperform not using a skill?

About cold-email

When to use cold-email

You need a first-touch cold email for a specific prospect or segment. You want a multi-email follow-up sequence that increases reply chances. You have limited prospect context but still need concise, human-sounding outreach copy.

When cold-email is not the right choice

You need to actually send emails or run an outbound campaign from a mail platform. You are writing lifecycle, nurture, or customer marketing emails rather than cold outreach.

What it produces

Produces text report.