融资材料：做 BP、一页纸与财务摘要
做 BP、一页纸与财务摘要，按投资人关心的顺序组织。
What it produces
生成 BP、一页纸、投资人备忘录、财务模型等相互一致的融资文档。
Install
d=$(mktemp -d);
git -C "$d" init -q;
git -C "$d" fetch -q --depth 1 --filter=blob:none https://github.com/affaan-m/ECC.git 25278e7d7b6cf6e6a4e7a6c8e10f14ff22f0eb5b;
git -C "$d" sparse-checkout set --no-cone skills/investor-materials;
git -C "$d" checkout -q FETCH_HEAD;
mkdir -p ~/.claude/skills/investor-materials;
cp -R "$d/skills/investor-materials/." ~/.claude/skills/investor-materials/;
rm -rf "$d"Installs to ~/.claude/skills/investor-materials; to switch to Codex or Hermes, change only this path.
--- name: investor-materials description: Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials. Use when the user needs investor-facing documents, projections, use-of-funds tables, milestone plans, or materials that must stay internally consistent across multiple fundraising assets. metadata: origin: ECC --- # Investor Materials Build investor-facing materials that are consistent, credible, and easy to defend. ## When to Activate - creating or revising a pitch deck - writing an investor memo or one-pager - building a financial model, milestone plan, or use-of-funds table - answering accelerator or incubator application questions - aligning multiple fundraising docs around one source of truth ## Golden Rule All investor materials must agree with each other. Create or confirm a single source of truth before writing: - traction metrics - pricing and revenue assumptions - raise size and instrument - use of funds - team bios and titles - milestones and timelines If conflicting numbers appear, stop and resolve them before drafting. ## Core Workflow 1. inventory the canonical facts 2. identify missing assumptions 3. choose the asset type 4. draft the asset with explicit logic 5. cross-check every number against the source of truth ## Asset Guidance ### Pitch Deck Recommended flow: 1. company + wedge 2. problem 3. solution 4. product / demo 5. market 6. business model 7. traction 8. team 9. competition / differentiation 10. ask 11. use of funds / milestones 12. appendix If the user wants a web-native deck, pair this skill with `frontend-slides`. ### One-Pager / Memo - state what the company does in one clean sentence - show why now - include traction and proof points early - make the ask precise - keep claims easy to verify ### Financial Model Include: - explicit assumptions - bear / base / bull cases when useful - clean layer-by-layer revenue logic - milestone-linked spending - sensitivity analysis where the decision hinges on assumptions ### Accelerator Applications - answer the exact question asked - prioritize traction, insight, and team advantage - avoid puffery - keep internal metrics consistent with the deck and model ## Red Flags to Avoid - unverifiable claims - fuzzy market sizing without assumptions - inconsistent team roles or titles - revenue math that does not sum cleanly - inflated certainty where assumptions are fragile ## Quality Gate Before delivering: - every number matches the current source of truth - use of funds and revenue layers sum correctly - assumptions are visible, not buried - the story is clear without hype language - the final asset is defensible in a partner meeting