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 wants to write an email to an investor — cold outreach, warm intro request, follow-up after a meeting, monthly investor update, or thank-you note. Also activates for "intro email", "investor email", "follow up with VC", or "investor update".
$ npx -y skills add shawnpang/startup-founder-skills --skill fundraising-email --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/fundraising-emailContext preview
The summary Claude sees to decide when to auto-load this skill.
When the user wants to write an email to an investor — cold outreach, warm intro request, follow-up after a meeting, monthly investor update, or thank-you note. Also activates for "intro email", "investor email", "follow up with VC", or "investor update".
name: fundraising-email description: When the user wants to write an email to an investor — cold outreach, warm intro request, follow-up after a meeting, monthly investor update, or thank-you note. Also activates for "intro email", "investor email", "follow up with VC", or "investor update". related: [pitch-deck, investor-research] reads: [startup-context]
From `startup-context`: company one-liner, stage, key traction metrics, fundraising status, and any notable social proof (investors, customers, press).
From the user: email type, recipient (investor name and firm), prior relationship context, and desired outcome (meeting, intro, materials review).
1. **Read startup context** — Pull the company narrative, metrics, and fundraising details from `.agents/startup-context.md`. 2. **Determine email type** — Classify as one of the five types below. Each has different structure, tone, and length. 3. **Draft the email** — Follow the type-specific template. Keep it short — investors scan, they don't read. 4. **Add personalization** — Include at least one specific reference to why this investor is a fit (thesis, portfolio company, blog post). Generic emails get ignored. 5. **Review against principles** — Check the draft against the quality checklist. Trim aggressively. 6. **Deliver the final draft** — Output subject line and email body, ready to copy-paste.
**To:** [Investor Name] **Subject:** [Subject line] [Email body]
For investor updates, output a longer structured email with sections (see type 4 below).
**Goal**: Get a 30-minute meeting. **Length**: 5-7 sentences, under 150 words.
**Goal**: Make it effortless for your connector to intro you. **Two parts**:
**Goal**: Maintain momentum, deliver materials, set next steps. **Length**: 4-8 sentences.
**Goal**: Keep current and prospective investors informed. **Length**: 300-500 words.
**Goal**: Maintain the relationship. **Length**: 3-5 sentences.
1. **Brevity wins** — Investors get 50-100 inbound emails weekly. Over 200 words in a cold email gets skimmed. 2. **Specificity beats superlatives** — "$42K MRR growing 25% MoM" beats "fast-growing revenue". 3. **Social proof early** — Recognizable customer, investor, or accelerator in the first two lines. 4. **One clear CTA** — Every email gets exactly one ask. 5. **Personalization is mandatory** — Reference their thesis, portfolio, or writing. Doubles response rates. 6. **Subject lines are headlines** — Lead with your best metric or most surprising fact. 7. **Send Tuesday-Thursday, 8-10am investor's timezone** — Open rates drop on Mondays and Fridays.
**Example prompt**: "Write a cold email to Sarah Chen at Greylock. We're an AI code review startup with $55K MRR."
**Good output**:
> **Subject:** $55K MRR — AI code review, 4 enterprise customers — CodeLens > > Hi Sarah, > > Your investment in Developer Infrastructure at Greylock — particularly the thesis in your "Next Wave of DevTools" post — is why I wanted to reach out to you specifically. > > I'm the CEO of CodeLens. We automate code review for enterpri
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".…