cmj-hub Cold Email — JMC Outreach Craft Skill
Comprehensive cold email orchestrator for B2B operators. Anchors every output on a Pain Signal Profile (not demographics) and forces the output into a shape you can ship.
Quick Reference
| Slash | What it does |
|---|---|
/cold-email |
Interactive mode — detect intent, route to a sub-skill |
/cold-email write |
Draft a single signal-anchored cold email (<90 words, binary CTA) |
/cold-email sequence |
Design a 3-touch or 5-touch follow-up sequence |
/cold-email audit |
30-point outbound program audit (infra / targeting / messaging / ops) |
/cold-email nurture |
5-email nurture stream with route-to-sales trigger |
/cold-email deliverability |
15-point pre-campaign domain health check |
/cold-email subject |
Subject-line patterns by framework (pain / curiosity / proof / direct) |
Core principles (the JMC stance)
- A cold email is a hire — not a search query. Every prompt anchors on a Pain Signal Profile, names the constraint, and forces the output into a shape you can ship.
- No demographics in the opener. "VP of Marketing at Series B SaaS" isn't a signal. "Just posted a job for a Demand Gen Lead" is.
- Binary CTAs only. "Worth 15 minutes Thursday?" not "Let me know if you'd like to learn more."
- <90 words for the first touch. Anything longer signals desperation.
- One specific ask per email. Stack-ranked asks confuse buyers.
- No "Hope you're well" / "Just bumping this". Banned openers.
Workflow router
When invoked, detect the user's intent and route to a sub-skill:
| User says | Route to |
|---|---|
| "Write a cold email to..." | skills/cold-email-craft |
| "Build a 3-touch / follow-up sequence" | skills/cold-email-craft (sequence mode) |
| "Audit my outbound program" | skills/cold-email-audit |
| "Design a nurture stream" | skills/cold-email-nurture |
| "Is my domain ready to send?" | skills/cold-email-deliverability |
| "Suggest subject lines" | skills/cold-email-subject-lines |
If intent is ambiguous, ask one clarifying question — never two.
Variables (sub-skills inherit these)
The core framework operates on six variables. Capture them once, reuse across all sub-skills:
| Variable | Source | Example |
|---|---|---|
firstName |
Recipient list | Sarah |
role |
LinkedIn / CRM | VP of Demand Gen |
company |
Same | Acme Cloud |
signal |
Public signal — job post, funding, product launch, leadership change | "Just posted 'Senior Demand Gen Lead' role on LinkedIn 4 days ago" |
pain |
Pain Signal Profile — what the signal implies | "Pipeline gap; existing demand gen motion isn't producing enough SQLs" |
evp |
Your one-line value prop in their words | "We help Series-B SaaS hit pipeline targets without hiring 2 more SDRs" |
senderName |
You | Jay |
If any are missing, ask the user — don't fabricate.
References
Load these on demand for deeper context:
references/jmc-framework.md— The full JMC cold email frameworkreferences/banned-patterns.md— Lines / openers / closes that failreferences/binary-ctas.md— 30 binary CTA patternsreferences/psp-anchors.md— How to derive signal → pain → EVP
Sub-skills
skills/cold-email-craft— Single email + 3-touch sequence draftingskills/cold-email-audit— 30-point outbound program auditskills/cold-email-nurture— 5-email nurture stream designskills/cold-email-deliverability— 15-point pre-campaign domain healthskills/cold-email-subject-lines— Subject-line patterns by framework
Specialist agents
agents/cold-email-reviewer— Quality scorer (0-100) against frameworkagents/cold-email-deliverability-auditor— DNS/reputation specialist
Free hosted version
The same job runs in a browser, no install and no key: Cold Email Linter