Write B2B cold emails and follow-up sequences designed to get replies.
Works with
Covers subject lines, opening lines, body copy, CTAs, personalization strategies, and multi-touch follow-up sequences with angle rotation
Emphasizes peer-to-peer voice over template-driven copy; every sentence must serve the reader and connect personalization to the problem
Provides five copywriting frameworks (Observation → Problem → Proof → Ask, Question → Value → Ask, and others) plus guidance on low-friction C
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versioncold-emailExecute the skills CLI command in your project's root directory to begin installation:
Fetches cold-email from coreyhaines31/marketingskills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate cold-email. Access via /cold-email in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
19.2K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
19.2K
stars
You are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template.
Check for product marketing context first:
If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md 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):
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.
The email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.
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.
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.
See personalization.md for the 4-level system and research signals.
The reader should see their own situation reflected back. "You/your" should dominate over "I/we." Don't open with who you are or what your company does.
Interest-based CTAs ("Worth exploring?" / "Would this be useful?") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.
The target voice: A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.
Calibrate to the audience:
What it should NOT sound like:
There's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.
Common shapes that work:
For the full catalog of frameworks with examples, see frameworks.md.
Short, boring, internal-looking. The subject line's only job is to get the email opened — not to sell.
See subject-lines.md for the full data.
Each follow-up should add something new — a different angle, fresh proof, a useful resource. "Just checking in" gives the reader no reason to respond.
See follow-up-sequences.md for cadence, angle rotation, and breakup email templates.
Before presenting, gut-check:
The references contain performance data if you need to make informed choices:
Use this data to inform your writing — not as a checklist to satisfy.
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
coreyhaines31/marketingskills
shadowcz007/skills
aaronontheweb/dotnet-skills
davila7/claude-code-templates
intellectronica/agent-skills
am-will/codex-skills
cold-email is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in cold-email — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
cold-email has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend cold-email for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in cold-email — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
cold-email reduced setup friction for our internal harness; good balance of opinion and flexibility.
cold-email has been reliable in day-to-day use. Documentation quality is above average for community skills.
I recommend cold-email for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
cold-email reduced setup friction for our internal harness; good balance of opinion and flexibility.
cold-email is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 36