营销与写作

cold-email

coreyhaines31/m…ngskills

Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to sending setup, LinkedIn, multichannel cadences, and reply handling. Use when the user mentions "cold email," "cold outreach," "outbound," "prospecting email," "SDR emails," "follow-up sequence," "nobody's replying," "email deliverability," "sending domains," "warm up inboxes," "LinkedIn outreach," "connection request message," "multichannel sequence," "cadence," "cold call," "voicemail," "handle replies," "AI SDR," "teardown outreach," or "product-led outbound." Send from secondary domains, verify lists first, turn off open tracking, and stop every channel when a prospect replies. Copy avoids AI tells like 'it's not X, it's Y' reveals. For building the list and account research, see prospecting. For lifecycle email, see emails. For call scripts and sales collateral, see sales-enablement.

  • 13万 次安装
  • 5.7万 星标
  • 收录于

安装命令

npx skills add https://github.com/coreyhaines31/marketingskills --skill cold-email

要点

Write B2B cold emails and follow-up sequences designed to get replies.

  • Covers subject lines, opening lines, body copy, CTAs, personalization strategies, and multi-touch follow-up sequences with angle rotation
  • Emphasizes peer-to-peer voice over template-driven copy; every sentence must serve the reader and connect personalization to the problem
  • Provides five copywriting frameworks (Observation → Problem → Proof → Ask, Question → Value → Ask, and others) plus guidance on low-friction CTAs and breakup email protocols
  • Includes data on reply rates, conversion funnels, subject line optimization, and common mistakes to avoid (jargon, feature dumps, generic openings)

SKILL.md

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.