cold-email
Skill1 starsChanged 2 months agoMITView on GitHub
Run the full pipeline to produce one ready-to-send internship cold email for one person at one company — research, contact, match, draft, edit, QA. Use whenever an email to a new company is needed. Produces a draft for a human to send; never sends anything.
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 repository37 other files it gives its agents.
- wsb-data-pipelineSkill
- docx-exportSkill
- harvard-mdxSkill
- humanise-docx-reportSkill
- make-pdfSkill
- bom-builderSkill
- ring-testSkill
- batch-draftSkill
- cv-intakeSkill
- cv-upgradeSkill
- find-contactSkill
- followupSkill
- humanize-emailSkill
- log-outreachSkill
- outreach-statusSkill
- target-researchSkill
- erc-statusSkill
- log-sessionSkill
- score-auditSkill
- submission-checkSkill
- sumo-statusSkill
- trial-runSkill
- vr-statusSkill
- academic-registerSkill
- aviation-data-sourcesSkill
- business-frameworksSkill
- consultancy-registerSkill
- excel-deliverablesSkill
- forecasting-methodsSkill
- operations-frameworksSkill
- secondary-data-sourcesSkill
- archive-indexSkill
- event-proposalSkill
- meeting-minutesSkill
- read-boxnoteSkill
- captureSkill
- new-scriptSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 94 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Stop and say so if any of these fail:
- Very specific: line 24
Dossier: If shared/companies/<slug>.md is missing or older than a month, run /target-research <company>.
- Very specific: line 26
Contact: If the dossier has no verified contact, run /find-contact <company>.
- Distinctive: line 69
Never send: No mail client, no SMTP, no automation of the send step.
- Very specific: line 70
Never draft for a profile containing TBD.
- Very specific: line 71
Never draft against a pattern or unverified address.
- Distinctive: line 73
Never mix the two people's evidence.
- Distinctive: line 74
Every claim traces to a source.
- Very specific: line 75
If any step fails, report where it failed and what would unblock it.
“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, the full pipeline
Usage: /cold-email "<Person Name>" Space42
Produces one draft at <person>/drafts/YYYY-MM-DD-<company>.md with status: ready, for a human to read and send.
Preconditions
Stop and say so if any of these fail:
<person>/profile.mdexists and contains noTBDin the fields the email needs- Every open question in that sender's
profile.mdis answered — role type (internship versus permanent), public profile URL, target sector, and any domain exposure the pitch leans on. Both the target list and the email structure depend on them - The company is on
shared/targets.md - The daily cap has room: 5 first contacts per person per day
- The tracker does not already show this company contacted by this person
Steps
- Dossier. If
shared/companies/<slug>.mdis missing or older than a month, run/target-research <company>. - Contact. If the dossier has no
verifiedcontact, run/find-contact <company>. If nothing verifies, stop and report the alternative route. Do not draft against a guessed address. - Match. Spawn
profile_matcher. It picks one lead project, at most two supporting facts, names what to leave out, and does the gap analysis. If it returnsweakfit and recommends skipping, report that and stop. - Draft. Spawn
email_writerwith the dossier, the match report, the person's profile, evidence, signature and voice section. Under 150 words. Three ranked subject lines. Status:draft. - Edit. Spawn
editor. Cuts length, strips AI tells, fixes the ask, runs the swap test on paragraph 1, verifies facts survived unchanged. Status:edited. If it sends the draft back, loop once through step 4 and no further — a draft that fails twice has a wrong angle, which is a decision for the human. - QA. Spawn
send_qa. Full checklist. Every blocking issue goes back to the owning agent. On pass, status:ready. - Update the tracker with the company, contact, verification state and status.
- Hand off. Show the human the final email in full — subject, body, signature — the word count, the risks, and the exact next step.
Output format
## Ready to send: <person> → <company>
**To:** <name> <<address>> · <title>
**Verified:** <source>
**Subject:** <subject>
---
<the complete email, exactly as it should be sent>
---
**Words:** <n>
**Angle:** <one line>
**Links:** <URLs, each confirmed to resolve>
**Attachments:** none
**Before you send**
- <anything worth knowing>
**After you send**
1. Move the file to `<person>/sent/`
2. Set `sent:` in the frontmatter and update the tracker
3. Follow-up due <date>. One follow-up onlyRules
- Never send. No mail client, no SMTP, no automation of the send step. Not once.
- Never draft for a profile containing
TBD. - Never draft against a
patternorunverifiedaddress. - One email per company per person.
- Never mix the two people's evidence. Read only the folder of the person named in the command.
- Every claim traces to a source. If a sentence needs a number nobody has, the sentence goes without it.
- If any step fails, report where it failed and what would unblock it. Do not push a broken draft through to
ready.
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.

