agentleFS
Sign inStart free
SamuelNDCESamuelNDCE/claude-super-skill-library/skills/content-marketing/investor-materials/SKILL.md

investor-materials

Skill1 starsChanged 3 months agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

9 rules. 8 are common, 0 are distinctive, and 1 is very specific to this project.

  • 8

    Common

    Most of the 8 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    All investor materials must agree with each other.

    line 21
  2. Common:

    Create or confirm a single source of truth before writing:

    line 23
  3. Common:

    If conflicting numbers appear, stop and resolve them before drafting.

    line 31
  4. Common:

    use of funds / milestones

    line 55
  5. Very specific:

    If the user wants a web-native deck, pair this skill with frontend-slides.

    line 58
  6. Common:

    keep claims easy to verify

    line 65
  7. Common:

    keep internal metrics consistent with the deck and model

    line 79
  8. Common:

    every number matches the current source of truth

    line 92
  9. Common:

    use of funds and revenue layers sum correctly

    line 93

“Common” is measured: kept by at least 6 in 10 of the 8 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.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

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free