Token导航 LogoToken导航TokenDH.com
研究检索只读github未标认证来源可访问许可证需确认审计通过

fundraising-email筹款电子邮件

Agent Skill

fundraising-email 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

667

周安装

27

GitHub Stars

114

下载量

210
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:fundraising-email(筹款电子邮件)
来源仓库:https://github.com/shawnpang/startup-founder-skills
仓库路径:skills/fundraising-email
安装命令:
npx skills add https://github.com/shawnpang/startup-founder-skills --skill fundraising-email
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/shawnpang/startup-founder-skills --skill fundraising-email

简介

fundraising-email 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中根据关键词、任务场景或来源线索快速定位候选结果。

  • 适用于筹款电子邮件相关的信息搜集与筛选,可结合来源仓库和原始 README 核验具体用法。
  • 通过 npx skills add 命令从指定 GitHub 仓库安装,支持主流宿主环境集成。
  • 安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写操作。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

SKILL.md

Fundraising Email

When to Use

  • The founder needs to write a cold outreach email to an investor.
  • The founder wants to draft a warm intro request (a "forwardable email").
  • The founder needs a follow-up after an investor meeting.
  • The founder is writing a monthly investor update.
  • The founder wants to send a thank-you or round-closing notification.

Context Required

From startup-context: company one-liner, stage, key traction metrics, fundraising status, and any notable social proof (investors, customers, press).

From the user: email type, recipient (investor name and firm), prior relationship context, and desired outcome (meeting, intro, materials review).

Workflow

  1. Read startup context — Pull the company narrative, metrics, and fundraising details from .agents/startup-context.md.
  2. Determine email type — Classify as one of the five types below. Each has different structure, tone, and length.
  3. Draft the email — Follow the type-specific template. Keep it short — investors scan, they don't read.
  4. Add personalization — Include at least one specific reference to why this investor is a fit (thesis, portfolio company, blog post). Generic emails get ignored.
  5. Review against principles — Check the draft against the quality checklist. Trim aggressively.
  6. Deliver the final draft — Output subject line and email body, ready to copy-paste.

Output Format

**To:** [Investor Name]
**Subject:** [Subject line]

[Email body]

For investor updates, output a longer structured email with sections (see type 4 below).

Frameworks & Best Practices

The Five Email Types

1. Cold Outreach

Goal: Get a 30-minute meeting. Length: 5-7 sentences, under 150 words.

  • Line 1: Why *this* investor specifically (1 sentence).
  • Lines 2-3: What you do and for whom (no jargon).
  • Lines 4-5: Strongest traction proof point — one number that makes them lean in.
  • Line 6: Specific, low-commitment ask ("Would you have 30 minutes this week or next?").
  • No attachments on first email. Subject line formula: [Specific hook] — [Company Name] (e.g., "$40K MRR in 6 months, AI contract review — Lexara").

2. Warm Intro Request (The Forwardable Email)

Goal: Make it effortless for your connector to intro you. Two parts:

  • Note to connector (2-3 sentences): "Would you be willing to introduce me to [Partner] at [Firm]? Short blurb below you can forward directly."
  • Forwardable blurb (4-6 sentences): Written so the connector sends it as-is. Include what the company does, strongest metric, why this firm is relevant, and what you're looking for. If the connector has to rewrite it, they won't send it.

3. Follow-Up After Meeting

Goal: Maintain momentum, deliver materials, set next steps. Length: 4-8 sentences.

  • Thank them and reference one specific thing discussed. Attach requested materials. Address any open question. Propose a specific next step with a date. Send within 3 hours — speed signals competence.

4. Monthly Investor Update

Goal: Keep current and prospective investors informed. Length: 300-500 words.

  • Highlights: Top 3 wins (metrics-first).
  • KPIs: Table with this month, last month, MoM change.
  • Challenges: 1-2 honest struggles (invites help; investors respect candor).
  • Asks: 1-3 concrete requests (intros to specific customer types, candidates for a role).
  • What's Next: Top 2-3 priorities for next month.
  • Send on the same day each month. Monthly updates are the #1 way to convert a "not yet" into a future "yes".

5. Thank-You / Round Closing Note

Goal: Maintain the relationship. Length: 3-5 sentences.

  • If invested: genuine thanks, confirm logistics, add to update list.
  • If passed: thank them, leave the door open, ask if they want monthly updates. Never burn bridges — the investor who passes on seed may lead your Series A.

Core Principles

  1. Brevity wins — Investors get 50-100 inbound emails weekly. Over 200 words in a cold email gets skimmed.
  2. Specificity beats superlatives — "$42K MRR growing 25% MoM" beats "fast-growing revenue".
  3. Social proof early — Recognizable customer, investor, or accelerator in the first two lines.
  4. One clear CTA — Every email gets exactly one ask.
  5. Personalization is mandatory — Reference their thesis, portfolio, or writing. Doubles response rates.
  6. Subject lines are headlines — Lead with your best metric or most surprising fact.
  7. Send Tuesday-Thursday, 8-10am investor's timezone — Open rates drop on Mondays and Fridays.

What Not to Do

  • No "disruptive", "revolutionary", "game-changing", or "the Uber of X".
  • No NDAs. No reputable investor signs them for startup pitches.
  • Don't email multiple partners at the same firm. They compare notes.
  • Don't follow up more than twice without new information.
  • Don't CC multiple investors on the same email.

Related Skills

  • pitch-deck — the email drives the meeting; the deck carries the meeting
  • investor-research — research determines who to email and what personalization to use

Examples

Example prompt: "Write a cold email to Sarah Chen at Greylock. We're an AI code review startup with $55K MRR."

Good output:

Subject: $55K MRR — AI code review, 4 enterprise customers — CodeLens Hi Sarah, Your investment in Developer Infrastructure at Greylock — particularly the thesis in your "Next Wave of DevTools" post — is why I wanted to reach out to you specifically. I'm the CEO of CodeLens. We automate code review for enterprise engineering teams using LLMs, catching security vulnerabilities and logic errors that slip past existing tools. We launched 5 months ago: $55K MRR, 4 enterprise customers (two Fortune 500), growing 30% MoM. We're raising a $3M seed round. Would you have 30 minutes this week or next?

Example prompt: "Help me write this month's investor update."

Good output approach: Pull metrics from startup context, ask the founder for this month's highlights and challenges, then produce the structured update. Flag any missing or stale KPIs.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.19%
按下载量换算80

Claude

29.36%
按下载量换算62

Cursor

19.59%
按下载量换算41

Gemini CLI

8.42%
按下载量换算18

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills