Skip to content
cccskills
FreePublished on GitHub

investor-materials

Create and revise pitch decks, investor summaries, financial models, and accelerator applications using a shared set of facts. Cross-check figures, assumptions, funding requests, and milestones so fundraising documents remain consistent and their claims are easy to verify.

OriginalShow the original 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.

See how to install

Good for

  • Creating or revising an investor pitch deck
  • Writing an investor summary or memo
  • Building financial projections and use-of-funds tables
  • Preparing accelerator applications
  • Aligning figures across fundraising documents

Files included (1)

  • SKILL.md2.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

accessibility

FreeSummary

Design and audit interfaces for Web, iOS, and Android using WCAG 2.2 accessibility guidance. Check screen-reader labels, keyboard navigation, contrast, and control sizes to identify barriers and guide implementation for people using assistive technology.

  • Adding descriptive labels to icon-only buttons
  • Reviewing keyboard navigation and modal focus
  • Checking contrast and control sizes
affaan-m/ECC283.2KUpdated Oct 16, 2026

Investigate unreliable AI agents across 12 layers, including instructions, memory, tool execution, and display. Use code and logs to trace failures, rank findings by severity, and produce an ordered repair plan that prioritizes code changes.

  • Investigating failures that appear only inside an agent application
  • Tracing old conversation content leaking into new sessions
  • Checking skipped or falsely claimed tool execution
affaan-m/ECC283.2KUpdated Oct 16, 2026

agent-eval

FreeSummary

Compare coding agents on tasks from your own codebase. Define success checks, run agents in separate Git working directories, and report pass rates, available API costs, completion time, and consistency across repeated trials.

  • Comparing coding agents on real development tasks
  • Evaluating a new tool or model before adoption
  • Checking performance after agent updates
affaan-m/ECC283.2KUpdated Oct 16, 2026

Design and refine an AI agent’s available actions, tool inputs, and result formats. Define recovery steps for errors, manage the information kept in context, and evaluate changes through completion rates, retries, and cost per successful task.

  • Define an AI agent’s tool set and input formats
  • Make tool results and next steps easier to interpret
  • Specify safe retries and stopping conditions
affaan-m/ECC283.2KUpdated Oct 16, 2026

Diagnose failed AI agent runs by capturing errors, checking likely causes, and choosing small, reversible recovery actions. The workflow produces a structured report of the failure, recovery steps, and evidence, helping explain repeated retries or stalled progress.

  • Diagnosing repeated tool calls with no progress
  • Investigating quality loss as context grows
  • Checking file paths and environment mismatches
affaan-m/ECC283.2KUpdated Oct 16, 2026

Diagnose AI agent runs that fail repeatedly, loop through tools, or lose track of the task. Capture errors and environment details, test a focused recovery action, and produce a report explaining the evidence and outcome.

  • Diagnosing repeated failures in an agent run
  • Investigating loops through the same tool calls
  • Reviewing output degradation as context grows
affaan-m/ECC283.2KUpdated Oct 5, 2026

See all skills by affaan-m

Report a problem with this skill