Best for
- Use when the user mentions 'cold email,' 'cold outreach,' 'prospecting emails,' 'SDR emails,' 'sales emails,' 'first touch email,' 'follow-up sequence,' or 'email prospecting.
alirezarezvani/claude-skills/marketing-skill/skills/cold-email/SKILL.md
When the user wants to write, improve, or build a sequence of B2B cold outreach emails to prospects who haven't asked to hear from them. Use when the user mentions 'cold email,' 'cold outreach,' 'prospecting emails,' 'SDR emails,' 'sales emails,' 'first touch email,' 'follow-up sequence,' or 'email prospecting.' Also use when they share an email draft that sounds too sales-y and needs to be humanized. Distinct from email-sequence (lifecycle/nurture to opted-in subscribers) — this is unsolicited
Decision brief
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.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/alirezarezvani/claude-skills --skill "marketing-skill/skills/cold-email"Inspect the Agent Skill "cold-email" from https://github.com/alirezarezvani/claude-skills/blob/aa8d778811a557a2c28ccadda4cf3d0bd028a4cc/marketing-skill/skills/cold-email/SKILL.md at commit aa8d778811a557a2c28ccadda4cf3d0bd028a4cc. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Check for context first: If .claude/product-marketing-context.md exists, read it before asking questions.
Who are they at this company? (Role, seniority — affects how they write)
Who is the target? (Job title, company type, company size)
What's the goal of the first email? (Book a call? Get a reply? Get a referral?)
When they need a single first-touch email or a template for a segment.
Permission review
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 93/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 23,781 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
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.
Check for context first:
If .claude/product-marketing-context.md exists, read it before asking questions.
Gather this context:
When they need a single first-touch email or a template for a segment.
references/frameworks.md)When they need a multi-email sequence (typically 4-6 emails).
When they have an active sequence and want to improve it.
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.
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.
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.
The opener should be about them — their situation, their problem, their context. Not about you or your product.
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.
Adjust tone, length, and specificity based on who you're writing to:
| Audience | Length | Tone | Subject Line Style | What Works |
|---|---|---|---|---|
| C-suite (CEO, CRO, CMO) | 3-4 sentences | Ultra-brief, peer-level, strategic | Short, vague, internal-looking | Big problem → relevant proof → one question |
| VP / Director | 5-7 sentences | Direct, metrics-conscious | Slightly more specific | Specific observation + clear business angle |
| Mid-level (Manager, Analyst) | 7-10 sentences | Practical, shows you did homework | Can be more descriptive | Specific problem + practical value + easy CTA |
| Technical (Engineer, Architect) | 7-10 sentences | Precise, no fluff | Technical specificity | Exact problem → precise solution → low-friction ask |
The higher up the org chart, the shorter your email needs to be. A CEO gets 100+ emails per day. Three sentences and a clear question is a gift, not a slight.
The goal of a subject line is to get the email opened — not to convey value, not to be clever, not to impress anyone. Just open it.
The best cold email subject lines look like internal emails. They're short, slightly vague, and create just enough curiosity to click.
| Pattern | Example | Why It Works |
|---|---|---|
| Two or three words | quick question | Looks like an actual email from a colleague |
| Specific trigger + question | your TechCrunch piece | Specific enough to not look like spam |
| Shared context | re: Series B | Feels like a follow-up, not cold |
| Observation | your ATS setup | Specific, relevant, not salesy |
| Referral hook | [mutual name] suggested I reach out | Social proof front-loaded |
Most deals happen in follow-ups. Most follow-ups are useless. The difference is whether the follow-up adds value or just creates noise.
| Send Day | Gap | |
|---|---|---|
| Email 1 | Day 1 | — |
| Email 2 | Day 4 | +3 days |
| Email 3 | Day 9 | +5 days |
| Email 4 | Day 16 | +7 days |
| Email 5 | Day 25 | +9 days |
| Breakup | Day 35 | +10 days |
Gaps increase over time. You're persistent but not annoying.
Each follow-up must have a new angle. Rotate through:
Never "just check in." "Just following up to see if you had a chance to read my last email" is a waste of both your time and theirs. If you have nothing new to add, don't send the email.
Don't reference all previous emails. Each follow-up should stand alone. The prospect doesn't remember your earlier emails. Don't make them scroll.
The last email in a sequence should close the loop professionally. It signals this is the last one — which paradoxically increases reply rate because people don't like loose ends.
Example breakup:
"I'll stop cluttering your inbox after this one. If [problem] ever becomes a priority, happy to reconnect — just reply here and I'll pick it up.
If there's someone else at [Company] I should speak with, a name would go a long way.
Either way — good luck with [whatever's relevant]."
See references/follow-up-playbook.md for full cadence templates and angle rotation guide.
These are not suggestions — they're patterns that mark you as a non-human and kill reply rates:
| ❌ Avoid | Why It Fails |
|---|---|
| "I hope this email finds you well" | Instant tell that this is templated. Cut it. |
| "I wanted to reach out because..." | 3-word delay before actually saying anything |
| Feature dump in email 1 | Nobody cares about features when they don't trust you yet |
| HTML templates with logos and colors | Looks like marketing, gets spam-filtered |
| Fake Re:/Fwd: subject lines | Feels deceptive — kills trust before the first word |
| "Just checking in" follow-ups | Adds no value, removes credibility |
| Opening with "My name is X and I work at Y" | They can see your name. Start with something interesting. |
| Social proof that doesn't connect to their problem | "We work with 500 companies" means nothing without context |
| Long-form case study in email 1 | Save it for follow-up when they've shown interest |
| Passive CTAs ("Let me know if you're interested") | Weak. Ask a direct question or propose a specific next step. |
A great email sent from a flagged domain never lands. Basics you need to have in place:
mail.yourdomain.com or outreach.yourdomain.com.See references/deliverability-guide.md for domain warmup schedule, SPF/DKIM setup, and spam trigger word list.
Surface these without being asked:
| Tool | Invocation | Output |
|---|---|---|
| Sequence analyzer | python3 scripts/email_sequence_analyzer.py sequence.json (no arg = embedded demo; - reads stdin) | Per-email 0-100 score across word count, reading level, personalization, CTA clarity, spam triggers, subject lines |
Run it on every drafted sequence before delivering: any email scoring below 70 gets rewritten against the flagged dimensions (spam triggers and CTA clarity first), then re-scored.
| When you ask for... | You get... |
|---|---|
| Write a cold email | First-touch email + 3 subject line variants + brief rationale for structure choices |
| Build a sequence | 5-6 email sequence with send gaps, subject lines per email, and angle summary for each follow-up — scored with email_sequence_analyzer.py before delivery |
| Critique my email | Line-by-line assessment + rewrite + explanation of each change |
| Write follow-ups only | Follow-up emails 2-6 with unique angles per email + breakup email |
| Analyze sequence performance | email_sequence_analyzer.py score report + diagnosis of where the sequence breaks (subject/body/CTA) + specific rewrite recommendations |
All output follows the structured communication standard:
Alternatives
coreyhaines31/marketingskills
When the user wants to figure out which marketing actually drives conversions and revenue, choose or interpret an attribution model, or reconcile conflicting numbers across tools. Also use when the user mentions "attribution," "attribution model," "first-touch vs last-touch," "multi-touch," "which channel drives revenue," "what's my real CAC," "my dashboards disagree," "Google/Meta says X but GA says Y," "media mix model," "MMM," "incrementality," "geo lift," "holdout test," "how did you hear ab
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold out
aaron-he-zhu/aaron-marketing-skills
Use when the user asks to "analyze my target audience", "build an audience profile for influencer targeting", "research a niche community", or "deep-dive a subculture before partnering with creators"; in audience mode produces demographic/psychographic profiles, a platform-priority matrix, named personas, and an influencer-selection criteria set, and in niche mode produces a community map, culture decode (language/norms/taboos), key-voice tiers, a Brand Fit Score, and a phased entry strategy. No
aaron-he-zhu/aaron-marketing-skills
Use it for marketing and sales tasks; the detail page covers purpose, installation, and practical steps.