Fundraising Email
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".
Install
npx skills add shawnpang/startup-founder-skills --skill fundraising-emailgit clone --depth 1 https://github.com/shawnpang/startup-founder-skills.git /tmp/startup-founder-skills
mkdir -p ~/.claude/skills
cp -r /tmp/startup-founder-skills/skills/fundraising-email ~/.claude/skills/fundraising-emailPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Fundraising Email ## When to Use - The founder needs to write a cold outreach email to an investor. - The founder wants to draft a warm intro request (a "forwardable email"). - The founder needs a follow-up after an investor meeting. - The founder is writing a monthly investor update. - The founder wants to send a thank-you or round-closing notification. ## Context Required 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). ## Workflow 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. ## Output Format
Details
- Skill name
fundraising-email- Repository
- shawnpang/startup-founder-skills
- Path
skills/fundraising-email/SKILL.md- License
- MIT
- Repo updated
- 16 March 2026
FAQ
What does the Fundraising Email skill do?
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".
How do I install the Fundraising Email skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add shawnpang/startup-founder-skills --skill fundraising-email. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Fundraising Email popular?
It lives in shawnpang/startup-founder-skills, which has 393 GitHub stars and 46 forks.
Related skills
Accelerator Application
393shawnpang/startup-founder-skills
When the user wants to apply to startup accelerators, incubators, or fellowship programs. Also use when the user mentions "YC application", "Techstars", "accelerator", or "apply to programs".
Architecture Design
393shawnpang/startup-founder-skills
When the user needs to design or evaluate system architecture — service boundaries, data models, API contracts, infrastructure topology, database selection, or dependency analysis. Also activate for "design the system", "how should I architect this", "monolith vs microservices", or architecture decision records.
Board Update
393shawnpang/startup-founder-skills
When the user needs to write a monthly or quarterly investor update, prepare a board deck, or communicate company progress to stakeholders.
Roadmap Planning
393shawnpang/startup-founder-skills
When the user needs to organize product initiatives into a prioritized, time-sequenced plan with outcomes and dependencies.
Fill in Notes
177Polaris-Aeterna/loom-notes
Turn a textbook chapter, lecture, or paper into beautiful "fill-in" study notes — written to be READ (clean statements, intuition) yet engineered to be FILLED (blanks, proof skeletons, "your turn" computations) so the reader learns by active recall. Notes are typeset with the Loom XeLaTeX class in this repo. Use when the user wants study notes from a source with gaps to fill in, worked examples restaged as exercises, or theorems stated but proofs left open. Triggers: "make fill-in notes", "turn this chapter into notes I can fill in", "guided / skeleton study notes", "study notes from this book
Turborepo
398JetBrains/skills
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.