cold-outreach
Skill0 starsChanged 9 months agoMITView on GitHub
Write highly effective cold emails and LinkedIn messages to recruiters, hiring managers, founders, and engineers at target companies. Based on Ben Lang's proven cold outreach framework (Next Play). Use when the user wants to: (1) write a cold email to someone at a company they want to work for, (2) craft LinkedIn messages or InMail to recruiters or hiring managers, (3) reach out about unadvertised positions, (4) follow up on outreach or applications, (5) network with founders or executives for job opportunities, (6) prepare an outreach campaign to multiple companies. Triggers on: cold email, outreach, reach out to, contact recruiter, email founder, write to hiring manager, job email, networking email, LinkedIn message, InMail.
We split this skill into the rules it gives an agent
23 rules. 0 are common, 23 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 26 edited versions we read keep these.
23
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 and messages that get responses from recruiters, hiring managers, founders, and engineers.
- Distinctive: line 30
Ask the user for the information needed.
- Distinctive: line 40
Do you have specific accomplishments with numbers you can cite?
- Distinctive: line 44
If the user already provided this context, skip directly to drafting.
- Distinctive: line 60
Use the company website, job description, and recruiter profile to infer priorities.
- Distinctive: line 62
If those sources are missing, ask the user to provide them before drafting.
- Distinctive: line 66
Every effective cold email has exactly three parts:
- Distinctive: line 76
Under 200 words total: No exceptions. Brevity works on everyone.
- Distinctive: line 81
Sound human: Read it aloud. If it doesn't sound like you actually talk, rewrite it.
- Distinctive: line 83
No em dashes: Use commas or parentheses instead.
- Distinctive: line 84
High-level only: Avoid specific implementation details, or granular execution details.
- Distinctive: line 111
Before presenting the draft, check every message against these five failure modes.
- Distinctive: line 114
Buzzwords: - Remove all corporate language.
- Distinctive: line 116
Too vague: - Every claim needs specificity.
- Distinctive: line 117
Too granular: - If it dives into project-level details that are not too in depth for the first 200 word intro, strip it back to higher …
- Distinctive: line 118
Dishonest or spammy: - No fake personalization ("I've been a fan for years!" when they just found the company).
- Distinctive: line 126
Never: "Inquiry about opportunities" or "Following up on my application"
- Distinctive: line 130
When in doubt: the CEO/founder
- Distinctive: line 139
Wait 4-5 business days after initial email
- Distinctive: line 141
After 2 follow-ups with no response, move on
- Distinctive: line 165
Only suggest this approach when the user has time and the target company warrants the extra effort.
- Distinctive: line 176
If response rate is under 10%: revisit the five deadly sins, shorten emails, add more specificity, check targeting.
- Distinctive: line 180
Before any message is finalized, verify:
“Common” is measured: kept by at least 6 in 10 of the 26 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 Outreach
Write cold emails and messages that get responses from recruiters, hiring managers, founders, and engineers. Based on Ben Lang's framework (former Notion community lead, angel investor, creator of Next Play).
Announce at start: "I'm using the cold-outreach skill to help craft your message."
Core Truth
Cold email works. You can email any company regardless of posted jobs, location requirements, or stated credentials. Startups regularly make exceptions. The gap between effective and ineffective cold emails is enormous - this skill keeps you on the effective side.
Prerequisite: Cold outreach works best when you are genuinely competent at something valuable AND have demonstrated that competency. This skill amplifies real credibility; it cannot create it.
Workflow
Crafting a cold outreach message involves these steps:
- Gather context (who, what company, what role/goal)
- Identify the user's strongest relevant credentials and match them to the target's needs
- Draft the message using the three-part structure
- Validate against the five deadly sins
- Finalize with subject line and send strategy
Step 1: Gather Context
Ask the user for the information needed. Do not ask all at once - start with the essentials:
Essential (ask first):
- Who are you reaching out to? (name, title, company)
- What is the goal? (specific role, general interest, informational)
- What is your most relevant experience for this company/role?
If not provided, ask as follow-up:
- What does this company do? What stage are they at?
- How did you find them? (funding announcement, job board, referral, etc.)
- Do you have specific accomplishments with numbers you can cite?
- Provide links to: company website, job description (if any), and recruiter or hiring manager profile (LinkedIn or similar).
- What are they likely hiring for or optimizing right now?
If the user already provided this context, skip directly to drafting. If company or recruiter details are missing, prompt for them before drafting.
Step 2: Identify Strongest Credentials
Extract and sharpen the user's top 2-3 credentials. Apply these rules:
Make abstract concrete:
- "I drove results" -> "I helped increase conversion rate from 2% to 8%"
- "I work with startups" -> "I built payment systems at Stripe and billing tools at Notion"
- "Experienced engineer" -> "Built systems handling 300k+ TPS at Amazon"
Use numbers where they add clarity: revenue impact, user counts, performance metrics, team size, time saved. Keep them broad and avoid project-specific minutiae.
Prioritize relevance: Choose credentials that map directly to what the target company needs, not the most impressive ones in general.
Match to the target:
- Use the company website, job description, and recruiter profile to infer priorities.
- Select 2-3 background points that align with what they are hiring for or optimizing.
- If those sources are missing, ask the user to provide them before drafting.
Step 3: Draft Using the Three-Part Structure
Every effective cold email has exactly three parts:
Part 1 - Who you are: One sentence with your most relevant credential. Part 2 - Why you're reaching out: One sentence stating your purpose clearly and directly. Part 3 - Why they should care: 2-3 bullet points with concrete, specific accomplishments.
End with ONE clear ask. See references/email-examples.md for proven examples.
Hard Rules
- Under 200 words total. No exceptions. Brevity works on everyone.
- One clear ask at the end. Make it easy to say yes.
- Good: "Worth a 15-minute call next week?"
- Good: "Can I send over my portfolio?"
- Bad: "Let me know if you're interested" (vague, no action)
- Sound human. Read it aloud. If it doesn't sound like you actually talk, rewrite it.
- Use bullets for accomplishments. Easier to scan than paragraphs.
- No em dashes. Use commas or parentheses instead.
- High-level only. Avoid specific implementation details, or granular execution details. Keep success metrics showing goals achieved. Show competency and confidence without being boring.
Output Format
Generate the email in this structure:
Subject: [under 50 characters, relevant and direct]
Hi [Name],
[One sentence: who you are with most relevant credential]
[One sentence: why you're reaching out]
[2-3 bullets: why they should care, with high-level relevant accomplishments]
[One sentence: clear ask]
Best,
[User's name]Total: 100-150 words. See references/email-examples.md for complete examples.
Step 4: Validate Against the Six Deadly Sins
Before presenting the draft, check every message against these five failure modes. If any apply, fix before showing the draft.
- Too long - Over 200 words? Cut ruthlessly. Nobody reads unsolicited long emails.
- Buzzwords - Remove all corporate language. "Executed strategic initiatives" -> "built a tool that cut processing time by 40%". Remove buzzwords, then remove them again.
- No clear ask - Missing a specific action you want them to take? Add one.
- Too vague - Every claim needs specificity. Numbers, company names, concrete examples. No abstractions.
- Too granular - If it dives into project-level details that are not too in depth for the first 200 word intro, strip it back to higher level impact with the right metrics and actions.
- Dishonest or spammy - No fake personalization ("I've been a fan for years!" when they just found the company). It's fine to say "I saw you just raised a Series B."
Step 5: Subject Line and Send Strategy
Subject lines - Under 50 characters, relevant:
- "Engineer interested in your AI product"
- "Designer with fintech experience"
- "Quick question about [role]"
- Never: "Inquiry about opportunities" or "Following up on my application"
Who to email:
- For specific roles: the hiring manager (find on LinkedIn)
- When in doubt: the CEO/founder
- Small startups (<20 people): always the CEO
Finding email: Try firstname@company.com first (works ~70% of the time). Use Hunter.io, RocketReach, Nymeria, or ContactOut. Check personal websites and social media bios.
When to send: Tuesday-Thursday, 8-10 AM in their timezone. Avoid Mondays and Fridays.
Follow-Up Strategy
- Wait 4-5 business days after initial email
- Send maximum 1-2 follow-ups total
- After 2 follow-ups with no response, move on
See references/email-examples.md for follow-up templates.
LinkedIn Variation
For LinkedIn connection requests or InMail, apply the same three-part structure but even shorter:
Connection request (300 character limit):
Hi [Name], I'm a [role] with [X years] in [domain]. Saw you're hiring for [role] at [Company]. Would love to connect and learn more.After connecting (wait 1-2 days, then message): Same three-part structure as email, but slightly more conversational. Keep under 150 words.
"Show, Don't Tell" Tactic
For standout outreach, demonstrate value instead of just listing credentials:
- "I spent 30 minutes analyzing your onboarding flow and found 3 bottlenecks. Happy to share."
- "I built a quick prototype showing how [approach] could work for your use case. Can demo if interested."
- "I reviewed your blog post on [topic] and identified an optimization that could improve performance by 30%."
Only suggest this approach when the user has time and the target company warrants the extra effort.
Volume and Expectations
Even perfect emails can go unanswered (bad timing, inbox overload, spam filters, not hiring right now). The solution is volume:
- Target 10-30 companies over several weeks
- Expect 10-30% response rate
- Even 1-2 responses can lead to interviews
- Track what works, iterate on what doesn't
If response rate is under 10%: revisit the five deadly sins, shorten emails, add more specificity, check targeting.
Quality Checklist
Before any message is finalized, verify:
- Under 200 words
- No buzzwords or corporate jargon
- ONE clear ask
- Specific examples with numbers
- Sounds like a real human wrote it
- No fake personalization
- Subject line under 50 characters
- Prepared for a positive response
Resources
references/email-examples.md
Proven cold email examples that got responses, organized by scenario (startup founder, recruiter, hiring manager, internal transfer). Also includes follow-up templates and LinkedIn message examples. Load when drafting to reference specific patterns.
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- shawnpang/startup-founder-skills★ 331same name
- runxhq/runx★ 97same name
- Infinite-Labs-AI/infinite-skills★ 43same name
- etrebels/claude-code-growth-os★ 21same name
- duncan-buildroom/profit-room-skills★ 18same name
- YannisKiefer/dark-psychology-skills★ 11same name
- SanketSapkal/founder-skills★ 10same name
- manfromtunis/melek-skills★ 9same name
- Maudeunfledged834/startup-founder-skills★ 8same name
- koinod/koino-skills★ 7same name
17 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.
Used alongsideProjects with it also use lead-qualify, yt-search 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.
kronus-techSkilllead-qualify
Score and qualify an inbound lead based on budget, timeline, technical fit, and engagement signals. Auto-invoked when user says "qualify this lead", "score this lead", "is this worth pursuing".
Also in 3 projects that use this
azuma520Skillyt-search
Search YouTube videos, get video metadata, and download subtitles/transcripts using yt-dlp. Use when the user wants to find videos, search YouTube, look up a YouTube channel, get video info, download captions, grab subtitles, or extract a transcript. Triggers include "找影片", "搜影片", "YouTube 搜尋", "抓字幕", "逐字稿", "search videos", "find videos on YouTube", "get subtitles", "video transcript", "youtube tutorial", "watch video about", "影片推薦", "有沒有影片", "教學影片". Make sure to use this skill whenever the user mentions YouTube, video search, subtitles, or transcripts — even if they don't explicitly say "yt-search".
Also in 3 projects that use this
DanderlionJerSkillproposal-generator
Generate customized sales proposals from template and customer data
Also in 3 projects that use this
indranilbanerjeeSkillcontent-repurpose
Repurpose one content piece into 10+ channel formats with drafts and a calendar. \"repurpose this blog post\"
Also in 3 projects that use this
AnthropicSkillpitch-deck
Populates investment banking pitch deck templates with data from source files. Use when: user provides a PowerPoint template to fill in, user has source data (Excel/CSV) to populate into slides, user mentions populating or filling a pitch deck template, or user needs to transfer data into existing slide layouts. Not for creating presentations from scratch.
Also in 3 projects that use this
indranilbanerjeeSkillcontent-engine
Draft content in brand voice through a gated pipeline: blogs, ads, emails. Brief only → content-brief. \"write a blog post about X\"
Also in 4 projects that use this
In this repository29 other files it gives its agents.
- .agents/skills/vercel-composition-patterns/AGENTS.mdAGENTS.md
- .agents/skills/vercel-react-best-practices/AGENTS.mdAGENTS.md
- agent-browserSkill
- ai-sdkSkill
- algorithmic-artSkill
- audit-websiteSkill
- before-and-afterSkill
- core-web-vitalsSkill
- find-skillsSkill
- frontend-designSkill
- mcp-builderSkill
- next-best-practicesSkill
- pdfSkill
- performanceSkill
- prdSkill
- programmatic-seoSkill
- ralphSkill
- seo-auditSkill
- skill-creatorSkill
- theme-factorySkill
- ui-ux-pro-maxSkill
- using-git-worktreesSkill
- vercel-composition-patternsSkill
- vercel-react-best-practicesSkill
- webapp-testingSkill
- web-design-guidelinesSkill
- continuous-claudemd-updatesSkill
- design-tasteSkill
- pr-review-handlerSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.

