Content
70%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 body delivers a well-sequenced, validation-rich 9-phase workflow with concrete commands and a ready-to-use beamer template. Its weaknesses are redundancy (key presentation rules stated twice) and a monolithic inline structure — long templates that should live in reference files, plus a PPTX export step specified only as instructions.
Suggestions
Move the full TALK_SCRIPT.md template (including the 8-question Q&A block), the per-talk-type slide tables, and the beamer template into reference files (e.g., references/talk-script-template.md, references/slide-templates.md) linked from the body, keeping SKILL.md as an overview.
Deduplicate the presentation rules: keep the Phase 2 rules table and have Key Rules reference it instead of restating 'one message per slide', '≥60% figure area', and font minimums verbatim.
Bundle an executable generate_pptx.py script (or a references/ implementation guide with runnable code) instead of describing its behavior as a spec Claude must implement from scratch.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient tables and commands, but there is real tightening material: 'One message per slide', 'figure ≥60% of slide area', font-size minimums, and progressive-disclosure rules each appear twice (Phase 2 rules table AND Key Rules); slide-count guidance is given in Constants and again per talk type; and the ~90-line TALK_SCRIPT/Q&A template pads the body. Not level 4 because the duplication exceeds 'minor instances'. | 3 / 5 |
Actionability | Copy-paste-ready beamer template, concrete bash commands (latexmk, pdfinfo, symlink commands), named MCP tools, and an explicit compile error-retry loop — but Phase 7 specifies generate_pptx.py as requirements for Claude to write rather than providing executable code or a bundled script, leaving a minor gap versus the fully executable level-5 anchor. | 4 / 5 |
Workflow Clarity | Phases 0-8 are explicitly sequenced with state persisted to SLIDES_STATE.json after each phase, an explicit STOP checkpoint with enumerated user options, a bounded compile-retry loop (max 3 attempts), pdfinfo page-count verification, and startup resume logic — a clear feedback-rich sequence. | 5 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent), and long inline material that belongs in reference files is monolithically embedded — the full TALK_SCRIPT template with 8 Q&A examples, the beamer template, and per-talk-type slide tables. The three shared-protocol links point outside the bundle ('../../shared-references/*.md') with unverifiable paths. Structure exists but content that should be split out is inline, matching level 3. | 3 / 5 |
Total | 15 / 20 Passed |