investor-outreach
Skill44 starsChanged 5 months agoMITView on GitHub
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.
We split this skill into the rules it gives an agent
8 rules. 6 are common, 2 are distinctive, and 0 are very specific to this project.
6
Common
Most of the 13 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 9
Write investor communication that is short, personalized, and easy to act on.
- Common: line 22
Keep the ask low-friction.
- Distinctive: line 23
Use proof, not adjectives.
- Common: line 25
Never send generic copy that could go to any investor.
- Common: line 32
ask: one concrete next step
- Distinctive: line 43
If that context is missing, ask for it or state that the draft is a template awaiting personalization.
- Common: line 52
Do not keep nudging after that unless the user wants a longer sequence.
- Common: line 59
keep the forwardable blurb under 100 words
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Investor Outreach
Write investor communication that is short, personalized, 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, not adjectives.
- Stay concise.
- Never send generic copy that could go to any investor.
Cold Email Structure
- subject line: short and specific
- opener: why this investor specifically
- pitch: what the company does, why now, what proof matters
- ask: one concrete next step
- sign-off: name, role, 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, ask for it or state that the draft is a template awaiting personalization.
Follow-Up Cadence
Default:
- day 0: initial outbound
- day 4-5: short follow-up with one new data point
- day 10-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:
- message is personalized
- the ask is explicit
- there is no fluff or begging language
- the proof point is concrete
- word count stays tight
Trending
Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data
Other versions37 projects use a version of this.
Word for word · 22
- affaan-m/ECC★ 246k100% same
- loulanyue/awesome-claude-notes★ 272100% same
- tpavanipradeep/everything-claude-code★ 104100% same
- mit-network/everything-claude-code★ 76100% same
- j7-dev/everything-github-copilot★ 19100% same
- Infopibe/everything-claude-code★ 8100% same
- yapota2018/affaan-m-everything-claude-code★ 4100% same
- ArogyaReddy/https-github.com-affaan-m-everything-claude-code1★ 2100% same
- CodeWithBehnam/cc-docs★ 2100% same
- ashutoshrathi0909-oss/everything-claude-code★ 1100% same
12 more not listed
Edited · 13
- xu-xiang/everything-claude-code-zh★ 1.9k19% same
- mturac/everything-openai-codex★ 8962% same
- Fmarzochi/EGC★ 6162% same
- gongyijie85/dsh-ecc★ 862% same
- GPTtang/skill-atlas★ 499% same
- niloykumarbarman/EVERYTHING-CLAUDE-CODE★ 163% same
- SamuelNDCE/claude-super-skill-library★ 163% same
- SolshineCode/claude-code-skills★ 163% same
- vivekkhimani/gtm-tools-template★ 163% same
- davidanthonyn/claude-skills★ 063% same
3 more not listed
Wrote their own version · 2
- Unabyss/unabyss-skills★ 15same name
- rhfl04-dfdf/jychoi_everything-claude-code-ko★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository91 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .codex/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- examples/CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/common-agents.mdCursor rule
- .cursor/rules/common-coding-style.mdCursor rule
- .cursor/rules/common-development-workflow.mdCursor rule
- .cursor/rules/common-git-workflow.mdCursor rule
- .cursor/rules/common-hooks.mdCursor rule
- .cursor/rules/common-patterns.mdCursor rule
- .cursor/rules/common-performance.mdCursor rule
- .cursor/rules/common-security.mdCursor rule
- .cursor/rules/common-testing.mdCursor rule
- .cursor/rules/golang-coding-style.mdCursor rule
- .cursor/rules/golang-hooks.mdCursor rule
- .cursor/rules/golang-patterns.mdCursor rule
- .cursor/rules/golang-security.mdCursor rule
- .cursor/rules/golang-testing.mdCursor rule
- .cursor/rules/kotlin-coding-style.mdCursor rule
- .cursor/rules/kotlin-hooks.mdCursor rule
- .cursor/rules/kotlin-patterns.mdCursor rule
- .cursor/rules/kotlin-security.mdCursor rule
- .cursor/rules/kotlin-testing.mdCursor rule
- .cursor/rules/php-coding-style.mdCursor rule
- .cursor/rules/php-hooks.mdCursor rule
- .cursor/rules/php-patterns.mdCursor rule
- .cursor/rules/php-security.mdCursor rule
- .cursor/rules/php-testing.mdCursor rule
- .cursor/rules/python-coding-style.mdCursor rule
- .cursor/rules/python-hooks.mdCursor rule
- .cursor/rules/python-patterns.mdCursor rule
- .cursor/rules/python-security.mdCursor rule
- .cursor/rules/python-testing.mdCursor rule
- .cursor/rules/swift-coding-style.mdCursor rule
- .cursor/rules/swift-hooks.mdCursor rule
- .cursor/rules/swift-patterns.mdCursor rule
- .cursor/rules/swift-security.mdCursor rule
- .cursor/rules/swift-testing.mdCursor rule
- .cursor/rules/typescript-coding-style.mdCursor rule
- .cursor/rules/typescript-hooks.mdCursor rule
- .cursor/rules/typescript-patterns.mdCursor rule
- .cursor/rules/typescript-security.mdCursor rule
- .cursor/rules/typescript-testing.mdCursor rule
- agent-introspection-debuggingSkill
- agent-sortSkill
- api-designSkill
- article-writingSkill
- backend-patternsSkill
- benchmark-methodologySkill
- brand-discoverySkill
- brand-voiceSkill
- bun-runtimeSkill
- coding-standardsSkill
- competitive-platform-analysisSkill
- competitive-report-structureSkill
- content-engineSkill
- crosspostSkill
- deep-researchSkill
- dmux-workflowsSkill
- The first 60 shown.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

