investor-materials
Use when creating or updating pitch decks, one-pagers, investor memos, accelerator applications, financial models or use-of-funds tables. Enforces one source of truth so every fundraising document agrees on metrics, raise size and milestones.
- License 许可
- MIT
- 所属仓库
- monoes/monomind
- 最近更新
- 2026-11-10
- Stars
- ★ 23
- Forks
- 2
01 前言 Front Matter
- name
- investor-materials
- tags
- [ "finance", "writing", "fundraising" ]
- tools
- []
- source
- https://github.com/affaan-m/ECC
- license
- MIT
- description
- Use when creating or updating pitch decks, one-pagers, investor memos, accelerator applications, financial models or use-of-funds tables. Enforces one source of truth so every fundraising document agrees on metrics, raise size and milestones.
- source_path
- skills/investor-materials
- source_commit
- bf70150eb2df8070024e5bdf08e4aa08959e2735
02 资源文件 1
- 许可证LICENSE.txt1.0 KB
03 SKILL.md 正文
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
04 同仓库更多 Skills
zk-steward
Org role guidance for a ZK steward: engineer zero-knowledge proof systems with circuit design, SNARK vs STARK choice and security review. This is zero-knowledge cryptography, not Zettelkasten note-taking.
writing-plans
Use when you have a spec or requirements for a multi-step coding task and must write an implementation plan before touching code. Produces bite-sized TDD tasks with exact file paths, code and commands for an engineer with zero context.
write-spec
Write a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
write-query
Write optimized SQL for your dialect with best practices. Use when translating a natural-language data need into SQL, building a multi-CTE query with joins and aggregations, optimizing a query against a large partitioned table, or getting dialect-specific syntax for Snowflake, BigQuery, Postgres, etc.
workflow-automation
Org role guidance for workflow automation: build and maintain CI/CD definitions in GitHub Actions or equivalent: triggers, jobs, matrices, caching. Covers path filters, dependency caching, parallel jobs, timeouts and fail-fast ordering.
workflow-architect
Org role guidance for a workflow architect: map full workflow trees for systems, user journeys and agents, covering every branch and failure. Covers discovering workflows from code, handoff contracts, timeouts, recovery paths and observable state.