investor-outreach — Claude Code skill: investor emails
Drafts cold emails, warm intro blurbs, follow-ups, and investor updates. Use it when fundraising outreach needs a concise message tailored to a specific investor.
npx skills add affaan-m/ECC --skill investor-outreach -a claude-codeWhat investor-outreach does
investor-outreach drafts cold emails, warm introduction requests, follow-ups after meetings or no reply, and updates during a fundraising process. It is aimed at outreach to angels, VCs, strategic investors, and accelerators. Each message centers on the recipient, concrete proof, and one clear next step.
The skill includes structures for cold emails, warm intro requests, post-meeting updates, and follow-up sequences. Personalization can use portfolio companies, a fund thesis, a public talk or article, a mutual connection, or a clear product fit. Run brand-voice first when the sender’s voice needs to guide the draft.
Install it when an agent needs investor-facing fundraising copy. It is a poor fit for generic copy that has no specific investor or proof point behind it.
What it helps with
- draft a cold email to an investor
- write a forwardable warm intro blurb
- follow up after a meeting or no reply
- send an update during fundraising
- tailor outreach to a fund thesis
Example prompts for the agent
- Draft a cold email for this investor using their thesis and our concrete proof points.
- Write a forwardable warm intro blurb under 100 words.
- Prepare a post-meeting update with the promised answer, one new proof point, and the next step.
How to install investor-outreach
1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill investor-outreach -a claude-code2Manually: put the files in place
~/.claude/skills/investor-outreach/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/investor-outreach/
1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill investor-outreach -a codex2Manually: put the files in place
.agents/skills/investor-outreach/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill investor-outreach -a cursor2Manually: put the files in place
.cursor/skills/investor-outreach/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install affaan-m/ECC investor-outreach2Manually: put the files in place
.github/skills/investor-outreach/SKILL.md1Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill investor-outreach -a gemini-cli2Platform CLI
gemini skills install https://github.com/affaan-m/ECC --path skills/investor-outreachManually: put the files in place
.devin/skills/investor-outreach/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add affaan-m/ECC --skill investor-outreach -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set146
The whole set →Similar
Questions about investor-outreach
How do I install investor-outreach in Claude Code?
Run npx skills add affaan-m/ECC --skill investor-outreach -a claude-code. The skill file is placed at ~/.claude/skills/investor-outreach/SKILL.md.
What does investor-outreach do?
It drafts cold emails, warm intro requests, follow-ups, and investor updates. The writing keeps the ask explicit and uses concrete proof instead of vague praise.
What context does investor-outreach need for personalization?
You can provide portfolio companies, a public thesis, a mutual connection, or a product and market fit with the investor’s focus. The draft should be personalized before it is sent.
Source text
SKILL.md · MIT
--- name: investor-outreach description: Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging. metadata: origin: ECC --- # Investor Outreach Write investor communication that is short, concrete, and easy to act on. ## When to Activate - writing a cold email to an investor - drafting a warm intro request - sending follow-ups after a meeting or no response - writing investor updates during a process - tailoring outreach based on fund thesis or partner fit ## Core Rules 1. Personalize every outbound message. 2. Keep the ask low-friction. 3. Use proof instead of adjectives. 4. Stay concise. 5. Never send copy that could go to any investor. ## Voice Handling If the user's voice matters, run `brand-voice` first and reuse its `VOICE PROFILE`. This skill should keep the investor-specific structure and ask discipline, not recreate its own parallel voice system. ## Hard Bans Delete and rewrite any of these: - "I'd love to connect" - "excited to share" - generic thesis praise without a real tie-in - vague founder adjectives - begging language - soft closing questions when a direct ask is clearer ## Cold Email Structure 1. subject line: short and specific 2. opener: why this investor specifically 3. pitch: what the company does, why now, and what proof matters 4. ask: one concrete next step 5. sign-off: name, role, and one credibility anchor if needed ## Personalization Sources Reference one or more of: - relevant portfolio companies - a public thesis, talk, post, or article - a mutual connection - a clear market or product fit with the investor's focus If that context is missing, state that the draft still needs personalization instead of pretending it is finished. ## Follow-Up Cadence Default: - day 0: initial outbound - day 4 or 5: short follow-up with one new data point - day 10 to 12: final follow-up with a clean close Do not keep nudging after that unless the user wants a longer sequence. ## Warm Intro Requests Make life easy for the connector: - explain why the intro is a fit - include a forwardable blurb - keep the forwardable blurb under 100 words ## Post-Meeting Updates Include: - the specific thing discussed - the answer or update promised - one new proof point if available - the next step ## Quality Gate Before delivering: - the message is genuinely personalized - the ask is explicit - the proof point is concrete - filler praise and softener language are gone - word count stays tight
© affaan-m · MIT · affaan-m/ECC