investor-outreach
- Use it when:
- You're writing to angels, VCs, strategic investors or accelerators: a cold email, a warm intro request, a follow-up or an update.
- It does:
- Builds each message around why this investor, what the company does with its proof, and one concrete ask, and cuts stock phrases like "I'd love to connect".
- You get:
- Short drafts, flagged as unfinished when there's nothing specific to personalize them with.
- Pairs with:
- ECC's brand-voice skill when your own voice matters.
TL;DR
Investor messages should be short, concrete and easy to act on, and none should be sendable to just any investor. A cold email has a short, specific subject line, an opener on why this investor, a pitch with what the company does, why now and the proof that matters, one next step, and a sign-off with a credibility anchor if needed. Personalization comes from portfolio companies, a public thesis, talk or post, a mutual connection or a clear fit with the investor's focus. Follow-ups default to day 4 or 5 with one new data point and a final one on day 10 to 12, then stop. Warm intro requests give the connector the reason it's a fit and a forwardable blurb under 100 words. Post-meeting updates cover what was discussed, the promised answer, a new proof point and the next step. Before delivering, it checks the draft is personalized, the ask explicit, the proof concrete and the filler gone.
Summarizes the skill at d2ef268.
npx skills add https://github.com/affaan-m/ecc --skill investor-outreach skills.sh pageSource on GitHubAll skills from affaan-m/ecc
- Total Downloads
- 5,400 on skills.sh, Nov 9, 2026
- Repo stars
- 299,776 affaan-m/ecc
- First seen
- May 19, 2026 on skills.sh
Weekly values
| Week to | Installs |
|---|---|
| Sep 21 | 256 |
| Sep 28 | 162 |
| Oct 5 | 141 |
| Oct 12 | 231 |
| Oct 19 | 413 |
| Oct 26 | 405 |
| Nov 2 | 472 |
| Nov 9 | 440 |
| Category |
Articles, docs, internal comms, research write-ups and prose that doesn't read as generated. Run a company outside its code and marketing: strategy, sales, finance, operations, legal, management and hiring. |
|---|---|
| Type |
Knowledge and rules the agent applies while it works: best practices, design principles, API references. |
| Effect |
Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code. |
| Needs |
Instructions only. Works in any agent that supports skills. |
| Publisher |
Everyone else. Unverified vendor claims default to community. |
| Topics |
SKILL.md
From affaan-m/ecc at d2ef268. Checked daily, last changed Nov 6, 2026.
Frontmatter
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: ECCInvestor 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
- Personalize every outbound message.
- Keep the ask low-friction.
- Use proof instead of adjectives.
- Stay concise.
- 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
- subject line: short and specific
- opener: why this investor specifically
- pitch: what the company does, why now, and what proof matters
- ask: one concrete next step
- 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