Investor Materials
Build investor-ready materials with Muse that stay internally consistent: pitch decks, one-pagers, memos, accelerator applications, financial models with explicit assumptions and a single source of truth.
- What
- Build investor-ready materials with Muse that stay internally consistent: pitch decks, one-pagers, memos, accelerator applications, financial models with explicit assumptions and a single source of truth.
- Cost
- Free
- Needs
- Use "Investor Materials" with your Muse.
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: a guide for building investor-facing materials with Muse that are consistent, credible, and defensible in a partner meeting. The golden rule comes first: all investor materials must agree with each other, so you create or confirm a single source of truth before writing anything, covering traction metrics, pricing and revenue assumptions, raise size and instrument, use of funds, team bios and titles, milestones and timelines, and you stop to resolve conflicting numbers before drafting. Asset guidance is concrete: a recommended twelve-step pitch deck flow from company and wedge through problem, solution, product, market, business model, traction, team, competition, ask, use of funds, and appendix, with a note to pair it with frontend-slides for a web-native deck; one-pagers and memos that state what the company does in one clean sentence, show why now, put traction early, and make the ask precise; financial models with explicit assumptions, bear base and bull cases, clean layer-by-layer revenue logic, milestone-linked spending, and sensitivity analysis; accelerator applications that answer the exact question asked, prioritize traction and insight, and avoid puffery. Red flags to avoid are listed: unverifiable claims, fuzzy market sizing without assumptions, inconsistent team roles, revenue math that does not sum cleanly, inflated certainty where assumptions are fragile. The quality gate before delivering checks that every number matches the source of truth, use of funds and revenue layers sum correctly, assumptions are visible not buried, the story is clear without hype language, and the final asset is defensible. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: Muse drafts the materials, you own the numbers; no skill fixes weak traction. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Copy the install package below, then paste it into MuseThe install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Use "Investor Materials" with your Muse. Prerequisites: none to install. Pure guidance; having your real traction numbers and assumptions ready helps. 1. Open the skill: https://github.com/affaan-m/ECC/blob/main/skills/investor-materials/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Help me build [pitch deck / one-pager / memo / financial model] for [company]. Here are my numbers: [traction, pricing, raise, team]." 3. Establish the single source of truth first, then draft, then run the quality gate: every number matching, math that sums, assumptions visible. Tip: build the source-of-truth fact sheet before any asset; it keeps the deck, memo, and model consistent. Safety: a skill is plain-text instructions; it runs nothing by itself. Review generated commands before running them.
Saved to your recent installs. Find it anytime on /connect.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.