本文へ移動
cccskills
無料GitHub で公開

cold-email

Write and optimize B2B cold outreach emails and follow-up sequences. For lifecycle/nurture emails to opted-in subscribers use email-sequence.

日本語の概要は準備中です。原文の説明を表示しています。

SebastianLuser/claude-code-arcaneスター 3(GitHub 3 + cccskills 0)

実行スコア 未検証

インストール方法を見る

含まれるファイル(6)

  • SKILL.md8.6 KB
  • references/deliverability-guide.md9.0 KB
  • references/follow-up-playbook.md9.1 KB
  • references/frameworks.md9.0 KB
  • references/voice-and-subject-lines.md2.2 KB
  • scripts/email_sequence_analyzer.py19.2 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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 & Subject Lines

See references/voice-and-subject-lines.md for audience-specific calibration (C-suite, VP, mid-level, technical), subject line patterns that work, and patterns that kill opens.


Follow-Up Strategy

Cadence: Day 1 → Day 4 → Day 9 → Day 16 → Day 25 → Breakup Day 35. Gaps increase over time. Each follow-up must have a new angle (evidence, problem angle, insight, direct question, or reverse ask). Never "just check in." Each email stands alone.

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


What to Avoid

Patterns that mark you as non-human: "I hope this email finds you well," "I wanted to reach out because...," feature dumps in email 1, HTML templates, fake Re:/Fwd: subject lines, "Just checking in" follow-ups, opening with "My name is X and I work at Y," passive CTAs.

See references/frameworks.md for the full anti-patterns list.


Deliverability Basics

Use a dedicated sending domain, configure SPF/DKIM/DMARC, warm up new domains over 4-6 weeks, send plain text, include unsubscribe mechanism, stay under 100-200 emails/day.

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

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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

Plan, design, and implement A/B tests and experiments with statistical rigor. Covers hypothesis frameworks, sample sizing, metrics, and result analysis.

日本語の概要は準備中です。原文の説明を表示しています。

SebastianLuser/claude-code-arcane32026年10月27日 更新

Web/mobile accessibility decision guide: WCAG 2.2 AA, ARIA, keyboard nav, focus management, contrast, testing. Use for: a11y, accessibility, wcag, aria, screen reader, keyboard, contrast.

日本語の概要は準備中です。原文の説明を表示しています。

SebastianLuser/claude-code-arcane32026年10月27日 更新

Generate, iterate, and scale ad creative for paid advertising across Google, Meta, LinkedIn, and X. Covers platform specs, creative frameworks, and quality validation.

日本語の概要は準備中です。原文の説明を表示しています。

SebastianLuser/claude-code-arcane32026年10月27日 更新

Musica interactiva para juegos: layering vertical, re-secuenciacion horizontal, stingers, reglas de transicion con sync points, y mapeo de estados de gameplay a musica. Usar para: musica adaptativa, sistema de musica dinamica, transiciones musicales, combat music.

日本語の概要は準備中です。原文の説明を表示しています。

SebastianLuser/claude-code-arcane32026年10月27日 更新

Design multi-agent systems, create agent architectures, define communication patterns, and build autonomous agent workflows with structured evaluation frameworks.

日本語の概要は準備中です。原文の説明を表示しています。

SebastianLuser/claude-code-arcane32026年10月27日 更新

Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, response formats, and quality loops.

日本語の概要は準備中です。原文の説明を表示しています。

SebastianLuser/claude-code-arcane32026年10月27日 更新

SebastianLuser のスキルをすべて見る

このスキルの問題を報告する