investor-materials
This skill creates and maintains investor-facing documents including pitch decks, one-pagers, memos, financial models, and accelerator applications. Use it when preparing fundraising materials that require internal numerical consistency, explicit assumptions, and alignment across multiple documents around a single source of truth before drafting any asset.
git clone --depth 1 https://github.com/affaan-m/ECC /tmp/investor-materials && cp -r /tmp/investor-materials/.cursor/skills/investor-materials ~/.claude/skills/investor-materialsSKILL.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 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
Workflow command scaffold for add-language-rules in everything-claude-code.
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails and you need a reproducible diagnosis instead of a retry.
Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.
>
>
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.
>