Cold Email
Write and run B2B cold outbound that gets replies, from cold emails and follow-ups to...
Install
npx skills add coreyhaines31/marketingskills --skill cold-email -g -a claude-code -y- Repository
- coreyhaines31/marketingskills57.8k
- Category
- Writing
- Updated
- 5d ago
- License
- MIT
- Context cost
- Mediumabout 2,887 tokens
- Runs scripts
- No, instructions only
What it does
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.
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):
- Who are you writing to?, Role, company, why them specifically
- What do you want?, The outcome (meeting, reply, intro, demo)
- What's the value?, The specific problem you solve for people like them
- What's your proof?, A result, case study, or credibility signal
- 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.
