mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-06-20 03:40:29 +08:00
db7f2a6fd5
The official Agent Skills spec (agentskills.io/specification) whitelists exactly 6 top-level frontmatter keys (name/description/license/compatibility/metadata/ allowed-tools). A top-level `origin` key fails the official validator (anthropics/skills quick_validate.py ALLOWED_PROPERTIES; skills-ref validate). This moves `origin: X` -> `metadata.origin: X` across the canonical skills/ tree, preserving each value verbatim. Frontmatter-only, minimal diff. - 251 SKILL.md updated (242 new metadata block, 9 appended to existing metadata) - origin values preserved verbatim (verified 251/251) - YAML validated on all changed files - scoped to canonical skills/ only (docs/<lang> translations + tool mirrors .cursor/.kiro/.agents left untouched; presumably regenerated from canonical) Addresses #2233
98 lines
2.7 KiB
Markdown
98 lines
2.7 KiB
Markdown
---
|
|
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
|