$npx -y skills add affaan-m/ECC --skill investor-outreachDraft 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.
| 1 | # Investor Outreach |
| 2 | |
| 3 | Write investor communication that is short, concrete, and easy to act on. |
| 4 | |
| 5 | ## When to Activate |
| 6 | |
| 7 | - writing a cold email to an investor |
| 8 | - drafting a warm intro request |
| 9 | - sending follow-ups after a meeting or no response |
| 10 | - writing investor updates during a process |
| 11 | - tailoring outreach based on fund thesis or partner fit |
| 12 | |
| 13 | ## Core Rules |
| 14 | |
| 15 | 1. Personalize every outbound message. |
| 16 | 2. Keep the ask low-friction. |
| 17 | 3. Use proof instead of adjectives. |
| 18 | 4. Stay concise. |
| 19 | 5. Never send copy that could go to any investor. |
| 20 | |
| 21 | ## Voice Handling |
| 22 | |
| 23 | If the user's voice matters, run `brand-voice` first and reuse its `VOICE PROFILE`. |
| 24 | This skill should keep the investor-specific structure and ask discipline, not recreate its own parallel voice system. |
| 25 | |
| 26 | ## Hard Bans |
| 27 | |
| 28 | Delete and rewrite any of these: |
| 29 | - "I'd love to connect" |
| 30 | - "excited to share" |
| 31 | - generic thesis praise without a real tie-in |
| 32 | - vague founder adjectives |
| 33 | - begging language |
| 34 | - soft closing questions when a direct ask is clearer |
| 35 | |
| 36 | ## Cold Email Structure |
| 37 | |
| 38 | 1. subject line: short and specific |
| 39 | 2. opener: why this investor specifically |
| 40 | 3. pitch: what the company does, why now, and what proof matters |
| 41 | 4. ask: one concrete next step |
| 42 | 5. sign-off: name, role, and one credibility anchor if needed |
| 43 | |
| 44 | ## Personalization Sources |
| 45 | |
| 46 | Reference one or more of: |
| 47 | - relevant portfolio companies |
| 48 | - a public thesis, talk, post, or article |
| 49 | - a mutual connection |
| 50 | - a clear market or product fit with the investor's focus |
| 51 | |
| 52 | If that context is missing, state that the draft still needs personalization instead of pretending it is finished. |
| 53 | |
| 54 | ## Follow-Up Cadence |
| 55 | |
| 56 | Default: |
| 57 | - day 0: initial outbound |
| 58 | - day 4 or 5: short follow-up with one new data point |
| 59 | - day 10 to 12: final follow-up with a clean close |
| 60 | |
| 61 | Do not keep nudging after that unless the user wants a longer sequence. |
| 62 | |
| 63 | ## Warm Intro Requests |
| 64 | |
| 65 | Make life easy for the connector: |
| 66 | - explain why the intro is a fit |
| 67 | - include a forwardable blurb |
| 68 | - keep the forwardable blurb under 100 words |
| 69 | |
| 70 | ## Post-Meeting Updates |
| 71 | |
| 72 | Include: |
| 73 | - the specific thing discussed |
| 74 | - the answer or update promised |
| 75 | - one new proof point if available |
| 76 | - the next step |
| 77 | |
| 78 | ## Quality Gate |
| 79 | |
| 80 | Before delivering: |
| 81 | - the message is genuinely personalized |
| 82 | - the ask is explicit |
| 83 | - the proof point is concrete |
| 84 | - filler praise and softener language are gone |
| 85 | - word count stays tight |