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.
738 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
265
stars on the repo
on the repository, not the skill itself
Install
one command, takes just this skill from the repository
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
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
원문
영문 원문
탐색
한국어 문서 안내
기여 가이드
How to use it
Copy the folder
Take loulanyue/awesome-claude-notes-ko-kr-investor-materials from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
Check the name does not clash
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.