affaan-m/ecc

investor-outreach

Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising.

Zobacz źródło

Jak używać

  1. Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
  2. W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
  3. Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/affaan-m/ecc --skill investor-outreach

Przed rozpoczęciem

  • Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
  • Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

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

Powiązane zadania

z tego samego repozytorium

Więcej Skills

Wszystkie Skills
affaan-m
Społeczność

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

Instalacje / 24h
489
GitHub Stars
308,2 tys.
Aktualizacja
20 lis
affaan-m
Społeczność

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

Instalacje / 1h
5
GitHub Stars
308,2 tys.
Aktualizacja
20 lis
affaan-m
Społeczność

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

Instalacje / 1h
2
GitHub Stars
307,9 tys.
Aktualizacja
20 lis
affaan-m
Społeczność

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

Instalacje / 1h
2
GitHub Stars
307,9 tys.
Aktualizacja
20 lis