本文へ移動
cccskills
無料GitHub で公開

pitch-deck-reviewer

Score 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.

インストール方法を見る

含まれるファイル(4)

  • SKILL.md3.4 KB
  • assets/deck_summary_template.md941 B
  • references/pitch_deck_heuristics.md5.4 KB
  • scripts/deck_structure_scorer.py9.3 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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


Clarify First

Before scoring the deck, confirm these inputs. If any is unknown or vague, ASK — do not assume:

  • Funding stage — seed vs Series A sets the required-slide rubric (--stage flag) and what counts as a gap
  • Slide-by-slide summary — one bullet per slide (number + title + 1-2 sentences); vague summaries produce false gaps
  • Round context — amount raising and traction stage, so the "ask" and "traction" slides are judged against the right bar

Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.


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.

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.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

This skill should be used when the user asks to "check accessibility", "audit WCAG compliance", "scan HTML for a11y issues", "check color contrast", or "find accessibility violations in web pages".

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9002026年10月7日 更新

Design and run statistically rigorous A/B tests and experiments. Use when planning experiments, calculating sample sizes, designing test variants, selecting metrics, analyzing results, or when someone says "let's test that."

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9002026年10月7日 更新

Design and analyze A/B tests: sample size, test duration, and statistical significance for conversion experiments. Use when setting up an A/B test, calculating sample size, designing an experiment, or analyzing results.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9002026年10月7日 更新

Sales execution across pipeline, discovery, demos, negotiation, and closing. Use when qualifying opportunities, running MEDDIC discovery, building account plans, handling objections, structuring proposals, or forecasting pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9002026年10月7日 更新

Design ad creative across Google, Meta, LinkedIn, Twitter/X, and TikTok with platform format specs, headline formulas, and A/B testing. Use when writing ad copy, generating headline variations, creating ad sets, or validating creative.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9002026年10月7日 更新

aeo

無料

Answer Engine Optimization (AEO): optimize content to be cited by LLMs (ChatGPT, Claude, Perplexity, Gemini) in their answers. Use when designing content for LLM citation, auditing citability, or structuring Q&A schema.

日本語の概要は準備中です。原文の説明を表示しています。

borghei/Claude-Skills9002026年10月7日 更新

borghei のスキルをすべて見る

このスキルの問題を報告する