Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
infrasity-labs avatar

Cold Email

  • 52 installs
  • 93 repo stars
  • Updated June 28, 2026
  • infrasity-labs/dev-gtm-claude-skills

This is a copy of cold-email by coreyhaines31 - installs and ranking accrue to the original listing.

Cold Email is an agent skill that applies benchmark-backed B2B cold-email methods so solo builders can draft sequences aligned to realistic open, reply, and

About

Cold Email is an agent skill from the dev-gtm skill pack that encodes expert outbound methods and published performance benchmarks for solo and indie builders selling dev tools, APIs, and B2B SaaS. It is for founders who need repeatable cold sequences—not one-off chat drafts—grounded in measurable targets for opens, replies, positive sentiment, meetings booked, and bounces. Use it when you are launching distribution to a named ICP, validating an offer with a small targeted list, or growing pipeline through follow-up cadences, and you want copy decisions tied to levers that actually move reply rate: hook framing, personalization depth, word count, list size per campaign, reading level, timing, and follow-up spacing. The included funnel model makes expectations explicit so you do not misread a 5% reply rate as failure when end-to-end conversion is inherently low. Treat it as procedural GTM knowledge packaged for Claude Code, Cursor, and Codex workflows rather than an ESP integration or CRM MCP server.

  • 2024–2025 benchmark table for open, reply, positive-reply, meeting-booking, and bounce rates with good vs excellent band
  • Realistic 500-email funnel model with ~0.2% end-to-end conversion for average performers
  • Seven ranked performance levers: hook type, personalization depth, brevity, targeting precision, follow-ups, reading lev
  • Concrete targets such as 25–75 word bodies, ≤50 contacts per campaign, and Thursday peak reply timing
  • Hook guidance: timeline hooks vs problem hooks with stated meeting lift (3.4x) for sequence design

Cold Email by the numbers

  • 52 all-time installs (skills.sh)
  • +4 installs in the week ending Jul 25, 2026 (Skillselion tracking)
  • Data as of Jul 26, 2026 (Skillselion catalog sync)
npx skills add https://github.com/infrasity-labs/dev-gtm-claude-skills --skill cold-email

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs52
repo stars93
Last updatedJune 28, 2026
Repositoryinfrasity-labs/dev-gtm-claude-skills

What it does

Draft and tune B2B cold-email sequences using 2024–2025 benchmark targets, funnel math, and ranked performance levers for dev GTM.

Who is it for?

Best when you're running small, highly targeted outbound (roughly ≤50 contacts per campaign) and want sequences informed by published reply-rate and meeting-booking benchmarks.

Skip if: Skip if you're relying only on inbound/PLG, mass-blast outreach without ICP clarity, or regulated industries where you have not reviewed compliance and opt-out requirements locally.

When should I use this skill?

When you are writing or optimizing B2B cold email or follow-up sequences and want copy and cadence choices anchored to published GTM benchmarks rather than intuition.

What you get

You leave with benchmark-calibrated messaging choices—hooks, length, list size, follow-ups, and timing—mapped to a explicit reply-to-meeting funnel you can paste into your ESP or CRM workflow.

  • Cold-email and follow-up drafts sized to 25–75 words with hook and CTA choices tied to benchmark levers
  • Campaign expectations framed with the documented open→reply→meeting funnel
  • A short optimization checklist mapped to the seven ranked performance levers

By the numbers

  • Benchmark bands cite ~27.7% average open rate and ~4–5.8% reply rate with good tiers up to 10–15%
  • Funnel model: 500 emails → ~25 replies (5%) → ~4 meetings → ~1 client (~0.2% end-to-end for average performers)
  • Performance guidance: 25–75 word emails, ≤50 contacts per campaign, first follow-up adds ~49% more replies, Thursday ~6.

Files

SKILL.mdMarkdownGitHub ↗

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.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):

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:

  • benchmarks.md — Reply rates, conversion funnels, expert methods, common mistakes
  • 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.

Related skills

How it compares

Use instead of generic “write me a cold email” prompts that omit funnel math, benchmark bands, and ranked deliverability/reply levers.

FAQ

Who is cold-email for?

Cold Email is for developers doing dev-focused GTM—founders, technical solopreneurs, and small teams selling SaaS, APIs, or dev services who own their own outbound copy and list strategy.

When should I use cold-email?

Use it during Validate to pressure-test an offer with a tight prospect list, during Launch distribution when you are opening your first outbound channel, and during Grow when you iterate follow-ups and re-engagement; it also helps in Idea audience work when you need structured fo

Is cold-email safe to install?

Treat it as procedural marketing guidance only; review the Security Audits panel on this Prism page before installing, and never paste secrets, full lead databases, or non-consented personal data into agent sessions.

Sales & Marketingdistributionlifecycle

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.