pitch-deck-reviewer
Score a pitch deck (provided as text/markdown summary of slides) against YC, Sequoia, and a16z heuristics — does it have the right slides in the right order with the right content? Use before sending a deck to investors, practicing pitch with a co-founder, or when the user mentions pitch deck, fundraising deck, seed deck, or Series A deck review.
What this skill does
# Pitch Deck Reviewer Score a pitch deck's structure against the YC / Sequoia / a16z heuristics. > **Note:** This evaluates *structure*, not *content quality*. A perfectly-structured deck for a bad business is still a bad pitch. But a poorly-structured deck for a great business often gets passed. --- ## Keywords pitch deck, pitch, fundraise, fundraising, seed deck, Series A deck, investor deck, slide deck, YC, Y Combinator, Sequoia, a16z --- ## Quick Start 1. Summarize each slide as one bullet in `deck_summary.md` (slide number + title + 1-2 sentences of content) 2. Run: `python scripts/deck_structure_scorer.py deck_summary.md` 3. Address gaps; iterate --- ## Core Workflows ### Workflow 1: Pre-Send Deck Review 1. Summarize deck slide-by-slide in `deck_summary.md` 2. Run scorer 3. Add missing slides (the scorer flags by category) 4. Re-order if structure flow is off 5. Pair with `documents/pptx-toolkit/` for actual pptx audit **Time Estimate:** 1-2 hours per major deck iteration. ### Workflow 2: First Deck Build (No Existing Deck) 1. Read `references/pitch_deck_heuristics.md` 2. Use the structure rubric (10-15 slides covering specific topics) 3. Draft slide-by-slide 4. Validate as Workflow 1 **Time Estimate:** 1-2 weeks for first complete draft. --- ## Tools ### deck_structure_scorer.py Reads a markdown file describing the deck slide-by-slide and scores it against required slides per stage. ```bash python scripts/deck_structure_scorer.py deck_summary.md python scripts/deck_structure_scorer.py deck_summary.md --json # For Series A python scripts/deck_structure_scorer.py deck_summary.md --stage series-a ``` Stages: `seed` (default), `series-a`. --- ## Reference Guides - **`references/pitch_deck_heuristics.md`** — YC, Sequoia, a16z deck structure heuristics; common mistakes; stage differences --- ## Templates - **`assets/deck_summary_template.md`** — Slide-by-slide summary template --- ## Best Practices - **One idea per slide.** If you can't summarize it in one sentence, split it. - **Numbers, not adjectives.** "Strong growth" is weak. "$80k → $312k MRR over 12 months" is strong. - **Order matters.** Most decks under-invest in problem framing and the "why now" slide. - **Don't ship 30+ slides.** A seed deck is 10-12 slides; a Series A deck is 12-15. - **Demo is not the deck.** Decks introduce; demos persuade. Plan both.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.