Search the docs, videos, blog, apps, teams, skills and release notes.
At a glance
What it is
Covers seed and Series A. For live delivery and Q&A, switch to demo-day-and-q-a. For the shift sentence anchoring slide one, run narrative-shift first.
A skill is a written procedure a bot loads when a job calls for it. This one is a single file, SKILL.md, and the whole file is on this page.
Each of these library teams gives its bots this skill. Import one and look inside first.
The whole file, exactly as it downloads. Read it before you rely on it.
SKILL.md
78 lines · 816 words
Mode skill. Default-enabled on the Stage specialist.
Use when the deliverable is the actual deck — slides in order, with speaker notes. Covers seed and Series A. For live delivery and Q&A, switch to demo-day-and-q-a. For the shift sentence anchoring slide one, run narrative-shift first.
A pitch deck is a sequence of claims, each earning the next.
Covers seed and Series A. For live delivery and Q&A, switch to demo-day-and-q-a. For the shift sentence anchoring slide one, run narrative-shift first.
Nothing. It ships with Murage, which is open source. Your bots run on the AI plan you already have.
Yes. Open it in Settings → Skills to read, edit or duplicate it. Skill Guard scans it again after every edit.
Download the app, connect the AI you already pay for, and tell your Chief of Staff what needs doing. Plan on about ten minutes from install to a working team.
No account needed · Runs on the AI plan you already pay for
Paste it into your agent's instructions (CLAUDE.md, AGENTS.md or a custom GPT), or add it to a bot in Murage.
Ask Ember for the bot, then switch the skill on in its settings.
Step 1
Send your Chief of Staff this message. It proposes the bot and its role first, and creates it when you say go.
Send this to Ember
“Create a bot that uses the Pitch Deck skill, and show me the plan first.”
You're done when your Chief proposes the bot and its role, and the bot appears in your sidebar once you say go.
Step 2
You're done when you see the bot’s skills and the library.
Step 3
You're done when the skill shows as on for that bot.
Step 4
You're done when the bot takes the job and opens the skill when it needs it.
Prefer to do it yourself? Choose + in the sidebar, then New Bot.Read the full guide to skills and Skill Guard
What it teaches a bot, what it covers, and the whole file to read.
The principle
**Mode skill.** Default-enabled on the Stage specialist.
What it covers
When to use
The ten-slide arc
Procedure
Decision rules
Anti-patterns
Before / after
Sequoia template, refined with Raskin's spine. Eleven slides if the ask warrants its own page.
The shift. One sentence: what changed in the world. No product. No company name in the headline.
The stakes. Who wins and who loses under the new rules. The slide where the room leans in or checks their phone.
The problem. The new winner criterion, stated as a problem the buyer feels today. Customer-voice phrasing if available.
The old way and why it fails. Name the incumbent approach. State the dimension on which it falls short of the new criterion. Do not insult the incumbent — explain its design assumption and why the shift broke it.
The new way. Name the new approach as a category, not a product. "We're building a [category] for [audience] in the era of [shift]."
The product. One screen, one workflow, one frame. The product is the proof of the category, not the category itself.
Traction or design-partner evidence. Revenue, users, retention, design partners, waitlist — in that priority. Real numbers only.
Market built bottom-up. Number of buyers × annual willingness to pay × adoption assumption, with the source for each. Top-down TAM goes in the appendix.
Business model. Pricing, unit economics, payback period. Coin sets these; you place them.
Team. One sentence per founder naming the earned advantage relevant to this problem.
The ask. Round size, runway it buys, three milestones it will produce.
Lock the shift sentence first. Run narrative-shift. Do not draft slides until the shift survives the three-question test.
Draft slide one as a headline plus a single proof point. No bullets. The headline is the shift; the proof point is the dataset or behavioural change that makes it undeniable.
Work slides two through five before the product slide. Founders skip to the product. You force the narrative spine first.
Pull traction numbers verbatim. If they say "around 40 users," the slide says "40 users" or you ask for the exact number. No rounding up.
Get the market build from Coin. Ask Coin to produce it; you place it.
Write speaker notes in the founder's voice. Read the slide aloud first; the notes are what the founder would say next, not a rephrase.
Stress-test against the twenty Q&A questions. Run demo-day-and-q-a. Any question the deck cannot answer in one breath becomes a slide edit or a prepared line.
Hand the visual template to Mira. You deliver content and structure; Mira sets the look. Do not pick fonts.
One claim per slide. If a slide makes two claims, split it or cut one.
The product is slide six. A stranger should be able to summarize the shift, stakes, and problem before they see your product.
Bottom-up market only. Top-down sizing belongs in the appendix, never as the primary slide.
The ask names milestones, not categories of spend. "$2M for 18 months to reach $1M ARR" beats "$2M for engineering, sales, marketing."
No "vision" slides at the end. The shift slide carries the vision. A second vision slide signals the first is weak.
Logo-clutter "as featured in" slides used as proof. Press is not traction.
Team slide with five faces and three sentences each. One sentence, founders only.
TAM/SAM/SOM dolls without a bottom-up build. Investors discount top-down to zero.
Product screens with feature labels and arrows. One screen, one workflow.
Competitive matrix scoring green on every row. No reader believes it; some leave on it.
Brief: "Seed deck for a B2B tool that pulls product analytics into Slack."
Before (product-first, no shift, generic stakes):
Slide 1: "Acme — product analytics, simplified." Slide 2: "The problem: product analytics is hard." Slide 3: "Our solution: Slack-native dashboards."
After (shift-first, stakes named, product on slide six):
Slide 1: "In 2025, every product team moved standups into Slack. Their analytics stayed in a browser tab nobody opens." Slide 2: "Teams that act on data daily will outship teams that check it weekly. The week-checkers are losing." Slide 3: "Product managers want one number every morning. They have eleven dashboards and check none."
The "after" earns slide six. The "before" dies on slide three.
SKILL.md
78 lines · 816 words
The text of SKILL.md is shown as it downloads, under the Apache-2.0 license, by Ferrox Labs. The license is the one in the file's own frontmatter.
Your new bot
Pitch Deck bot
Waiting in your sidebar once you say go.
No account needed · Runs on the AI plan you already pay for