Token导航 LogoToken导航

Agent Skill · 待分类

fundraising(fundraising 演示文稿)

fundraising 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

fundraising 是待分类类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描有提醒项,按安装量在待分类类的 11,208 个 Skill 里排第 9,871。

总安装 220周安装 9GitHub Stars 50下载 71核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

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

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

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/liqiongyu/lenny_skills_plus --skill fundraising

这个 Skill 是做什么的

这个 Skill 的分类还没最终确定,用法以来源仓库的说明为准。

fundraising 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息。适合在 Codex、Claude、Cursor、Gemini CLI 中围绕仓库状态、代码变更或协作事项进行整理。通过 npx skills add 命令从指定仓库安装并使用该技能。

使用前需确认权限范围、维护状态,以及是否涉及联网、命令执行或文件读写。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/fundraising

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/liqiongyu/lenny_skills_plus --skill fundraisin…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

fundraising 怎么安装?

在终端执行 npx skills add https://github.com/liqiongyu/lenny_skills_plus --skill fundraising。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

fundraising 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

fundraising 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

fundraising 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

fundraising 用的人多吗?

公开数据是累计安装 220 次,近一周安装 9 次,下载 71 次,GitHub 50 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

fundraising 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理待分类类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

待分类类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
infsh-cli

infsh CLI · Codex、Claude

4,374,576382权限未标注未明确未收录
ai-video-generation

AI 视频生成 · Codex、Claude

4,313,376382调用外部服务未明确有提醒
lark-openapi-explorer

云雀 OpenAPI 浏览器 · Codex、Claude

2,064,1209,011需要联网未明确有提醒
lark-workflow-standup-report

Lark 工作流程站立报告 · Codex、Claude

2,041,6328,978需要联网未明确通过
use-my-browser

使用我的浏览器 · Codex、Claude

1,848,49140操作浏览器未明确未通过
fundraising

fundraising 演示文稿 · 本页

22050需要联网未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Fundraising

Scope

Covers

  • Deciding whether to raise venture funding (vs bootstrapping / delaying / alternatives) and articulating the trade-offs
  • Designing a round (amount, timeline, milestone, target investor profile) without pretending to give legal/tax advice
  • Building an investor-ready narrative and a pitch deck outline optimized for first impressions
  • Running the fundraising process as a pipeline (target list, outreach, follow-ups, rejection handling, momentum)
  • Preparing for diligence (data-room checklist + FAQs/objections) and reducing “unknown unknowns”

When to use

  • “Should I raise venture capital or bootstrap?”
  • “Help me build a pitch deck narrative and a strong first slide.”
  • “I need an investor outreach plan and a pipeline tracker.”
  • “I’m starting a pre-seed/seed raise; help me run the process end-to-end.”

When NOT to use

  • You need to build a founder-led sales motion or close your first customers — use founder-sales (this pack raises capital; that pack generates revenue)
  • You want to validate a startup idea before raising — use startup-ideation (validate the idea first, then raise)
  • You need help with presentation delivery, storytelling mechanics, or slide design — use giving-presentations (this pack builds the narrative and deck *outline*; that pack covers delivery and design)
  • You have a job offer to negotiate (not an investment round) — use negotiating-offers
  • You need legal, tax, or securities advice (term sheets, SAFE/notes, incorporation, compliance) — involve qualified professionals
  • You’re raising grants/donations or structured debt (use a fundraising/grants/debt-specific workflow instead)
  • You only want visual slide design polish with no strategy/process work
  • You’re in an immediate liquidity crisis where the only viable path is emergency financing within days (this skill can help structure messaging, but you should prioritize urgent financial triage with experts)

Inputs

Minimum required

  • Company snapshot: what you build, who it’s for, and why now
  • Stage + traction (or pre-traction proof), plus 1–3 key metrics (even proxies)
  • Team snapshot (founders, key strengths, gaps you’re hiring for)
  • Runway + constraints (cash, time, geography, intro network, fundraising window)
  • Fundraising intent: why raise, target amount (or range), and what milestone it buys

Missing-info strategy

  • Ask 3–5 questions at a time from references/INTAKE.md.
  • If specifics are missing, proceed with labeled assumptions and ranges (never invent exact numbers).
  • Do not request sensitive credentials or confidential customer/employee data; use anonymized examples.

Outputs (deliverables)

Produce a Fundraising Pack (Markdown in chat; or as files if requested) in this order:

  1. Raise Decision Memo (VC vs bootstrap/delay; trade-offs; “if we raise” vs “if we don’t” plan)
  2. Round Design Brief (amount, timing, milestone, use of funds, target investor profile)
  3. Pitch Narrative + Deck Outline (including a high-signal first slide + talk track)
  4. Investor ICP + Target List + Pipeline Tracker (with weekly activity targets)
  5. Outreach + Follow-up Scripts (warm intro ask, cold email, post-meeting follow-up)
  6. Diligence Prep (data-room checklist + FAQ/objection responses)
  7. Operating Cadence (weekly dashboard, “100 no’s” resilience plan, next-14-days action plan)
  8. Risks / Open questions / Next steps (always)

Templates: references/TEMPLATES.md Expanded guidance: references/WORKFLOW.md

Workflow (8 steps)

