Index of every page on this site: llms.txt
All skills
Run it yourself

When the user wants to write or run B2B cold outbound, or asks whether an opener, reason to reach out, or email works or why nobody replies: cold emails, follow-ups, sending domains, deliverability, LinkedIn, cadences. Send from secondary domains, verify lists first, turn off open tracking, stop every channel when a prospect replies. No AI tells like 'it's not X, it's Y'. For the list, see prospecting. For lifecycle email, see emails. For call scripts, see sales-enablement.

Use this Skill: https://skilld.dev/gh/coreyhaines31/marketingskills/cold-email

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈123 tokens for metadata: the name and description. ≈3k when used: this file. ≈16k more on demand in 11 files.

Description uses 6.1% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈491 characters, or 6.1%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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

  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 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.
  • Check the EU and UK rules first. Germany and Italy require the recipient's prior consent for a cold email, B2B included; the UK allows B2B email under legitimate interest but not to sole traders or partnerships without consent. The country-by-country rules and the exclusion checklist are in the prospecting skill's compliance reference.

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:

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 (built by this repository's maintainer; say so if you name it), 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)

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

2 warningstoday5 checks · Risk SAFE
  • Gen Agent Trust Hubtoday

    This skill provides instructional frameworks and reference data for B2B cold email outreach. It contains no malicious code, hidden instructions, or security vulnerabilities.

  • Socket9d

    No alerts

  • Snyktoday

    Risk: MEDIUM · 3 issues

  • Runlayer8mo

    2/6 files flagged

  • ZeroLeaks7mo

    1 finding · Score: 69/100

Signed by skilld at 5b2b400. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated yesterday
metadata
{
  "version": "2.2.7"
}
  • cold-email
  • sales
  • b2b
  • outreach
  • prospecting
  • email-sequences
  • copywriting
  • sdr

README badge

README badge for coreyhaines31/marketingskills/cold-email

Writes B2B cold emails and follow-up sequences designed to get replies, covering subject lines, opening hooks, body copy, calls-to-action, and multi-touch cadences. Targets sales development reps, founders, and sales teams doing outbound prospecting and includes frameworks for personalization based on research signals and role-level calibration.

Generated from the current SKILL.md.

Does this skill write emails for warm outreach or lifecycle sequences?
No. This skill focuses on cold outreach and B2B prospecting emails. For warm/lifecycle email sequences, use the emails skill instead.
What if I don't have research signals or proof points for my prospect?
The skill works with whatever you provide. If you have a strong value prop and clear outcome, that's enough to start writing. The skill will note what would make the email stronger but won't block on missing inputs.
Can I use templates or frameworks from this skill?
Yes. The skill provides copywriting frameworks (Observation → Problem → Proof → Ask, Question → Value → Ask, etc.) and references for subject lines, follow-up sequences, and personalization strategies. These are starting points, not rigid templates to fill in.
Does this skill cover follow-up sequences?
Yes. It covers multi-touch follow-up sequences with cadence, angle rotation, and breakup email templates. Each follow-up should add new proof or a different angle rather than just checking in.
What tone should cold emails have?
Write like a peer or colleague, not a vendor. Conversational with contractions, confident but not pushy, and grounded in the prospect's world. Avoid marketing patterns like 'I hope this email finds you well,' jargon, and feature dumps.

Generated from the current SKILL.md. These answers refresh after source changes.