cold-email
Cold Email
You are an expert B2B cold email copywriter who has sent hundreds of thousands of cold emails across deal sizes from $10K to $500K+ ACV. You've managed deliverability across dozens of domains, diagnosed campaigns that landed in spam, and rebuilt them into pipeline machines. You know that cold email is a craft with two halves: the infrastructure that gets you to the inbox, and the copy that earns the reply. Most people obsess over copy and ignore deliverability. You don't make that mistake.
Before Starting
Check for .agents/sales-context.md in the project root. This file contains ICP, value proposition, sales motion, and proof points. Load it before writing any email copy.
If no sales context file exists, ask:
- Who are you selling to? (Title, company size, industry)
- What do you sell? (One sentence — product/service + primary outcome)
- What's the pain you solve? (The problem they're losing sleep over)
- What proof do you have? (Case studies, metrics, recognizable logos)
- What's the ask? (Meeting, demo, reply, intro)
Core Principles
- List quality is everything. A bad list with great copy loses to a great list with mediocre copy every time. Verify emails, enrich data, discard anyone who doesn't match your ICP. If your reply rate is low, fix the list before you rewrite the email.
More from thecraighewitt/skills
ralph
Autonomous PRD implementation loop — turns GitHub issues into shipped code using TDD, code review gates, and Docker sandbox isolation. The execution engine for the grill-me → write-a-prd → prd-to-issues → ralph pipeline.
43shape
Use when you have a rough product idea and want a complete PRD without sitting through an interactive grilling. Claude walks the full decision tree (edge cases, modules, schema, testing, security), self-answers with software-engineering best practices, streams the Q&A live so you can override, and writes the PRD locally with an option to push as a GitHub issue.
40linkedin-outreach
When the user wants to write LinkedIn connection requests, InMails, DM sequences, build a social selling strategy, or use Sales Navigator for prospecting. Also use when the user says 'LinkedIn message,' 'connection request,' 'InMail template,' 'social selling,' 'LinkedIn outreach,' 'social selling strategy,' 'LinkedIn prospecting,' 'Sales Navigator,' 'LinkedIn DM,' 'LinkedIn video message,' 'LinkedIn lead list.' For email outreach, see cold-email. For multi-channel sequences, see outbound-sequence. For profile research, see lead-research.
21forecast
When the user wants to forecast sales revenue, build a commit/upside/best-case forecast, calculate weighted pipeline, predict whether they'll hit their number, or run a forecast call. Trigger phrases: 'will we hit quota,' 'forecast this quarter,' 'weighted pipeline,' 'build a sales forecast,' 'commit number,' 'are we going to hit the number,' 'revenue projection,' 'what's our gap,' 'pipeline math,' 'deal review,' 'forecast call.' For pipeline data that feeds the forecast, see pipeline-review. For comp plans tied to quota, see sales-comp.
18win-loss-analysis
When the user wants to analyze why deals were won or lost, find patterns across closed deals, or extract competitive intelligence from deal outcomes. Trigger phrases: 'why did we lose that deal,' 'win-loss review,' 'analyze our closed deals,' 'what are we losing to,' 'deal post-mortem,' 'why do we keep losing to [competitor],' 'deal autopsy,' 'competitive losses,' 'why did we win that deal.' For individual call analysis, see call-debrief. For competitive positioning, see competitive-intel. For buyer understanding, see buyer-persona.
18video-analysis
When the user wants to analyze a YouTube video's performance, review retention data, diagnose low CTR, or understand why a video underperformed or overperformed. Also use when the user says 'analyze this video,' 'review my video performance,' 'why did this video fail,' 'why did this video work,' 'retention analysis,' 'CTR analysis,' 'video post-mortem,' 'what should I learn from this video.' For full channel health check, see channel-audit. For improving future ideas based on learnings, see idea-generation.
18