Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Structure and write investor pitch decks covering problem, solution, market, business model, traction, team, and financials. Use this skill when the user needs to create a fundraising presentation, prepare for investor meetings, or structure a startup pitch — even if they say 'build a pitch deck', 'present to investors', 'prepare for fundraising', or 'how should I structure my pitch'.
.claude/skills/asgard-ai-platform-ops-pitch-deck/SKILL.md| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-03 | ✗→✓ | ▲ Improved | -12% | 0% |
| case-13 | ✗→✓ | ▲ Improved | 24% | 0% |
| case-15 | ✗→✓ | ▲ Improved | 80% | 0% |
| case-04 | ✓→✓ | = Same ✓ | 55% | 0% |
| case-05 | ✓→✓ | = Same ✓ | 69% | 0% |
IRON LAW: 10-15 Slides, One Idea Per Slide
Investors see 100+ decks per month. They spend 3-4 minutes on average.
Every slide must earn its place. If a slide doesn't advance the core
narrative (problem → solution → why us → why now), cut it.| # | Slide | Purpose | Time | |---|-------|---------|------| | 1 | Title | Company name, one-line description, your name | 10 sec | | 2 | Problem | The pain point — specific, relatable, data-backed | 30 sec | | 3 | Solution | How you solve it — clear, concrete | 30 sec | | 4 | Demo/Product | Show, don't tell — screenshot, video, or flow | 45 sec | | 5 | Market Size | TAM → SAM → SOM with methodology | 30 sec | | 6 | Business Model | How you make money — pricing, unit economics | 30 sec | | 7 | Traction | What you've achieved — revenue, users, growth rate | 30 sec | | 8 | Competition | 2×2 positioning map — where you win | 20 sec | | 9 | Team | Why THIS team wins — relevant experience | 20 sec | | 10 | Financials | 3-year projection — revenue, key assumptions | 30 sec | | 11 | The Ask | How much, what for, what milestones it enables | 20 sec | | 12 | Contact | Name, email, next step | 5 sec |
Problem Slide:
Market Size:
Traction Slide (most important for fundraising):
Competition Slide:
The Ask:
markdown# Pitch Deck Outline: {Company} ## Slide-by-Slide Content ### 1. Title - Company: {name} - Tagline: {one line} ### 2. Problem - Pain point: {specific, data-backed} - Who has this problem: {target customer} ### 3. Solution - What we do: {one sentence} - How it works: {2-3 bullet points} ### 4. Product - {Screenshot/demo description} ### 5. Market - TAM: ${X} - SAM: ${X} - SOM: ${X} (methodology: {how calculated}) ### 6. Business Model - Revenue model: {subscription/transaction/etc.} - Pricing: {specifics} - Unit economics: {LTV, CAC, margins} ### 7. Traction - {Key metric 1}: {number} - {Key metric 2}: {number} - Growth: {rate} ### 8. Competition - 2×2 axes: {X axis} vs {Y axis} - Our position: {top-right quadrant and why} ### 9. Team - {Name}: {relevant credential} - {Name}: {relevant credential} ### 10. Financials | | Y1 | Y2 | Y3 | |---|-----|-----|-----| | Revenue | ${X} | ${X} | ${X} | ### 11. The Ask - Raising: ${X} - Use: {allocation} - Milestones: {what this funding achieves} ## Design Guidelines - Font size: ≥ 24pt (readable from back of room) - Max words per slide: 30-40 - One chart/visual per slide maximum
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-01 | fail→fail | 34,951 | 39,286 | +12% | 1 | 1 | 0% | 5,393 | 5,771 | +7% | 0 | 0 | — |
case-02 | fail→fail | 32,816 | 24,266 | -26% | 1 | 1 | 0% | 5,652 | 5,348 | -5% | 0 | 0 | — |
case-03 | fail→pass | 35,257 | 21,989 | -38% | 1 | 1 | 0% | 6,007 | 5,308 | -12% | 0 | 0 | — |
case-04 | pass→pass | 11,195 | 11,193 | -0% | 1 | 1 | 0% | 1,864 | 2,893 | +55% | 0 | 0 | — |
case-05 | pass→pass | 15,858 | 14,385 | -9% | 1 | 1 | 0% | 2,258 | 3,827 | +69% | 0 | 0 | — |
case-06 | pass→pass | 39,287 | 39,411 | +0% | 1 | 1 | 0% | 6,081 | 8,796 | +45% | 0 | 0 | — |
case-07 | pass→pass | 14,797 | 10,288 | -30% | 1 | 1 | 0% | 2,279 | 2,899 | +27% | 0 | 0 | — |
case-08 | pass→pass | 14,621 | 12,546 | -14% | 1 | 1 | 0% | 2,426 | 3,455 | +42% | 0 | 0 | — |
case-09 | pass→pass | 13,522 | 9,538 | -29% | 1 | 1 | 0% | 2,107 | 2,767 | +31% | 0 | 0 | — |
case-10 | pass→pass | 11,807 | 9,548 | -19% | 1 | 1 | 0% | 1,842 | 2,810 | +53% | 0 | 0 | — |
case-11 | fail→fail | 14,004 | 13,386 | -4% | 1 | 1 | 0% | 2,252 | 3,541 | +57% | 0 | 0 | — |
case-12 | pass→pass | 13,274 | 11,550 | -13% | 1 | 1 | 0% | 1,972 | 3,145 | +59% | 0 | 0 | — |
case-13 | fail→pass | 15,488 | 10,689 | -31% | 1 | 1 | 0% | 2,551 | 3,165 | +24% | 0 | 0 | — |
case-14 | pass→pass | 13,224 | 13,066 | -1% | 1 | 1 | 0% | 1,959 | 3,409 | +74% | 0 | 0 | — |
case-15 | fail→pass | 11,744 | 13,471 | +15% | 1 | 1 | 0% | 1,794 | 3,221 | +80% | 0 | 0 | — |
case-16 | pass→pass | 13,243 | 11,000 | -17% | 1 | 1 | 0% | 2,123 | 3,245 | +53% | 0 | 0 | — |
case-17 | pass→pass | 16,007 | 12,208 | -24% | 1 | 1 | 0% | 2,229 | 3,305 | +48% | 0 | 0 | — |
case-18 | pass→pass | 12,516 | 11,884 | -5% | 1 | 1 | 0% | 1,945 | 3,026 | +56% | 0 | 0 | — |
case-19 | pass→pass | 12,992 | 8,559 | -34% | 1 | 1 | 0% | 1,958 | 2,614 | +34% | 0 | 0 | — |
case-20 | pass→pass | 14,546 | 15,653 | +8% | 1 | 1 | 0% | 2,107 | 3,761 | +79% | 0 | 0 | — |
case-21 | pass→pass | 15,034 | 12,873 | -14% | 1 | 1 | 0% | 2,124 | 3,376 | +59% | 0 | 0 | — |
case-22 | pass→pass | 12,303 | 8,798 | -28% | 1 | 1 | 0% | 1,767 | 2,635 | +49% | 0 | 0 | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +14 percentage points is the difference between those two pass rates over the 22 comparable cases.
Without the skill loaded, the model failed this case. With it loaded, the same prompt on the same model passed. This is one improved case from the latest verified run; every case, including any that regressed, is in the table above.
Other measured skills in the registry, with their headline benchmark lift.