cold-email
Writes and runs B2B cold outbound: emails and follow-ups, sending setup and deliverability, LinkedIn and multichannel cadences, reply handling.
- Kind
- Skill
- Works with
- Claude Code
- Source
- Marketing Skills (Corey Haines) @ 88c79f6528a9
- Path
- skills/cold-email/SKILL.md
- Jobs
- Documentation, Automation
- Topics
- Email & newsletters, Sales & CRM
Credit
- Made by
- coreyhaines31
- Original
- github.com/coreyhaines31/marketingskills/blob/88c79f6528a9347…
- License
- MIT
Listed by Skill Manifest; not made by us.
InstallInstall it with npx.
npx skills add coreyhaines31/marketingskills --skill cold-email
Install factsScanned 2 Nov 2026
- Adds
- .claude/skills/cold-email/ (the skill folder)
- 10 file(s) the skill refers to
- Runs scripts
- None found
- Uses the network
- None found
- Needs secrets
- None found
- Source revision
- 88c79f6528a9
- Licence
- MIT
- Last activity
- 31 Oct 2026
- Review
- Reviewed
Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.
- Only the main file is read; other files in the folder are not scanned
# 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 …