accelerator-applicatio…
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC…
When the user needs to write recruiting outreach messages to attract passive candidates or request referrals.
$ npx -y skills add shawnpang/startup-founder-skills --skill sourcing-outreach --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/sourcing-outreachContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user needs to write recruiting outreach messages to attract passive candidates or request referrals.
name: sourcing-outreach description: When the user needs to write recruiting outreach messages to attract passive candidates or request referrals. related: [job-description, interview-kit] reads: [startup-context]
Activate when the user asks to write cold outreach to potential candidates (LinkedIn InMails, cold emails), craft referral request messages, build a multi-touch follow-up sequence, or improve response rates on existing recruiting outreach. Also activate when the user is sourcing for a specific role and needs help personalizing messages at scale.
1. **Research the candidate** — Review the candidate details provided by the user. Identify 1-2 specific, genuine connection points: a project they shipped, a talk they gave, an open-source contribution, a blog post, or a career pattern that signals fit. 2. **Choose the outreach template** — Select from: cold LinkedIn InMail, cold email, warm intro request, referral ask, or follow-up. Each has different length and tone constraints. 3. **Draft the message** — Write a short, personalized message using the PRC framework (see below). Keep LinkedIn InMails under 300 characters for the preview. Keep cold emails under 150 words. 4. **Add a clear, low-friction CTA** — The ask should be small: a 15-minute call, a reply with interest level, or permission to send more details. Never ask for a resume or formal application in cold outreach. 5. **Build the follow-up sequence** — Draft 2-3 follow-ups spaced 4-7 days apart. Each follow-up adds new information (a company milestone, a team blog post, a relevant data point) rather than just "bumping" the thread. 6. **Review for tone** — Ensure the message sounds human, not templated. Check that personalization is specific enough that it could only apply to this candidate.
Every outreach message should contain three elements in roughly this order:
**LinkedIn InMail:**
**Cold Email:**
**Warm Intro / Referral Request:**
Before writing, look for:
Hey friends. Shawn here. I've been bootstrapping and starting companies for the past 10 years (still working hard at 996 level).
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC…
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure…
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to…
When the user needs to identify at-risk accounts, understand why customers are leaving, reduce churn rate, build health scores,…
When the user needs to set up or improve CI/CD pipelines — GitHub Actions, GitLab CI, deployment automation, or says "set up CI",…
When the user asks for a code review, shares code for feedback, or says "review this", "check my code", "what's wrong with this".…