borghei/Claude-Skills / personal-productivity/pitch-deck-reviewer
pitch-deck-reviewer
VerifiedScore a pitch deck's structure and content against YC, Sequoia, and a16z heuristics. Use before sending a deck to investors, practicing a pitch, or reviewing a seed or Series A fundraising deck.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.8 KB |
| assets/deck_summary_template.md | markdown | 941 B |
| references/pitch_deck_heuristics.md | markdown | 5.4 KB |
| scripts/deck_structure_scorer.py | script | 9.3 KB |
assets/deck_summary_template.md
View on GitHub# Pitch Deck Summary — [Company Name]
Write one bullet per slide: slide number + title + 1-2 sentences of content. Keep it tight; the scorer reads this for structure not detail.
---
1. **Title / vision** — [Company name + 1-line "what we do"]
2. **Problem** — [The pain in customer language]
3. **Why now** — [Recent shift that makes this newly possible / urgent]
4. **Solution / product** — [How we solve, with visual]
5. **Market size** — [Bottoms-up TAM with sourcing]
6. **Business model** — [How we charge, unit economics teaser]
7. **Traction** — [Hard numbers — MRR, customers, growth]
8. **Competition** — [Landscape map, our differentiation]
9. **Team** — [Founders + relevant background]
10. **Ask / round** — [Raising $X, milestones it buys, timeline]
---
(Optional additional slides — only if substantive)
11. **Roadmap** — [Next 12-18 months]
12. **Vision** — [Where this goes 5-10 years out]
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |