Ops Pitch Deck Agent Skill
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'.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/asgard-ai-platform/skills --skill ops-pitch-deckWhat comes with it
6 513 bytes besides the instructionThe instruction itself
7 sections, as written by the authorPitch Deck
Framework
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.
Standard Pitch Deck Structure (12 Slides)
| # | 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 |
Slide-by-Slide Guide
Problem Slide:
- Make the audience FEEL the pain
- Use a specific example or data point ("40% of SMBs spend 20+ hrs/month on manual invoicing")
- Avoid abstract problems ("businesses need better solutions")
Market Size:
- TAM = Total Addressable Market (if you captured 100%)
- SAM = Serviceable Addressable Market (your segment)
- SOM = Serviceable Obtainable Market (realistic 3-year target)
- Show methodology, not just a number
Traction Slide (most important for fundraising):
- Revenue curve (up and to the right)
- Growth rate (MoM or YoY)
- Key milestones: customers, partnerships, product launches
- If pre-revenue: waitlist, LOIs, pilot results
Competition Slide:
- 2×2 matrix, NOT a feature comparison table
- Choose axes that make you the clear winner in the top-right
- Include indirect competitors and substitutes
The Ask:
- Amount: specific number ("NT$30M Series A")
- Use of funds: top 3 allocations (product 40%, sales 35%, operations 25%)
- Milestones the funding enables ("reach $1M ARR, expand to 3 markets")
Output Format
# 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
Gotchas
- Traction trumps everything: A deck with amazing traction and mediocre design beats a beautiful deck with no traction. Lead with your strongest metric.
- Don't read slides aloud: Slides are visual aids. You tell the story; slides provide evidence. If you're reading bullets, there are too many bullets.
- "We have no competition" = red flag: Investors know this means you haven't researched. There's always competition — even if it's "doing nothing" or "using a spreadsheet."
- Financial projections WILL be questioned: "How did you get to $10M Y3?" Have a bottom-up model ready. Top-down market share assumptions are weak alone.
- Send a condensed version for email: The presentation deck (with minimal text, big visuals) differs from the email/read-ahead deck (more text, self-explanatory). Prepare both.
References
- For financial modeling behind the projections, see the fin-modeling skill
Other skills for the same job
different authors, same section of the catalogue
List OKX Agentic Wallet exclusive trading competitions, register users for contests, track participation and leaderboard rankings, and claim won rewards. Use when users want to list available trading competitions or trading cups, view competition rules / prize pool / total prizes, register or sign up or enroll or join a contest, check the leaderboard (who is winning) or their own rank (am I in the prize zone, what is my place), ask did I win or query participation / claim status, claim won rewards or prizes from completed competitions, see which wallet account they registered with, or submit Telegram / WeChat / Email / Twitter contact for prize delivery to top-tier winners.
Prepare for client review meetings with portfolio performance summary, allocation analysis, talking points, and action items. Pulls together account data into a concise meeting-ready format. Use before quarterly reviews, annual checkups, or ad-hoc client meetings. Triggers on "client review", "meeting prep for [client]", "quarterly review", "prep for [client name]", or "client meeting".
Draft concise morning meeting notes summarizing overnight developments, trade ideas, and key events for coverage stocks. Designed for the 7am morning meeting format — tight, opinionated, actionable. Triggers on "morning note", "morning meeting", "what happened overnight", "trade idea", "morning call prep", or "daily note".
Hunting skill for race condition vulnerabilities. Built from 12 public bug bounty reports including modern HTTP/2 single-packet attack cases (James Kettle DEF CON 2023 "Smashing the State Machine"; RyotaK / Flatt Security 10,000-request first-sequence-sync expansion 2024). Covers coupon double-redemption, gift-card double-spend, MFA-OTP-validate race, account-create race, faucet/crypto token double-mint, email-activation race, vote/upvote inflation, password-reset token race, rate-limit bypass via concurrent requests. Use when hunting race conditions, TOCTOU bugs, MFA-bypass-via-timing.
> Read Discord for financial research using opencli (read-only). Use this skill whenever the user wants to read Discord channels, search for messages in trading servers, view guild/channel info, monitor crypto or market discussion groups, or gather financial sentiment from Discord. "what's happening in the trading Discord", "show Discord channels", "list my servers", "Discord sentiment on BTC", "what are people saying in Discord about AAPL", "monitor crypto Discord", any mention of Discord in context of reading financial news, market research, or trading community discussions. This skill is READ-ONLY — it does NOT support sending messages, reacting, or any write operations.
> Expert SWIFT Customer Security Programme (CSP) advisor covering the Customer Security Controls Framework (CSCF v2026). Use this skill whenever a user asks about SWIFT CSP, CSCF controls, SWIFT security attestation, KYC-SA portal, SWIFT architecture types (A1/A2/A3/A4/B), mandatory vs advisory controls, independent assessment, SWIFT secure zone, secure flow zone, MFA for operators, SWIFT messaging security, payment fraud prevention on SWIFT, gap analysis for CSCF, or compliance with SWIFT's 32 controls Environment, Know and Limit Access, Detect and Respond. Control 2.4 (Back-Office Data Flow Security) is now mandatory in v2026. v2026 attestation window is July 1– December 31, 2026. Trigger for any SWIFT CSP or CSCF compliance question.
When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' or 'involuntary churn.' This skill covers voluntary churn (cancel flows, save offers, exit surveys) and involuntary churn (dunning, payment recovery). For post-cancel win-back email sequences, see email-sequence. For in-app upgrade paywalls, see paywall-upgrade-cro.
Expert SWIFT Customer Security Programme (CSP) advisor covering the Customer Security Controls Framework (CSCF v2026). Use this skill whenever a user asks about SWIFT CSP, CSCF controls, SWIFT security attestation, KYC-SA portal, SWIFT architecture types (A1/A2/A3/A4/B), mandatory vs advisory controls, independent assessment, SWIFT secure zone, secure flow zone, MFA for operators, SWIFT messaging security, payment fraud prevention on SWIFT, gap analysis for CSCF, or compliance with SWIFT's 32 controls (25 mandatory, 7 advisory in v2026) across the three objectives: Secure Your Environment, Know and Limit Access, Detect and Respond. Control 2.4 (Back-Office Data Flow Security) is now mandatory in v2026. v2026 attestation window is July 1– December 31, 2026. Trigger for any SWIFT CSP or CSCF compliance question.
How to use it
Take asgard-ai-platform/ops-pitch-deck from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.