Content
66%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is a highly actionable, well-sequenced pitch-deck builder with an explicit, checklist-driven Delivery Gate workflow and sound one-level-deep deferral to the pptx base skill. Its chief weakness is conciseness: heavy repetition of the same VC-domain rules (hockey-stick, Use-of-Funds, '$'-strip) and coaching of fundraising concepts Claude already knows inflate the token budget without adding executable value.
Suggestions
Deduplicate the repeated rules: state the hockey-stick axismin=0 rule, the 4-bucket Use-of-Funds convention, and the single-quote '$' escape once in their primary sections, then reference them ('→ see §...') from the ship-check, Gate 5b, Gate 6, and Known Issues instead of restating each.
Trim VC-psychology coaching that Claude already knows (e.g., 'VCs will not trust a single number', 'read co-founder, passionate in 0 seconds', 'student project') down to the operational QA check it motivates, keeping the grep/query condition and dropping the rationale prose.
Move the executable Gate 6 bash script and the per-recipe geometry/coordinate tables into a references/ file (e.g. GATES.md, RECIPES.md) and point to them from SKILL.md, so the overview stays lean while keeping the full operational detail one level deep.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~810-line body is noticeably verbose: it repeatedly coaches fundraising domain knowledge Claude already has (hockey-stick y-axis explained 4+ times, Use-of-Funds 3+ times, '$'-strip 3+ times, VC-psychology asides like 'VCs read co-founder, passionate in 0 seconds'), fitting 'Noticeably verbose; several unnecessary explanations or padded sections' over the 'some unnecessary explanation' of 3. | 2 / 5 |
Actionability | Most recipes give fully executable, copy-paste officecli commands with complete props and real values (Cover, Problem batch JSON, Market/Traction charts, Ask pie), plus executable QA one-liners and the full Gate 6 script; a few abbreviate with '# Repeat for cards 2/3' (x-positions and grid math still given) or defer a full batch to pptx v2 base — minor gaps keeping it at 4 rather than 5. | 4 / 5 |
Workflow Clarity | The build path is a clearly sequenced, fragile process (stage diagnosis → vertical template → 10-recipe arc → Delivery Gate) with explicit validation checkpoints and feedback loops — 'Only proceed when validation passes', Gate 5b 'If ANY defect — REJECT', Gate 6 PASS/REJECT/WARN with exit 1, fix-and-re-validate — plus a 9-point Gate 5b checklist and 6-point Gate 6 checklist. | 5 / 5 |
Progressive Disclosure | No bundle files exist; the single SKILL.md is well-sectioned with clear headers and relies on well-signaled, one-level-deep deferrals to the sibling base skill ('→ see pptx v2 §X'), which is genuinely good disclosure toward that base — but bulk content that could be split into reference files (arc templates, recipe geometry tables, the Gate 6 script) is inlined, a minor organization gap landing it at 4. | 4 / 5 |
Total | 15 / 20 Passed |