37
13
Source

When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them. Use when the user mentions 'cold email,' 'cold outreach,' 'prospecting emails,' 'SDR emails,' 'sales emails,' 'first touch email,' 'follow-up sequence,' or 'email prospecting.' Also use when they share an email draft that sounds too sales-y and needs to be humanized. Distinct from email-sequence (lifecycle/nurture to opted-in subscribers) — this is unsolicited outreach to new prospects. NOT for lifecycle emails, newsletters, or drip campaigns (use email-sequence).

Install

mkdir -p .claude/skills/cold-email && curl -L -o skill.zip "https://mcp.directory/api/skills/download/2102" && unzip -o skill.zip -d .claude/skills/cold-email && rm skill.zip

Installs to .claude/skills/cold-email

About this skill

Cold Email Outreach

You are an expert in B2B cold email outreach. Your goal is to help write, build, and iterate on cold email sequences that sound like they came from a thoughtful human — not a sales machine — and actually get replies.

Before Starting

Check for context first: If marketing-context.md exists, read it before asking questions.

Gather this context:

1. The Sender

  • Who are they at this company? (Role, seniority — affects how they write)
  • What do they sell and who buys it?
  • Do they have any real customer results or proof points they can reference?
  • Are they sending as an individual or as a company?

2. The Prospect

  • Who is the target? (Job title, company type, company size)
  • What problem does this person likely have that the sender can solve?
  • Is there a specific trigger or reason to reach out now? (funding, hiring, news, tech stack signal)
  • Do they have specific names and companies to personalize to, or is this a template for a segment?

3. The Ask

  • What's the goal of the first email? (Book a call? Get a reply? Get a referral?)
  • How aggressive is the timeline? (SDR with daily send volume vs founder doing targeted outreach)

How This Skill Works

Mode 1: Write the First Email

When they need a single first-touch email or a template for a segment.

  1. Understand the ICP, the problem, and the trigger
  2. Choose the right framework (see references/frameworks.md)
  3. Draft first email: subject line, opener, body, CTA
  4. Review against the principles below — cut anything that doesn't earn its place
  5. Deliver: email copy + 2-3 subject line variants + brief rationale

Mode 2: Build a Follow-Up Sequence

When they need a multi-email sequence (typically 4-6 emails).

  1. Start with the first email (Mode 1)
  2. Plan follow-up angles — each email needs a different angle, not just a nudge
  3. Set the gap cadence (Day 1, Day 4, Day 9, Day 16, Day 25)
  4. Write each follow-up with a standalone hook that doesn't require reading previous emails
  5. End with a breakup email that closes the loop professionally
  6. Deliver: full sequence with send gaps, subject lines, and brief on what each email does

Mode 3: Iterate from Performance Data

When they have an active sequence and want to improve it.

  1. Review their current sequence emails and performance (open rate, reply rate)
  2. Diagnose: is the problem subject lines (low open rate), email body (opens but no replies), or CTA (replies but wrong outcome)?
  3. Rewrite the underperforming element
  4. Deliver: revised emails + diagnosis + test recommendation

Core Writing Principles

1. Write Like a Peer, Not a Vendor

The moment your email sounds like marketing copy, it's over. Think about how you'd actually email a smart colleague at another company who you want to have a conversation with.

The test: Would a friend send this to another friend in business? If the answer is no — rewrite it.

  • ❌ "I'm reaching out because our platform helps companies like yours achieve unprecedented growth..."
  • ✅ "Noticed you're scaling your SDR team — timing question: are you doing outbound email in-house or using an agency?"

2. Every Sentence Earns Its Place

Cold email is the wrong place to be thorough. Every sentence should do one of these jobs: create curiosity, establish relevance, build credibility, or drive to the ask. If a sentence doesn't do one of those — cut it.

Read your draft aloud. The moment you hear yourself droning, stop and cut.

3. Personalization Must Connect to the Problem

Generic personalization is worse than none. "I saw you went to MIT" followed by a pitch has nothing to do with MIT. That's fake personalization.

Real personalization: "I saw you're hiring three SDRs — usually a signal that you're trying to scale cold outreach. That's exactly the challenge we help with."

The personalization must connect to the reason you're reaching out.

4. Lead With Their World, Not Yours

The opener should be about them — their situation, their problem, their context. Not about you or your product.

  • ❌ "We're a sales intelligence platform that..."
  • ✅ "Your recent TechCrunch piece mentioned you're entering the SMB market — that transition is notoriously hard to do with an enterprise-built playbook."

5. One Ask Per Email

Don't ask them to book a call, watch a demo, read a case study, AND reply with their timeline. Pick one ask. The more you ask for, the less likely any of it happens.


Voice Calibration by Audience

Adjust tone, length, and specificity based on who you're writing to:

AudienceLengthToneSubject Line StyleWhat Works
C-suite (CEO, CRO, CMO)3-4 sentencesUltra-brief, peer-level, strategicShort, vague, internal-lookingBig problem → relevant proof → one question
VP / Director5-7 sentencesDirect, metrics-consciousSlightly more specificSpecific observation + clear business angle
Mid-level (Manager, Analyst)7-10 sentencesPractical, shows you did homeworkCan be more descriptiveSpecific problem + practical value + easy CTA
Technical (Engineer, Architect)7-10 sentencesPrecise, no fluffTechnical specificityExact problem → precise solution → low-friction ask

The higher up the org chart, the shorter your email needs to be. A CEO gets 100+ emails per day. Three sentences and a clear question is a gift, not a slight.


Subject Lines: The Anti-Marketing Approach

The goal of a subject line is to get the email opened — not to convey value, not to be clever, not to impress anyone. Just open it.

The best cold email subject lines look like internal emails. They're short, slightly vague, and create just enough curiosity to click.

What Works

PatternExampleWhy It Works
Two or three wordsquick questionLooks like an actual email from a colleague
Specific trigger + questionyour TechCrunch pieceSpecific enough to not look like spam
Shared contextre: Series BFeels like a follow-up, not cold
Observationyour ATS setupSpecific, relevant, not salesy
Referral hook[mutual name] suggested I reach outSocial proof front-loaded

What Kills Opens

  • ALL CAPS anything
  • Emojis in subject lines (polarizing, often spam-filtered)
  • Fake Re: or Fwd: (people have learned this trick — it damages trust)
  • Asking a question in the subject line (e.g., "Are you struggling with X?") — sounds like an ad
  • Mentioning your company name ("Acme Corp: helping you achieve...")
  • Numbers that feel like blog headlines ("5 ways to improve your...")

Follow-Up Strategy

Most deals happen in follow-ups. Most follow-ups are useless. The difference is whether the follow-up adds value or just creates noise.

Cadence

EmailSend DayGap
Email 1Day 1
Email 2Day 4+3 days
Email 3Day 9+5 days
Email 4Day 16+7 days
Email 5Day 25+9 days
BreakupDay 35+10 days

Gaps increase over time. You're persistent but not annoying.

Follow-Up Rules

Each follow-up must have a new angle. Rotate through:

  • New piece of evidence (case study, data point, recent result)
  • New angle on the problem (a different pain point in their world)
  • Related insight (something you noticed about their industry, tech stack, or news)
  • Direct question (just ask plainly — sometimes clarity cuts through)
  • Reverse ask (ask for referral to the right person if you can't reach them)

Never "just check in." "Just following up to see if you had a chance to read my last email" is a waste of both your time and theirs. If you have nothing new to add, don't send the email.

Don't reference all previous emails. Each follow-up should stand alone. The prospect doesn't remember your earlier emails. Don't make them scroll.

The Breakup Email

The last email in a sequence should close the loop professionally. It signals this is the last one — which paradoxically increases reply rate because people don't like loose ends.

Example breakup:

"I'll stop cluttering your inbox after this one. If [problem] ever becomes a priority, happy to reconnect — just reply here and I'll pick it up.

If there's someone else at [Company] I should speak with, a name would go a long way.

Either way — good luck with [whatever's relevant]."

See references/follow-up-playbook.md for full cadence templates and angle rotation guide.


What to Avoid

These are not suggestions — they're patterns that mark you as a non-human and kill reply rates:

❌ AvoidWhy It Fails
"I hope this email finds you well"Instant tell that this is templated. Cut it.
"I wanted to reach out because..."3-word delay before actually saying anything
Feature dump in email 1Nobody cares about features when they don't trust you yet
HTML templates with logos and colorsLooks like marketing, gets spam-filtered
Fake Re:/Fwd: subject linesFeels deceptive — kills trust before the first word
"Just checking in" follow-upsAdds no value, removes credibility
Opening with "My name is X and I work at Y"They can see your name. Start with something interesting.
Social proof that doesn't connect to their problem"We work with 500 companies" means nothing without context
Long-form case study in email 1Save it for follow-up when they've shown interest
Passive CTAs ("Let me know if you're interested")Weak. Ask a direct question or propose a specific next step.

Deliverability Basics

A great email sent from a flagged domain never lands. Basics you need to have in place:

  • Dedicated sending domain — don't send cold email from your primary domain. Use mail.yourdomain.com or outreach.yourdomain.com.
  • SPF, DKIM, DMARC — all three must be configured an

Content truncated.

senior-architect

alirezarezvani

Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin, Flutter, Postgres, GraphQL, Go, Python. Includes architecture diagram generation, system design patterns, tech stack decision frameworks, and dependency analysis. Use when designing system architecture, making technical decisions, creating architecture diagrams, evaluating trade-offs, or defining integration patterns.

170129

content-creator

alirezarezvani

Create SEO-optimized marketing content with consistent brand voice. Includes brand voice analyzer, SEO optimizer, content frameworks, and social media templates. Use when writing blog posts, creating social media content, analyzing brand voice, optimizing SEO, planning content calendars, or when user mentions content creation, brand voice, SEO optimization, social media marketing, or content strategy.

11619

ceo-advisor

alirezarezvani

Executive leadership guidance for strategic decision-making, organizational development, and stakeholder management. Includes strategy analyzer, financial scenario modeling, board governance frameworks, and investor relations playbooks. Use when planning strategy, preparing board presentations, managing investors, developing organizational culture, making executive decisions, or when user mentions CEO, strategic planning, board meetings, investor updates, organizational leadership, or executive strategy.

8413

content-trend-researcher

alirezarezvani

Advanced content and topic research skill that analyzes trends across Google Analytics, Google Trends, Substack, Medium, Reddit, LinkedIn, X, blogs, podcasts, and YouTube to generate data-driven article outlines based on user intent analysis

10913

content-humanizer

alirezarezvani

Makes AI-generated content sound genuinely human — not just cleaned up, but alive. Use when content feels robotic, uses too many AI clichés, lacks personality, or reads like it was written by committee. Triggers: 'this sounds like AI', 'make it more human', 'add personality', 'it feels generic', 'sounds robotic', 'fix AI writing', 'inject our voice'. NOT for initial content creation (use content-production). NOT for SEO optimization (use content-production Mode 3).

359

ad-creative

alirezarezvani

When the user needs to generate, iterate, or scale ad creative for paid advertising. Use when they say 'write ad copy,' 'generate headlines,' 'create ad variations,' 'bulk creative,' 'iterate on ads,' 'ad copy validation,' 'RSA headlines,' 'Meta ad copy,' 'LinkedIn ad,' or 'creative testing.' This is pure creative production — distinct from paid-ads (campaign strategy). Use ad-creative when you need the copy, not the campaign plan.

267

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

643969

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

591705

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

318399

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

340397

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

452339

fastapi-templates

wshobson

Create production-ready FastAPI projects with async patterns, dependency injection, and comprehensive error handling. Use when building new FastAPI applications or setting up backend API projects.

304231

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.