Content
78%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 is a strong, executable guide: a robust self-validating setup, concrete conventions, and copy-paste Python covering deck creation and Excel-model binding. The main gaps are the absence of any bundle files (shared setup logic and the pitch-deck checklist are inlined) and no explicit validation of the saved output.
Suggestions
Move the shared environment setup into a scripts/ helper (e.g. scripts/setup-docs-env.sh) and invoke it in one line, since the block is identical to the microsoft-office/pdf skills.
Move the 13-slide pitch-deck checklist to references/pitch-deck-structure.md with a one-line pointer from the body.
Add an explicit output validation step after prs.save (e.g., re-open the .pptx with python-pptx and confirm the slide count) to close the workflow's one checkpoint gap.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is directive and assumes competence ("Never transcribe numbers from memory or from a summary — open the workbook, read the named range"), with no padding explaining PowerPoint or how python-pptx works, matching "Efficient; minor instances of over-explanation that could be trimmed". Not 5 because the ~25-line commented venv-construction block and the provenance/attribution material are trimmable or movable overhead. | 4 / 5 |
Actionability | Every example is complete, executable code with concrete paths: the bash setup block, the template-loading snippet, add_picture with Inches coordinates, the full deck skeleton ending in prs.save("./out/pitch-aurora.pptx"), and the openpyxl named-range resolver — together covering the common cases (setup, title/table/chart slides, model binding). Matches "Fully executable; copy-paste ready code or commands; specific examples cover the common cases"; nothing is pseudocode. | 5 / 5 |
Workflow Clarity | A clear sequence is implied by section order — validated setup (the bash block self-checks imports), optional firm template, build slides, bind numbers to a recalculated workbook, save to ./out/, return the path — with the recalculation warning acting as a data checkpoint, matching "Clear sequence with most checkpoints present; minor validation gaps". Not 5 because the sequence is never enumerated and there is no validation of the saved output (e.g., re-opening the .pptx); not 3 because checkpoints do exist in setup and data binding. | 4 / 5 |
Progressive Disclosure | The file is well-sectioned and navigable, but it is a ~190-line monolith with no bundle: the setup block is stated to be "the same block as the microsoft-office/pdf skills" and the 13-item pitch-deck checklist ("Not prescriptive, but useful as a starting skeleton") is inline reference material, matching "Some structure but could be better organized... content that should be separate is inline". Not 4 because the shared setup logic and checklist genuinely belong in a script/reference file; not 2 because headers are clear and nothing is a wall of text. | 3 / 5 |
Total | 16 / 20 Passed |