affaan-m/ecc

investor-materials

Create and update pitch decks, one-pagers, investor memos, accelerator applications, financial models, and fundraising materials.

View source

How to use

  1. Copy the installation command and review the source package before installing it in your own agent environment.
  2. Check the source document for required tools, credentials and supported hosts.
  3. Describe your input and desired deliverable; review the output against the source material.
npx skills add https://github.com/affaan-m/ecc --skill investor-materials

Before you start

  • Installation does not include a model subscription, API allowance or permission to access your files.
  • Repository stars and installation counts describe activity, not an independent quality or security test.
Original skill document

Rendered from the source repository. Headings, examples, code, tables, links, and referenced images are preserved.

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

Related by task

from this repository

More skills

All skills
affaan-m
Community

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology. Use when writing Rust tests — unit, integration, async, property-based, or coverage.

24h installs
489
GitHub stars
308.2K
Updated
Nov 20
affaan-m
Community

search-first

Research-before-coding workflow: search npm/PyPI, MCP servers, skills, and GitHub for existing tools before writing custom code, then adopt, extend, or build. Launches the researcher agent for non-trivial needs. Use when starting a feature, adding a dependency or integration, or about to write a utility that may already exist.

1h installs
5
GitHub stars
308.2K
Updated
Nov 20
affaan-m
Community

browser-qa

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

1h installs
2
GitHub stars
307.9K
Updated
Nov 20
affaan-m
Community

docker-patterns

Docker and Docker Compose patterns for local development, hardened CLI installer harnesses, container security, networking, volumes, and multi-service orchestration. Use when creating or reviewing Dockerfiles and Compose services, testing installers across Linux distributions, or planning accurate native macOS and Windows validation.

1h installs
2
GitHub stars
307.9K
Updated
Nov 20