Skip to content
cccskills
FreePublished on GitHub

investor-materials

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.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

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

Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates.

The English summary is being prepared. Showing the original description.

sayasaya8039/ZWG_Terminal2Updated Jun 8, 2026

Operate as an agentic engineer using eval-first execution, decomposition, and cost-aware model routing.

The English summary is being prepared. Showing the original description.

sayasaya8039/ZWG_Terminal2Updated Jun 8, 2026

Engineering operating model for teams where AI agents generate a large share of implementation output.

The English summary is being prepared. Showing the original description.

sayasaya8039/ZWG_Terminal2Updated Jun 8, 2026

Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns.

The English summary is being prepared. Showing the original description.

sayasaya8039/ZWG_Terminal2Updated Jun 8, 2026

REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.

The English summary is being prepared. Showing the original description.

sayasaya8039/ZWG_Terminal2Updated Jun 8, 2026

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.

The English summary is being prepared. Showing the original description.

sayasaya8039/ZWG_Terminal2Updated Jun 8, 2026

See all skills by sayasaya8039

Report a problem with this skill