跳到正文
cccskills
免费在 GitHub 公开

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.

中文简介正在准备中。当前显示原文说明。

实测评分 未实测

查看安装方法

包含的文件(1)

  • SKILL.md2.1 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

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

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates.

中文简介正在准备中。当前显示原文说明。

sayasaya8039/ZWG_Terminal22026年6月8日 更新

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing.

中文简介正在准备中。当前显示原文说明。

sayasaya8039/ZWG_Terminal22026年6月8日 更新

Engineering operating model for teams where AI agents generate a large share of implementation output.

中文简介正在准备中。当前显示原文说明。

sayasaya8039/ZWG_Terminal22026年6月8日 更新

Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns.

中文简介正在准备中。当前显示原文说明。

sayasaya8039/ZWG_Terminal22026年6月8日 更新

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

中文简介正在准备中。当前显示原文说明。

sayasaya8039/ZWG_Terminal22026年6月8日 更新

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.

中文简介正在准备中。当前显示原文说明。

sayasaya8039/ZWG_Terminal22026年6月8日 更新

查看 sayasaya8039 的全部技能

报告此技能的问题