Content
77%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 highly actionable — every workflow carries concrete, copy-paste-ready commands with explicit validation checkpoints and error-recovery loops. Its two weaknesses are padded generic design advice (~120 lines of palettes and visual-detail catalogs inlined in SKILL.md) and broken progressive disclosure: the two MANDATORY reference files (html2pptx.md, ooxml.md) and the ooxml/scripts/* utilities the workflows depend on are not present in the bundle.
Suggestions
Ship html2pptx.md and ooxml.md in the bundle (and fix the ooxml/scripts/unpack.py, validate.py, pack.py paths) — both are marked MANDATORY reads but do not exist, so two of the three main workflows dead-end immediately.
Move the 18-palette color catalog and the 'Visual Details Options' lists into a one-level-deep reference file (e.g., references/design.md) and keep a two-line pointer in SKILL.md.
Tighten the template workflow by moving the full inventory-JSON schema example and formatting-pattern lists into the scripts' documentation or a reference file, keeping only the essential field notes inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The operational cores are lean ('python -m markitdown path-to-file.pptx', 'soffice --headless --convert-to pdf template.pptx', 'pdftoppm -jpeg -r 150 template.pdf slide'), but ~120 lines are generic design advice Claude does not need in context: 18 example color palettes ('Classic Blue: Deep navy (#1C2833)...'), catalogs like 'Rotated text headers at 90° or 270°', and reminders like 'Ensure readability: strong contrast'. This sits between level 3 ('mostly efficient but some unnecessary explanation or could be tightened') and level 2 ('several unnecessary explanations or padded sections') — the palette/visual-details blocks are genuine padding, but they are concentrated in one section while the rest is dense, so 3 fits better than 2. | 3 / 5 |
Actionability | Quotes: 'python ooxml/scripts/unpack.py <office_file> <output_dir>', 'python scripts/rearrange.py template.pptx working.pptx 0,34,34,50,52', 'python scripts/thumbnail.py output.pptx workspace/thumbnails --cols 4', plus a complete replacement-JSON example with real field names ('placeholder_type', 'space_before', 'theme_color'). Commands are copy-paste ready and cover the common cases — the level-5 anchor; not level 4 because there are no significant gaps in executable detail. | 5 / 5 |
Workflow Clarity | Quotes: editing workflow step 4 'CRITICAL: Validate immediately after each edit and fix any validation errors before proceeding: python ooxml/scripts/validate.py <dir> --original <file>', template workflow 'Repeat until all slides are visually correct', and replace.py's documented overflow/validation errors ('ERROR: Replacement text made overflow worse...'). Clear numbered sequences with explicit validation, feedback loops, and error-recovery guidance for the destructive/batch operations (slide deletion, automatic text clearing) — the level-5 anchor; the batch-operations cap of 3 does not apply because validation is present throughout. | 5 / 5 |
Progressive Disclosure | Quotes: 'Read [html2pptx.md](html2pptx.md) completely' and 'Read [ooxml.md](ooxml.md) (~500 lines)' — both marked MANDATORY, but neither file exists in the bundle (scripts/ contains only html2pptx.js, inventory.py, rearrange.py, replace.py, thumbnail.py; ooxml/scripts/unpack.py, validate.py, and pack.py are also absent). Scoring against the actual bundle structure per the judging guidelines: navigation to the two core reference documents is broken, and large reference-style content (the palette catalog, full inventory-JSON schema) is inlined in SKILL.md. This is worse than level 4 ('references mostly clear; minor organization gaps') and matches level 3 ('content that should be separate is inline' plus references that cannot be followed). | 3 / 5 |
Total | 16 / 20 Passed |