$npx -y skills add affaan-m/ECC --skill investor-materialsCreate 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 consisten
| 1 | # Investor Materials |
| 2 | |
| 3 | Build investor-facing materials that are consistent, credible, and easy to defend. |
| 4 | |
| 5 | ## When to Activate |
| 6 | |
| 7 | - creating or revising a pitch deck |
| 8 | - writing an investor memo or one-pager |
| 9 | - building a financial model, milestone plan, or use-of-funds table |
| 10 | - answering accelerator or incubator application questions |
| 11 | - aligning multiple fundraising docs around one source of truth |
| 12 | |
| 13 | ## Golden Rule |
| 14 | |
| 15 | All investor materials must agree with each other. |
| 16 | |
| 17 | Create or confirm a single source of truth before writing: |
| 18 | - traction metrics |
| 19 | - pricing and revenue assumptions |
| 20 | - raise size and instrument |
| 21 | - use of funds |
| 22 | - team bios and titles |
| 23 | - milestones and timelines |
| 24 | |
| 25 | If conflicting numbers appear, stop and resolve them before drafting. |
| 26 | |
| 27 | ## Core Workflow |
| 28 | |
| 29 | 1. inventory the canonical facts |
| 30 | 2. identify missing assumptions |
| 31 | 3. choose the asset type |
| 32 | 4. draft the asset with explicit logic |
| 33 | 5. cross-check every number against the source of truth |
| 34 | |
| 35 | ## Asset Guidance |
| 36 | |
| 37 | ### Pitch Deck |
| 38 | Recommended flow: |
| 39 | 1. company + wedge |
| 40 | 2. problem |
| 41 | 3. solution |
| 42 | 4. product / demo |
| 43 | 5. market |
| 44 | 6. business model |
| 45 | 7. traction |
| 46 | 8. team |
| 47 | 9. competition / differentiation |
| 48 | 10. ask |
| 49 | 11. use of funds / milestones |
| 50 | 12. appendix |
| 51 | |
| 52 | If the user wants a web-native deck, pair this skill with `frontend-slides`. |
| 53 | |
| 54 | ### One-Pager / Memo |
| 55 | - state what the company does in one clean sentence |
| 56 | - show why now |
| 57 | - include traction and proof points early |
| 58 | - make the ask precise |
| 59 | - keep claims easy to verify |
| 60 | |
| 61 | ### Financial Model |
| 62 | Include: |
| 63 | - explicit assumptions |
| 64 | - bear / base / bull cases when useful |
| 65 | - clean layer-by-layer revenue logic |
| 66 | - milestone-linked spending |
| 67 | - sensitivity analysis where the decision hinges on assumptions |
| 68 | |
| 69 | ### Accelerator Applications |
| 70 | - answer the exact question asked |
| 71 | - prioritize traction, insight, and team advantage |
| 72 | - avoid puffery |
| 73 | - keep internal metrics consistent with the deck and model |
| 74 | |
| 75 | ## Red Flags to Avoid |
| 76 | |
| 77 | - unverifiable claims |
| 78 | - fuzzy market sizing without assumptions |
| 79 | - inconsistent team roles or titles |
| 80 | - revenue math that does not sum cleanly |
| 81 | - inflated certainty where assumptions are fragile |
| 82 | |
| 83 | ## Quality Gate |
| 84 | |
| 85 | Before delivering: |
| 86 | - every number matches the current source of truth |
| 87 | - use of funds and revenue layers sum correctly |
| 88 | - assumptions are visible, not buried |
| 89 | - the story is clear without hype language |
| 90 | - the final asset is defensible in a partner meeting |