Skills affaan-m ecc

investor-materials

Use it when:
You're preparing a pitch deck, investor memo, one-pager, financial model, use-of-funds table or accelerator application.
It does:
Fixes one source of truth for traction, pricing, raise, use of funds, team and milestones, and stops when numbers conflict.
You get:
Fundraising drafts whose numbers match across every document, with assumptions shown rather than buried.
Deck order:
Twelve slides, from company and wedge through problem, market, traction and team to the ask, use of funds and appendix.

TL;DR

Its one rule is that every investor document must agree with every other. Before drafting, the agent inventories the canonical facts (traction metrics, pricing and revenue assumptions, raise size and instrument, use of funds, team bios and titles, milestones), lists the missing assumptions, and resolves any conflicting numbers first. Then it picks the asset and drafts it with explicit logic. Decks follow a twelve-part order; one-pagers and memos state the company in one sentence, show why now, put traction early and make a precise ask; financial models get visible assumptions, bear, base and bull cases where useful, layered revenue logic, milestone-linked spending and sensitivity analysis; accelerator answers address the exact question and match the deck. It steers clear of unverifiable claims, market sizing without assumptions, inconsistent titles and revenue math that doesn't sum. A final gate cross-checks every number against the source of truth. For a web-based deck it suggests pairing with ECC's frontend-slides skill.

Summarizes the skill at d2ef268.

npx skills add https://github.com/affaan-m/ecc --skill investor-materials
Total Downloads
5,600 on skills.sh, Nov 9, 2026
Repo stars
299,776 affaan-m/ecc
First seen
May 19, 2026 on skills.sh
Weekly Downloads
458
+73% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 21264
Sep 28178
Oct 5164
Oct 12259
Oct 19434
Oct 26424
Nov 2496
Nov 9458
Category

Articles, docs, internal comms, research write-ups and prose that doesn't read as generated.

Run a company outside its code and marketing: strategy, sales, finance, operations, legal, management and hiring.

Type

A multi-step process the agent follows: interview, debug, run a TDD loop, review.

Effect

Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.

Needs

Instructions only. Works in any agent that supports skills.

Publisher

Everyone else. Unverified vendor claims default to community.

Topics

SKILL.md

From affaan-m/ecc at d2ef268. Checked daily, last changed Nov 6, 2026.

Frontmatter
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