
Cold Outreach
- 4 installs
- Updated February 15, 2026
- vijaykpatel/favorite_skills_and_plugins
Helps with ai & agent building tasks.
About
cold-outreach is a Claude Code skill for ai & agent building. It helps developers move faster with AI-assisted coding.
- cold-outreach
- AI & Agent Building
- AI-coding skill
Cold Outreach by the numbers
- 4 all-time installs (skills.sh)
- Ranked #13,349 of 16,556 AI & Agent Building skills by installs in the Skillselion catalog
- Data as of Jul 7, 2026 (Skillselion catalog sync)
npx skills add https://github.com/vijaykpatel/favorite_skills_and_plugins --skill cold-outreachAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 4 |
|---|---|
| Last updated | February 15, 2026 |
| Repository | vijaykpatel/favorite_skills_and_plugins ↗ |
What it does
Helps with ai & agent building tasks.
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:
1. Gather context (who, what company, what role/goal) 2. Identify the user's strongest relevant credentials and match them to the target's needs 3. Draft the message using the three-part structure 4. Validate against the five deadly sins 5. 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.
1. Too long - Over 200 words? Cut ruthlessly. Nobody reads unsolicited long emails. 2. Buzzwords - Remove all corporate language. "Executed strategic initiatives" -> "built a tool that cut processing time by 40%". Remove buzzwords, then remove them again. 3. No clear ask - Missing a specific action you want them to take? Add one. 4. Too vague - Every claim needs specificity. Numbers, company names, concrete examples. No abstractions. 5. 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. 6. 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.
Cold Outreach Examples and Templates
Proven examples and reusable templates organized by scenario. Reference these when drafting outreach messages.
Table of Contents
- Proven Examples That Got Responses
- Templates by Scenario
- Follow-Up Templates
- LinkedIn Templates
- Good vs Bad Comparisons
---
Proven Examples That Got Responses
Example 1: High Schooler to CEO (Niraj Pant to Evan Spiegel, Snapchat)
Extreme brevity. Three bullets. Worked.
Hey, my name's Niraj Pant.
I understand your time is valuable. I'll only write three bullet points.
- Programming since 8th grade.
- Have most experience working in Java/Obj-C/Android/iOS.
- Want to intern for Snapchat this summer as a high school junior.
How?Why it worked: Radically short. Specific tech stack. Bold one-word ask. Respects the reader's time by design.
Example 2: Copywriter to Startup Founder
Opens with genuine product praise, then pivots to a soft ask.
Hey Ryan - [product] is so good. Used it last week for [reason] and was
impressed (especially by how good the notification selection/timing is).
Question: how are you doing on copywriting at the moment?
Asking because I write for startups.
Don't want to blast you with a wall of text so re: work background, that's
mostly on the site in my email address. Happy to share a bunch of past work
if it would be helpful.Why it worked: Authentic product usage (not fake). Low-pressure ask. Offers proof without forcing it. Conversational tone.
Example 3: Engineer to Seed-Stage Startup
Classic three-part structure executed well.
Hey Kevin - heard about Your Company from a friend. I'm emailing because I
saw you just raised a seed round and I'd like to help you build the product.
Two things that may be relevant:
- I worked at That Company, where I helped to build Successful Feature
(big driver of ARR).
- I built Personal Project, which currently has 100,000 active users.
Can share more about other work, but feel like these two are perhaps the
most relevant.
I think I could help you build out [Product] quickly and would like to
learn more.
Worth a chat?Why it worked: Clear reason for reaching out (seed round). Two specific, impressive bullets. Humble framing ("perhaps the most relevant"). Easy ask.
---
Templates by Scenario
Reaching a Startup Founder (Post-Funding)
Hi [Name],
Saw you just [raised Series A / closed seed round / launched product].
I'm a [role] with [X years] building [relevant domain] and would like
to help you [specific goal related to their stage].
Two things that might be relevant:
- [Specific accomplishment with numbers at a recognizable company]
- [Personal project or second accomplishment with measurable impact]
I think I could help with [specific challenge they likely face at their
stage]. Worth a quick call to explore?
Best,
[Your name]Reaching a Hiring Manager (Posted Role)
Hi [Name],
I'm a [role] who [most impressive one-line credential]. I noticed you're
hiring for [specific role] and wanted to reach out directly.
A few things that may be relevant:
- [Accomplishment directly mapping to the job requirements]
- [Second accomplishment, ideally with metrics]
- [Optional: relevant side project or open source work]
Would you have 15 minutes this week to chat about the role?
Best,
[Your name]Reaching a Recruiter
Hi [Name],
I'm a [role] with [X years] in [domain]. I saw [Company] is hiring for
[role/team] and I'm very interested.
Quick background:
- [Most relevant credential with numbers]
- [Second credential mapping to their needs]
Happy to send my resume or hop on a quick call - whatever's easiest.
Best,
[Your name]Reaching Out with No Posted Job
Hi [Name],
I'm a [role] at [current company] and have been following [Company]
since [specific event: launch, funding, product release]. I'm reaching
out because I'd like to explore whether there's a fit.
Background:
- [Top credential with impact metrics]
- [Second credential relevant to their domain]
I know you may not be actively hiring for this, but if there's interest,
I'd love to learn more about what you're building.
Worth a conversation?
Best,
[Your name]Internal Transfer (Same Large Company)
Hi [Name],
I'm a [title] on the [current team] team ([X years] at [Company]).
I noticed your team is building [product/feature] and it aligns with
my interest in [area].
Quick highlights:
- [Accomplishment on current team with metrics]
- [Cross-team initiative or leadership example]
- [Relevant technical skill or project]
Would love to learn more about your team's roadmap and explore if my
background could add value. Available for a quick coffee chat this week?
- [Your name]---
Follow-Up Templates
Follow-Up 1 (After 4-5 Business Days)
Hi [Name],
Just wanted to bump this in case it got buried. Still very interested
in [Company/Role] and happy to share more about my background.
Best,
[Your name]Follow-Up 2 / Final (After Another 5-7 Days)
Hi [Name],
I know your inbox is probably swamped, so this is my last note.
If timing isn't right now, totally understand. But if you'd like to
chat about how I could help with [specific thing], I'm around.
Best,
[Your name]Rules: Maximum 2 follow-ups. After that, move on. Keep them on your list to revisit in 3-6 months if relevant.
---
LinkedIn Templates
Connection Request (Under 300 Characters)
Hi [Name], I'm a [role] with [X years] in [domain]. Saw [Company] is
[hiring for X / building Y]. Would love to connect and learn more.Post-Connection Message (Wait 1-2 Days)
Hi [Name],
Thanks for connecting! I wanted to reach out because [reason - keep
it to one sentence].
[2-3 sentences about relevant experience with specifics]
Would you have 15 minutes for a quick call this week?
Best,
[Your name]---
Good vs Bad Comparisons
Credential Descriptions
| Bad (vague/buzzwordy) | Good (specific/concrete) |
|---|---|
| "Executed strategic initiatives to drive measurable outcomes" | "Helped increase revenue by $2M in 6 months" |
| "Leveraged synergies to optimize workflows" | "Built a tool that cut processing time by 40%" |
| "Experienced full-stack engineer" | "Built Stripe's payment dashboard serving 10M users" |
| "Drove impact across the organization" | "Led initiative that added $25M annual profit" |
| "Passionate about AI and machine learning" | "Built AI diagnostic tool that reduced incident resolution by 83%" |
| "Strong communicator and team player" | [Delete this entirely - show, don't tell] |
Subject Lines
| Bad | Good |
|---|---|
| "Inquiry about opportunities" | "Engineer interested in your AI product" |
| "Following up on my application" | "Quick question about ML engineer role" |
| "Job seeker reaching out" | "Designer with fintech experience" |
| "Can we connect?" | "Referral from [mutual connection]" |
| "I'd love to work at [Company]!" | "Distributed systems eng, 300k+ TPS" |
Opening Lines
| Bad | Good |
|---|---|
| "Sorry to bother you, I know you're busy..." | [Just get to the point respectfully] |
| "I'm the perfect candidate and would be amazing..." | [Let accomplishments speak for themselves] |
| "I've been a huge fan of your company for years!" (when you just found them) | "Saw you just raised a Series B" (honest) |
| "I'd love to work at your company doing whatever" | "I want to help you solve [specific problem]" |
Ask Lines
| Bad (vague) | Good (specific) |
|---|---|
| "Let me know if you're interested" | "Worth a 15-minute call next week?" |
| "I'd love to chat sometime" | "Can I send over my portfolio?" |
| "Hope to hear from you" | "Would you be open to a quick chat about the role?" |
| "Looking forward to connecting" | "Worth a chat?" |
---
Mindset Reminders
When the user is hesitant or overthinking:
- You're not bothering anyone. Hiring managers and founders want to find great people. You're helping them.
- Rejection is data. Every non-response teaches something. Iterate.
- Volume is your friend. Don't pin all hope on one email. Batch 10-30 companies.
- 80% sent beats 100% unsent. An imperfect email sent today beats a perfect one you never send.