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 highly actionable, well-validated workflows with excellent command-level specificity and feedback loops for every risky operation. Its weaknesses are token-heavy inline design catalogs and JSON schema documentation that belong in reference files, and mandatory referenced files (html2pptx.md, ooxml.md) that are absent from the bundle.
Suggestions
Move the 18 example color palettes and the Visual Details Options catalog (~90 lines) into a reference file such as references/design-options.md and keep a one-line pointer plus 2-3 examples in SKILL.md.
Move the full inventory JSON schema documentation (shape/paragraph property tables) into a reference file or the inventory.py docstring, keeping only a compact example in SKILL.md.
Ensure the mandatory referenced files html2pptx.md, ooxml.md, and ooxml/scripts/{unpack,validate,pack}.py actually ship in the skill bundle, or inline a minimal syntax cheat-sheet for html2pptx since that step currently has no executable example.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The workflow sections are efficient, but ~90 lines are design-catalog padding: 18 full hex palettes ("Coastal Rose: Old rose... beaver... eggshell"), long "Visual Details Options" lists, and duplicated design checklists ("State your approach" appears in both Design Principles and Requirements). Mostly efficient but could be tightened, matching the 3 anchor rather than the 2 anchor since no space is spent explaining concepts Claude already knows. | 3 / 5 |
Actionability | Concrete, executable commands throughout ("python scripts/rearrange.py template.pptx working.pptx 0,34,34,50,52", "pdftoppm -jpeg -r 150 -f 2 -l 5"), real validation-error examples, and a complete replacement JSON example. Not a 5 because the html2pptx step only says "Create and run a JavaScript file using the html2pptx.js library" with no inline executable example. | 4 / 5 |
Workflow Clarity | Every fragile workflow has explicit validation and feedback loops: "CRITICAL: Validate immediately after each edit and fix any validation errors before proceeding", "Repeat until all slides are visually correct" for thumbnail checks, revision-conflict retry for ppt_edit, and replace.py shape/overflow validation with sample error output — a direct match to the 5 anchor. | 5 / 5 |
Progressive Disclosure | References are clearly signaled and one level deep, and all five scripts/ files referenced in the body exist in the bundle, but the two "MANDATORY" reads (html2pptx.md and ooxml.md) are not present in the bundle, and ~50 lines of inventory JSON schema documentation plus the design catalogs are inlined in SKILL.md instead of split into reference files — matching the 3 anchor ('content that should be separate is inline'). | 3 / 5 |
Total | 15 / 20 Passed |