Content
56%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-sequenced workflows with real validation loops for editing and visual QA, but it is noticeably bloated with design-catalog padding and carries broken references: the mandatory html2pptx.md and ooxml.md files are absent from the bundle. The template workflow also lacks a final output-verification step.
Suggestions
Move the 18 example color palettes and the Visual Details Options / Typography Treatments catalogs into a reference file (e.g., design-catalog.md) and keep only a short pointer in SKILL.md; delete the filler 'When to Use' section and the verbatim Overview repeat.
Fix the broken references: either include html2pptx.md and ooxml.md in the bundle or correct their paths, and add a minimal inline html2pptx() JavaScript example so the creation workflow survives a missing reference file.
Add a final visual-validation step to the template workflow (thumbnail the output.pptx and check for overflow/placeholder issues) to match the feedback loops present in the other two workflows.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Several sections are padded: the Overview repeats the description verbatim, ~150 lines catalog 18 example color palettes and design-brainstorm lists ('Diagonal section dividers', 'Rotated text headers at 90° or 270°') that assume Claude lacks design knowledge it has, and the 'When to Use' section is pure filler ('This skill is applicable to execute the workflow or actions described in the overview.'). Not 3: this is multiple dedicated padded sections, not incidental over-explanation. | 2 / 5 |
Actionability | Mostly executable: exact commands (python -m markitdown, soffice --headless --convert-to pdf, pdftoppm -jpeg -r 150), full inventory/replacement JSON schemas, and concrete script invocations (python scripts/rearrange.py template.pptx working.pptx 0,34,34,50,52). Not 5: the from-scratch workflow defers to html2pptx.md, which is missing from the bundle, with no inline html2pptx() JS example, and the unpack.py path is hedged ('If the script doesn't exist at this path, use find . -name "unpack.py"'). | 4 / 5 |
Workflow Clarity | All three workflows are clearly numbered, and two have explicit feedback loops: the editing workflow mandates 'Validate immediately after each edit and fix any validation errors before proceeding', and the creation workflow says 'Repeat until all slides are visually correct'. Not 5: the template workflow (a batch operation across all slides) ends at replace.py with no final output-verification step. Not 3: validation checkpoints are explicit, not implicit. | 4 / 5 |
Progressive Disclosure | Sections are well-organized and references are clearly signaled one level deep, but scored against the actual bundle: the two MANDATORY reference docs (html2pptx.md, ooxml.md) and the ooxml/scripts/ helper scripts referenced by the body do not exist in the bundle, and the ~150-line palette/visual-design catalog that belongs in a separate reference file is fully inlined. Not 4: dead links on mandatory workflow steps and the inlined catalog are more than minor organization gaps. | 3 / 5 |
Total | 13 / 20 Passed |