Investor Materials
This is for when you need to build a pitch deck, investor memo, financial model, or any fundraising material where the numbers actually have to add up across documents. It enforces a single source of truth before drafting anything, so your traction metrics, revenue assumptions, use of funds, and team bios stay consistent whether you're updating a deck or filling out an YC application. The workflow is deliberate: inventory your canonical facts, flag missing assumptions, then draft with explicit logic you can defend in a partner meeting. Honestly, the discipline here is the point. It won't let you ship conflicting numbers or bury assumptions, which is exactly the kind of friction that prevents awkward follow-up emails after a pitch.
- installs
- 5.1K
- GitHub stars
- 229.1K
- last updated
- Jul 14, 2026
Install
$ npx -y skills add affaan-m/everything-claude-code --skill investor-materials --agent claude-codeInstalls into .claude/skills of the current project.
Files
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
- inventory the canonical facts
- identify missing assumptions
- choose the asset type
- draft the asset with explicit logic
- cross-check every number against the source of truth
Asset Guidance
Pitch Deck
Recommended flow:
- company + wedge
- problem
- solution
- product / demo
- market
- business model
- traction
- team
- competition / differentiation
- ask
- use of funds / milestones
- 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
Sponsors
