ai-cold-email
Skill0 starsChanged 6 months agoMITView on GitHub
Generate personalized cold outreach emails using AI
1 other project uses a version of this.
Adopted by
Most recently taken up by
- koinod/koino-skillsword for word, first seen May 22, 2026
Other versions1 project uses a version of this.
Word for word · 1
- koinod/koino-skills★ 7100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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 repository79 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ad-first-marketingSkill
- afrexai-community-growth-engineSkill
- agent-fleet-statusSkill
- agentgramSkill
- answeroverflowSkill
- answeroverflowSkill
- api-gatewaySkill
- apple-notesSkill
- autonomous-operatorSkill
- autonomous-revenueSkill
- brand-analyzerSkill
- brand-identitySkill
- brand-operatorSkill
- browser-useSkill
- byteroverSkill
- calendlySkill
- clawdcursorSkill
- clawd-provisionerSkill
- client-acquisitionSkill
- cold-email-writerSkill
- cold-outreachSkill
- Community ManagerSkill
- community-mod-packSkill
- competitive-ads-extractorSkill
- competitor-analyzerSkill
- content-engineSkill
- content-qa-scorerSkill
- content-repurposeSkill
- cron-automatorSkill
- daily-brief-generatorSkill
- deep-researchSkill
- elite-longterm-memorySkill
- email-responderSkill
- fathom-tele-tvSkill
- fleet-commanderSkill
- frontend-designSkill
- gogSkill
- himalayaSkill
- imsgSkill
- internet-marketingSkill
- klaviyoSkill
- knowledge-extractorSkill
- koino-frontendSkill
- lead-research-assistantSkill
- lead-scorerSkill
- macos-calendarSkill
- marketing-drafterSkill
- marketingSkill
- marketing-strategy-pmmSkill
- master-marketingSkill
- meeting-prepSkill
- moltbookSkill
- moltguardSkill
- objection-destroyerSkill
- ontologySkill
- pipeline-autopilotSkill
- marketing-ideasSkill
- proactive-agentSkill
- proposal-generatorSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
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 39
Before writing, analyze the inputs and build a prospect profile:
- Distinctive: line 69
No company pitch in the first email
- Distinctive: line 126
If you don't have a real case study, use an industry benchmark instead
- Distinctive: line 195
NEVER say "just following up" or "circling back"
- Distinctive: line 204
Before sending any email, verify:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
AI Cold Email Generator
Generate high-converting cold outreach emails personalized to your prospect. Uses the Observation > Question > Offer framework that consistently outperforms generic templates.
Usage
Provide the following about your prospect:
| Field | Required | Example |
| Prospect Name | Yes | "Sarah Chen" |
| Company | Yes | "Meridian Logistics" |
| Industry | Yes | "Third-party logistics / freight" |
| Pain Point | Yes | "Manual load matching wastes 15+ hours/week" |
| Your Name | Yes | "Alex Rivera" |
| Your Company | Yes | "FleetMind AI" |
| Your Offer | Yes | "AI-powered load matching platform" |
| Prospect's Role | Optional | "VP of Operations" |
| Recent Trigger | Optional | "Just expanded to 3 new warehouses" |
| Mutual Connection | Optional | "Met at FreightWaves LIVE" |
Output
You will receive 3 email variants plus a 3-touch follow-up sequence.
Step 1: Research & Personalization
Before writing, analyze the inputs and build a prospect profile:
- Observation: What specific, verifiable thing can you reference about the prospect or their company? (recent news, job change, company growth, public statement, industry trend affecting them)
- Question: What genuine question could you ask that demonstrates you understand their world?
- Offer: What specific, low-commitment value can you provide? (not "let's hop on a call" -- something they can use immediately)
Step 2: Generate 3 Email Variants
Variant A: The Short Punch (50-75 words)
Structure:
Subject: [Observation-based, no clickbait, under 6 words]
[First name],
[1 sentence: specific observation about their company/role]
[1 sentence: question that implies you understand their pain]
[1 sentence: concrete offer with zero commitment]
[Signature]Rules:
- No "I hope this finds you well"
- No "I wanted to reach out"
- No company pitch in the first email
- Subject line references THEM, not you
- Total email under 75 words
Variant B: The Value Lead (100-150 words)
Structure:
Subject: [Question format referencing their specific situation]
[First name],
[Observation paragraph: 2 sentences max. Reference something specific
about their company, industry move, or public content. Show you did
homework.]
[Bridge: 1 sentence connecting their situation to a pattern you've seen]
[Value: 2-3 sentences describing a specific insight, benchmark, or
framework relevant to their pain point. Give this away for free.]
[Soft CTA: Ask a question, don't demand a meeting]
[Signature]Rules:
- Lead with value they can use TODAY even if they never respond
- The insight should be genuinely useful, not a teaser
- CTA is a question, not a calendar link
Variant C: The Case Study Drop (150-200 words)
Structure:
Subject: [Result] for [similar company/role]
[First name],
[1 sentence observation about their specific challenge]
[2-3 sentence mini case study: "We worked with [similar company type]
who had [same pain point]. They were spending [X hours/dollars] on
[manual process]. After [your approach], they [specific result with
numbers].]
[1 sentence: what made their situation similar to the prospect's]
[Offer: share the full breakdown, a relevant resource, or a specific
recommendation -- NOT just "let's chat"]
[Signature]Rules:
- Case study must be from the same industry or analogous situation
- Include at least one specific number (hours saved, % improvement, dollars)
- If you don't have a real case study, use an industry benchmark instead
- CTA offers something tangible
Step 3: Subject Line Variations
Generate 5 subject lines for each variant (15 total), following these rules:
- Under 6 words
- No ALL CAPS
- No exclamation marks
- No "Quick question" or "Touching base"
- At least 2 should reference the prospect's company or situation specifically
- At least 1 should be a question
- At least 1 should reference a number or result
Step 4: Follow-Up Sequence
Follow-Up 1 (Day 3): The Bump + New Value
Subject: Re: [original subject]
[First name],
[1 sentence: reference original email without "just following up"]
[New value: share a relevant article, data point, or insight they
would genuinely find useful -- even if they never buy from you]
[Restate soft CTA differently than the first email]Follow-Up 2 (Day 7): The Pattern Interrupt
Subject: [Something unexpected -- industry hot take, contrarian opinion,
or humor relevant to their world]
[First name],
[2-3 sentences: share a genuine perspective on their industry that
shows you think about this space deeply. This should NOT be a pitch.
It should be something they'd forward to a colleague.]
[1 sentence: tie it back to how this relates to their specific situation]
[CTA: even softer -- "curious if you see it the same way"]Follow-Up 3 (Day 14): The Clean Break
Subject: Re: [original subject]
[First name],
[2-3 sentences: acknowledge they're busy, provide one final piece of
value (a resource, benchmark, or tool recommendation), and give them
a clean exit]
[Something like: "If the timing isn't right, no worries at all. But
if [pain point] becomes a priority, here's where to find me: [link]"]Rules for all follow-ups:
- NEVER say "just following up" or "circling back"
- Each follow-up must add NEW value, not just remind them you exist
- Tone should get progressively more casual, not more desperate
- The breakup email should leave them thinking "that person was genuinely helpful"
Quality Checklist
Before sending any email, verify:
- Opens with something about THEM, not about you
- No jargon or buzzwords ("synergy", "leverage", "circle back")
- A stranger could read this and learn something useful
- CTA requires less than 60 seconds of their time to respond
- You'd actually want to receive this email yourself
- Subject line would make you curious enough to open
- No more than 1 link in the entire email
- Reads well on mobile (short paragraphs, no walls of text)
- Specific to THIS prospect -- not a template with [brackets] filled in
- Follow-ups each add genuinely new value
Anti-Patterns (Never Do These)
| Bad | Why | Do Instead |
| "I hope this email finds you well" | Generic, wastes their time | Jump straight to the observation |
| "We're the leading provider of..." | Nobody cares about your ranking | Show what you did for someone like them |
| "Would love to pick your brain" | You're asking, not giving | Offer a specific insight first |
| "Let me know if you'd like to hop on a quick call" | Too much commitment for a cold email | Ask a question they can answer in 1 sentence |
| Sending the same template to 500 people | Low conversion, damages reputation | Batch by persona, personalize the observation |
| Following up 5+ times | Desperation kills deals | 3 follow-ups max, then move on |
Powered by KOINO Capital -- AI-powered business systems that close deals while you sleep.
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.

