investor-outreach
This Claude Code skill generates tailored investor communications including cold emails, warm introduction requests, follow-ups, and update emails for fundraising outreach. Use it when composing personalized messages to angels, venture capitalists, strategic investors, or accelerators that require specific references to the recipient's portfolio, thesis, or market focus, concrete proof points rather than generic language, and a single clear call to action designed for low friction engagement.
git clone --depth 1 https://github.com/affaan-m/ECC /tmp/investor-outreach && cp -r /tmp/investor-outreach/.cursor/skills/investor-outreach ~/.claude/skills/investor-outreachSKILL.md
# 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 1. Personalize every outbound message. 2. Keep the ask low-friction. 3. Use proof, not adjectives. 4. Stay concise. 5. Never send generic copy that could go to any investor. ## Cold Email Structure 1. subject line: short and specific 2. opener: why this investor specifically 3. pitch: what the company does, why now, what proof matters 4. ask: one concrete next step 5. 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
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
>
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
>
Build a source-derived writing style profile from real posts, essays, launch notes, docs, or site copy, then reuse that profile across content, outreach, and social workflows. Use when the user wants voice consistency without generic AI writing tropes.
Bun as runtime, package manager, bundler, and test runner. When to choose Bun vs Node, migration notes, and Vercel support.
>