agentsclimarketplace
Sign in

Investor outreach

Skill khanhhuyenngo985-sys/character-scene-design-skills/skills/.archive/content-social/investor-outreach

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.From its SKILL.md

Install
npx -y skills add khanhhuyenngo985-sys/character-scene-design-skills --skill investor-outreach

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.1 KB, 429 tokens by cl100k_base, as published. Nobody here has run it

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 9 of the 12 instructions most sales crm skills give in 429 tokens

Counted across 338 of the 356 authors here whose files we hold, read 2026-09-06

  • Read the product marketing context before asking questionsin 42 of 338, across 22 files
  • Keep the ask low-frictionhere, and in 34 of 338, across 13 files
  • Personalize every outbound messagehere, and in 32 of 338, across 11 files
  • Use proof instead of adjectiveshere, and in 31 of 338, across 10 files
  • Keep the forwardable blurb under 100 wordshere, and in 31 of 338, across 10 files
  • Check the quality gate before deliveringhere, and in 29 of 338, across 8 files
  • Stay concisehere, and in 24 of 338, across 7 files
  • Follow the default follow-up cadencehere, and in 22 of 338, across 5 files
  • Add one new data point in each follow-uphere, and in 19 of 338, across 7 files
  • Run brand-voice first when voice mattersin 18 of 338, across 5 files
  • Make the ask one concrete next stephere, and in 17 of 338, across 4 files
  • Keep the tool adjacent to the core productin 16 of 338, across 5 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.