cold-email
Skill1 starsChanged 3 months agoMITView on GitHub
Write a single first-touch cold email — hooks, structure, subject lines — using StoryBrand roles and a Proof/Promise/Plan close. Trigger on cold email, outreach email, prospecting email, or subject lines and hooks for a cold prospect. ROUTING - recipient has a workspace record but no active pipeline stage, use email-composer; active pipeline stage, use follow-up-nurture. No record at all = this skill.
101 other projects use a version of this.
Adopted by
Most recently taken up by
- atpaawej/opencode-skillpacktheir own version, first seen Nov 16, 2026
- JulyLay/cold-emailtheir own version, first seen Nov 16, 2026
- martinbattaglia-commits/Claude-skillstheir own version, first seen Nov 16, 2026
- AlejandroGodius/claude-skillstheir own version, first seen Nov 16, 2026
- yotamwiesel/claude-skillstheir own version, first seen Nov 16, 2026
- revnu-app/revnu-plugintheir own version, first seen Nov 8, 2026
Used with
Projects with it also use free-tools, popups and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CesarjoquinSkillfree-tools
When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.
Also in 25 projects that use this
CesarjoquinSkillpopups
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.
Also in 23 projects that use this
coreyhaines31Skillmarketing-council
When the user wants several expert takes on a marketing decision, or asks what a famous marketer would say about it: a simulated board (Seth Godin, David Ogilvy, April Dunford, Byron Sharp, and more), each grounded in their documented frameworks, where they disagree, and a recommendation. To execute, hand off to the relevant skill.
Also in 18 projects that use this
Hussain-ElfalahSkillandreessen
Also in 4 projects that use this
Hussain-ElfalahSkillbusiness-investment-advisor
Also in 4 projects that use this
roerohanSkillemails
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 outreach emails, see cold-email. For in-app onboarding, see onboarding.
Also in 24 projects that use this
- +5 more from Cesarjoquin
- +1 more from Hussain-Elfalah
Other versions101 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 101
- coreyhaines31/marketingskills★ 61ksame name
- LeoYeAI/openclaw-marketing-skills★ 1ksame name
- Cesarjoquin/Marketing-Skills★ 190same name
- b1rdmania/ghostclaw★ 91same name
- LOGIN-TB/claude-skills★ 82same name
- open-fox/agents★ 55same name
- mia-ppp/PMM-Skills★ 54same name
- SZcalligrapher/slash-skills-subscription★ 32same name
- roerohan/skills★ 29same name
- Mikefluff/skills★ 26same name
91 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository47 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- access-transfer-trackerSkill
- ai-3d-generatorSkill
- ai-asset-generatorSkill
- ai-demo-builderSkill
- apple-grade-designSkill
- brand-guide-builderSkill
- client-onboardingSkill
- cold-email-campaignSkill
- company-teardownSkill
- competitive-ads-extractorSkill
- content-calendarSkill
- content-repurposerSkill
- content-research-writerSkill
- content-strategySkill
- daily-briefSkill
- discovery-call-prepSkill
- email-composerSkill
- follow-up-nurtureSkill
- gbp-local-seoSkill
- hormozi-100m-leadsSkill
- interactive-website-builderSkill
- invoice-trackerSkill
- lead-flow-verifierSkill
- lead-scraperSkill
- mcp-integrationSkill
- meeting-listenerSkill
- post-purchase-email-seriesSkill
- productization-journalSkill
- proposal-generatorSkill
- prospect-workupSkill
- regulated-copy-complianceSkill
- retainer-reportingSkill
- review-managerSkill
- scroll-demo-builderSkill
- seo-auditSkill
- site-launch-cutoverSkill
- site-qa-checklistSkill
- social-media-auditorSkill
- social-media-managerSkill
- social-video-producerSkill
- stylized-3d-worldbuildingSkill
- video-analyzerSkill
- web-researchSkill
- website-builderSkill
- weekly-client-checkinSkill
- welcome-email-seriesSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 94 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Write cold emails that feel hand-crafted, hyper-specific, and impossible to ignore.
- Distinctive: line 34
Ask for anything missing:
- Distinctive: line 41
If given a rough draft, extract the core insight and rebuild with the structure below — do not just polish.
- Distinctive: line 46
Every cold email follows this sequence:
- Distinctive: line 68
Write like a sharp human, not a marketer.
- Distinctive: line 80
No exclamation points, no ALL CAPS
- Distinctive: line 81
No spam triggers ("Free", "Guaranteed", "Act Now", "Limited Time")
- Distinctive: line 104
Follow-ups after this first touch → follow-up-nurture
“Common” is measured: kept by at least 6 in 10 of the 94 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Cold Email
Write cold emails that feel hand-crafted, hyper-specific, and impossible to ignore. Act as a senior outbound strategist for service businesses and agencies.
Core philosophy
Cold emails fail because they make the sender the hero. Never do that. Apply StoryBrand roles (Donald Miller's framework — attributed once, used throughout):
- Prospect = the hero
- Their problem = the villain
- You = the quiet, confident guide who noticed something
- Your offer = a low-stakes first step, not a pitch
Hard rules (non-negotiable)
- Under 75 words. This cap wins over any other length guidance anywhere.
- Personalized — the email should read like it could only have been written for this one business. Their city, their competitor, their specific gap.
- One clear CTA. Exactly one ask, low-friction.
- Secondary domains only. Cold email never sends from the primary business domain — protect its deliverability reputation. Use lookalike secondary domains warmed up for outbound.
- Drafts go to the founder for review; the agent never sends.
Before you write
Ask for anything missing:
- Who is the prospect? (business name, industry, location)
- What specific observation is the hook based on?
- What is the CTA/offer? (audit, call, resource, question)
- Has the sender ever spoken to this person?
If given a rough draft, extract the core insight and rebuild with the structure below — do not just polish.
Email structure
Every cold email follows this sequence:
- Hook — a specific, real observation. Something you "noticed" or "found." Never open with "I" or a compliment.
- Problem — name the villain. Not them personally — the thing costing them business. Use numbers, seasons, local detail.
- Stakes — one sentence. What losing looks like. Real, not dramatic.
- Credibility (Proof) — one sentence. A specific, TRUE result you have produced. Specificity = believability. Never fabricate a number.
- CTA (Promise + Plan) — free, fast, clearly valuable. State exactly what they GET ("a free audit showing the 3 biggest issues") and how easy it is ("5 minutes to review, zero commitment"). "No pitch" language removes resistance.
- Sign-off — first name only. No "Best regards."
Proof/Promise/Plan, compressed
- Proof = the credibility line (one specific result)
- Promise = what the recipient gets by responding (inside the CTA)
- Plan = how easy the next step is (inside the CTA framing)
Tone rules
- Write like a sharp human, not a marketer.
- Short sentences. One idea per line. White space is a feature.
- Banned: "synergy," "leverage," "solutions," "I wanted to reach out," "hope this finds you well," "circle back," "touch base," and all filler.
- Specificity beats cleverness every time.
Subject lines
Written LAST, after the body. Principle: curiosity, not hype — it should feel like something a colleague sent, not an ad.
- Under 7 words
- No exclamation points, no ALL CAPS
- No spam triggers ("Free", "Guaranteed", "Act Now", "Limited Time")
- Reliable shapes: a question about their business ("quick question about
<business>"), a specific observation ("your<city>Google listing"), a named gap ("<competitor>is outranking you")
Output format
Subject: [subject line]
[email body]
[sign-off]Below the email, add a 2-4 sentence Strategy Note: which hook pattern and why, which villain you named, why the CTA is framed as it is. Then offer: "Want a 3-part follow-up sequence, or a different angle?"
Routing
- Recipient already in the pipeline with an active stage → follow-up-nurture
- Known contact (client, vendor, partner), no sales stage → email-composer
- Follow-ups after this first touch → follow-up-nurture
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