1) Intake + constraints snapshot

  • Inputs: user context; references/INTAKE.md.
  • Actions: Capture stage, runway, constraints, timing, and goal. Separate “must be true” vs “nice to have”. Identify what would make fundraising a mistake.
  • Outputs: Context snapshot + assumptions/unknowns list.
  • Checks: Timeline has dates; runway is stated (or explicitly unknown); constraints are explicit.

2) Decide whether to raise (and why)

  • Inputs: goals, constraints, risk tolerance, business model.
  • Actions: Write a Raise Decision Memo: why raise, why not, and the “venture treadmill” trade-off (growth expectations, dilution, speed). Propose alternatives (delay, revenue-first, angels, strategic, debt) where appropriate.
  • Outputs: Raise Decision Memo with a clear recommendation + decision criteria.
  • Checks: Recommendation is falsifiable (“we raise if X by date Y”); non-VC path is not hand-waved.

3) Design the round (make the plan fundable)

  • Inputs: runway, burn (or plan), milestone, hiring needs, market timing.
  • Actions: Define raise amount range, timing, and the milestone it buys. Specify investor profile (stage, check size, thesis, geography) and a simple “use of funds” narrative.
  • Outputs: Round Design Brief.
  • Checks: Amount ↔ milestone is coherent; plan fits constraints; assumptions are explicit.

4) Build the pitch narrative + first impression assets

  • Inputs: product, ICP, wedge, traction/proof, insights from Steps 1–3.
  • Actions: Draft a crisp one-liner, the “strongest point” for slide 1, and a deck outline that answers: problem, solution, why now, why you, why win, why invest.
  • Outputs: Pitch Narrative + Deck Outline (+ talk track).
  • Checks: First slide passes the 10-second test (what it is, for whom, why it matters); narrative has evidence, not vibes.

5) Build the investor pipeline (target list + math)

  • Inputs: target investor profile; network; constraints.
  • Actions: Create an ICP and a prioritized target list. Set pipeline math (how many intros/meetings/week) and define a tracking table.
  • Outputs: Investor ICP + Target List + Pipeline Tracker.
  • Checks: Targets match round design; outreach plan is schedulable; next 7 days have concrete outreach tasks.

6) Execute outreach + meetings (run the “100 no’s” process)

  • Inputs: scripts; target list; calendar.
  • Actions: Draft outreach messages, run outreach cadence, and standardize meeting flow + follow-ups. Track “nos” as data (rejection reasons) and iterate the pitch.
  • Outputs: Outreach + Follow-up Scripts + meeting agenda + iteration log.
  • Checks: Every meeting has a next step; follow-ups go out within 24 hours; learnings are captured weekly.

7) Prep diligence (reduce friction)

  • Inputs: likely diligence asks; current docs.
  • Actions: Create a lightweight data-room checklist and an FAQ/objection response sheet. Identify the 3–5 biggest diligence gaps and a plan to close them.
  • Outputs: Diligence Prep checklist + FAQ.
  • Checks: No claims without supporting artifacts; sensitive info is handled carefully.

8) Quality gate + finalize the pack

  • Inputs: full draft pack.
  • Actions: Run references/CHECKLISTS.md and score with references/RUBRIC.md. Tighten weak sections. Add Risks / Open questions / Next steps and a next-14-days action plan.
  • Outputs: Final Fundraising Pack.
  • Checks: Pack is decision-ready, narrative-coherent, and process-executable.

Quality gate (required)

Examples

Example 1 (pre-seed): “We’re 2 founders building a B2B workflow tool. We have 5 design partners and 2 pilots. We have 6 months runway and want to raise $1.5–2.0M. Use fundraising to produce the full Fundraising Pack including a deck outline and investor pipeline tracker.” Expected: decision memo + round design + deck outline (strong first slide) + target list + outreach scripts.

Example 2 (seed with traction): “We’re at $60k MRR and growing 10% MoM. We’re debating whether to raise now or wait 6 months. Use fundraising to help us decide and create an outreach plan if we choose to raise.” Expected: raise-vs-wait decision memo with criteria + round design options + pipeline plan.

Boundary example: “Draft a SAFE agreement and tell me what valuation I should take.” Response: out of scope for legal/pricing advice; offer to produce the negotiation inputs (round design assumptions, comps proxy approach, questions for counsel) and a fundraising process plan.

Anti-patterns

  1. Raising without a thesis — Jumping into investor outreach without a clear “why raise, why now, why this amount” decision memo. The raise decision memo is not optional — it prevents raising money you don't need or raising too little to hit the next milestone.
  2. Deck-first, narrative-last — Designing slides before having a crisp pitch narrative. The narrative (problem, wedge, why now, why you, why win) should drive the deck, not the other way around. Start with a strong one-liner and first-slide story.
  3. Spray-and-pray outreach — Sending the same cold email to 200 investors without ICP filtering. Effective fundraising targets 30-50 high-fit investors with warm paths, not a mass blast. Track signal-to-noise and iterate weekly.
  4. Ignoring the “100 no's” reality — Expecting a quick close and getting demoralized by rejection. The operating cadence should include resilience planning: rejection tracking, pitch iteration log, weekly learnings, and emotional support.
  5. Diligence denial — Waiting for a term sheet to start preparing for diligence. Build the data room checklist and FAQ/objection responses in parallel with outreach, not as an afterthought.

平台分布

Codex

34.47%
按下载量换算24

Claude

29.94%
按下载量换算21

Cursor

21.78%
按下载量换算15

Gemini CLI

8.91%
按下载量换算6

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills