MCPInstall

cold-email

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

Installs
867
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/alirezarezvani/claude-skills --skill cold-email
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads cold-email automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

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 .claude/product-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 and passing. Use mail-tester.com to verify.
  • Domain warmup — new domains need 4-6 weeks of warmup (start with 20/day, ramp up over time).
  • Plain text emails — or minimal HTML. Heavy HTML triggers spam filters.
  • Unsubscribe mechanism — required legally (CAN-SPAM, GDPR). Include a simple opt-out.
  • Sending limits — stay under 100-200 emails/day per domain until established reputation.
  • Bounce rate — above 5% hurts deliverability. Verify email lists before sending.

See references/deliverability-guide.md for domain warmup schedule, SPF/DKIM setup, and spam trigger word list.


Proactive Triggers

Surface these without being asked:

  • Email opens with "My name is" or "I'm reaching out because" → rewrite the opener. These are dead-on-arrival openers. Flag and offer an alternative that leads with their world.
  • First email is longer than 150 words → almost certainly too long. Flag word count and offer to trim.
  • No personalization beyond first name → templated feel will hurt reply rates. Ask if there's a trigger or signal they can work with.
  • Follow-up says "just checking in" or "circling back" → useless follow-up. Ask what new angle or value they can bring to that touchpoint.
  • HTML email template → recommend plain text. Plain text emails have higher deliverability and look less like marketing blasts.
  • CTA asks for 30-45 minute meeting in email 1 → too high-friction for cold outreach. Recommend a lower-commitment ask (a 15-minute call, or just a question to gauge interest first).

Tools

ToolInvocationOutput
Sequence analyzerpython3 scripts/email_sequence_analyzer.py sequence.json (no arg = embedded demo; - reads stdin)Per-email 0-100 score across word count, reading level, personalization, CTA clarity, spam triggers, subject lines

Run it on every drafted sequence before delivering: any email scoring below 70 gets rewritten against the flagged dimensions (spam triggers and CTA clarity first), then re-scored.


Output Artifacts

When you ask for...You get...
Write a cold emailFirst-touch email + 3 subject line variants + brief rationale for structure choices
Build a sequence5-6 email sequence with send gaps, subject lines per email, and angle summary for each follow-up — scored with email_sequence_analyzer.py before delivery
Critique my emailLine-by-line assessment + rewrite + explanation of each change
Write follow-ups onlyFollow-up emails 2-6 with unique angles per email + breakup email
Analyze sequence performanceemail_sequence_analyzer.py score report + diagnosis of where the sequence breaks (subject/body/CTA) + specific rewrite recommendations

Communication

All output follows the structured communication standard:

  • Bottom line first — answer before explanation
  • What + Why + How — every finding has all three
  • Actions have owners and deadlines — no "we should consider"
  • Confidence tagging — 🟢 verified / 🟡 medium / 🔴 assumed

Related Skills

  • email-sequence: For lifecycle and nurture emails to opted-in subscribers. Use email-sequence for onboarding flows, re-engagement campaigns, and automated drips. NOT for cold outreach — that's cold-email.
  • copywriting: For marketing page copy. Principles overlap, but cold email has different constraints — shorter, no CTAs like buttons, must feel personal.
  • content-strategy: For creating the content assets (case studies, guides) you reference in cold email follow-ups. Good follow-up sequences often link to content.
  • marketing-strategy-pmm: For positioning and ICP definition. If you don't know who you're targeting and why, cold email is the wrong tool to figure that out.

FAQ

What does the cold-email skill do?

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

How do I install cold-email?

Run npx skills add https://github.com/alirezarezvani/claude-skills --skill cold-email in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/cold-email/ (personal) or .claude/skills/cold-email/ (project).

Which AI agents can use cold-email?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is cold-email safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains cold-email?

It is published by alirezarezvani in alirezarezvani/claude-skills. It has 867 recorded installs.

More from alirezarezvani/claude-skills

View all →

engineering-skills

alirezarezvani/claude-skills

Index of the engineering-team skills bundle for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw, and 6 more tools. Architecture, frontend, backend, QA, DevOps, security, AI/ML, data engineering, Playwright, Stripe, AWS, MS365 (stdlib-only Python tools). Use when browsing or choosing among engineering-team role skills — load only the one specialist SKILL.md you need, never bulk-load the bundle.

Backend & APIs2.4K installs

finance-skills

alirezarezvani/claude-skills

Router/index for the finance skills bundled in this plugin: financial-analyst (ratio analysis, DCF valuation, budget variance, rolling forecasts), saas-metrics-coach (ARR/MRR, churn, CAC/LTV, NRR, quick ratio) and month-end-close (close calendar, reconciliations, flux review). Use when a finance request doesn't obviously match one skill and you need to pick the right one (e.g., 'analyze these financials', 'how healthy are my SaaS metrics').

Business & Finance2.3K installs

marketing-skills

alirezarezvani/claude-skills

Directory and router for the marketing skills library. Use when you need to find the right marketing skill for a task, see what marketing capabilities exist, or get oriented in this plugin. 44 specialist skills across 8 pods (content, SEO + AEO, CRO, channels, growth, intelligence, sales enablement, ops), 59 stdlib Python tools. Routes to one skill — it does not execute marketing work itself.

Marketing & SEO2.3K installs

business-growth-skills

alirezarezvani/claude-skills

Router/index for the 4 business & growth skills bundled in this plugin: customer-success-manager (health scoring, churn risk, expansion), sales-engineer (RFP analysis, competitive matrices, PoC planning), revenue-operations (pipeline, forecast accuracy, GTM efficiency), and contract-and-proposal-writer. Use when a growth/revenue request doesn't obviously match one skill and you need to pick the right one (e.g., 'which accounts are at risk', 'should we bid on this RFP').

Business & Finance2.2K installs

engineering-advanced-skills

alirezarezvani/claude-skills

Index of 37 advanced engineering agent skills for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. Use when browsing or choosing among the POWERFUL-tier engineering skills: agent design, RAG, MCP servers, CI/CD, database design, observability, security auditing, changelog/release automation, reliability (SLO/chaos/flags/operators), platform ops.

AI & Agents2K installs

product-skills

alirezarezvani/claude-skills

Use when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, SaaS scaffolding) or the 4 standalone product-team plugins (user stories, Apple HIG, code-to-PRD, research summarizer). Triggers on 'help me prioritize', 'plan a product experiment', 'we ship features nobody uses', 'run the discovery loop', 'is our OST sound'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a continuous-discovery loop (Torres cadence tracker + OST linter as machine gates) or a full goal→plan→execute→verify→close run through the repo-wide agent-harness. Distinct from project-management (how to deliver vs what to build), marketing/landing (from-scratch pages), and engineering/agent-harness (the generic loop engine this orchestrator plugs into).

Popular productivity & automation skills

View category →

agent-browser

vercel-labs/agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.

OfficialProductivity & Automation1.3M installs

lark-doc

open.feishu.cn

飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。

lark-base

open.feishu.cn

飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。

lark-drive

open.feishu.cn

飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。

lark-shared

open.feishu.cn

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.

lark-im

open.feishu.cn

飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。