From example-skills
Create compelling pitch decks for startups, projects, and internal proposals. Covers narrative structure, slide design principles, data visualization, and audience-specific adaptation. Triggers on pitch deck creation, presentation design, or fundraising deck requests.
npx claudepluginhub organvm-iv-taxis/a-i--skills --plugin document-skillsThis skill uses the workspace's default tool permissions.
Build presentations that communicate vision, demonstrate value, and compel action.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Designs and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Designs, implements, and audits WCAG 2.2 AA accessible UIs for Web (ARIA/HTML5), iOS (SwiftUI traits), and Android (Compose semantics). Audits code for compliance gaps.
Build presentations that communicate vision, demonstrate value, and compel action.
| Slide | Purpose | Time |
|---|---|---|
| 1. Title | Name, tagline, contact | 15s |
| 2. Problem | Pain point with evidence | 1min |
| 3. Solution | How you solve it | 1min |
| 4. Demo/Product | Show, don't tell | 2min |
| 5. Market | TAM/SAM/SOM, growth | 1min |
| 6. Business Model | How you make money | 1min |
| 7. Traction | Metrics, milestones, users | 1min |
| 8. Team | Why this team wins | 30s |
| 9. Ask | What you need, what they get | 30s |
| 10. Contact | CTA, next steps | 15s |
Hook → Pain → Failed Solutions → Your Insight → Product → Evidence → Vision → Ask
Best for: Markets where the problem is well-known but solutions are bad.
Vision → Why Now → How → Product → Traction → Team → Ask
Best for: Category-creating products where the vision is the differentiator.
Results → How We Did It → The Market → The Team → What's Next → Ask
Best for: Growth-stage pitches where numbers speak louder than vision.
BAD: Slide with 5 bullet points, a chart, and a screenshot
GOOD: One clear statement + one supporting visual
A viewer should grasp the slide's point within 3 seconds. If they can't, simplify.
1. Headline (largest, boldest) → The claim
2. Key visual (chart/screenshot) → The evidence
3. Supporting text (smallest) → The context
| Data Type | Best Chart | Avoid |
|---|---|---|
| Trend over time | Line chart | Pie chart |
| Comparison | Bar chart | 3D chart |
| Part of whole | Stacked bar, treemap | Pie chart (>5 segments) |
| Relationship | Scatter plot | Table |
| Single metric | Large number | Any chart |
┌─────────────────────────────┐
│ │
│ 47% │
│ reduction in deploy time │
│ │
│ (from 45min to 24min) │
│ │
└─────────────────────────────┘
Formula: Specific pain + Quantified impact + Who feels it
"Engineering teams waste 15 hours/week on manual deployment tasks.
For a 50-person team, that's $1.2M/year in lost productivity."
Formula: What it does + How it's different + Key benefit
"One-click deployment pipelines that integrate with your existing
CI/CD stack. No migration needed — install and deploy in 5 minutes."
TAM/SAM/SOM Framework:
Show growth trajectory, not just current numbers:
Month 1: 50 users
Month 3: 500 users
Month 6: 5,000 users
Month 12: 50,000 users (projected)
Focus on: Why this team? Not resume bullets, but relevant achievements.
"Previously built and sold DevToolCo (acquired by BigCorp).
15 years combined experience in CI/CD infrastructure.
Early engineers at [credible company]."
| Audience | Emphasize | De-emphasize |
|---|---|---|
| Investors | Market, traction, team | Technical details |
| Technical | Architecture, scalability | Business model |
| Executives | ROI, risk, timeline | Implementation details |
| Internal | Impact, resources needed | Market analysis |