Content
77%Reviews 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, actionable, well-sequenced operational guide with real validation feedback loops for the fragile OOXML and replacement operations. Its weaknesses are verbosity (inline palettes and design prose that don't earn their tokens) and a progressive-disclosure gap: two critical referenced files are missing from the bundle.
Suggestions
Add the missing reference files html2pptx.md and ooxml.md to the bundle (or point the MANDATORY 'Read entirely' instructions at paths that exist), since the creation and editing workflows currently depend on files that are absent.
Move the 18 inline example color palettes and the visual-details/geometric/border/typography catalogs into a separate reference file (e.g. design-reference.md) and keep SKILL.md as an overview, recovering conciseness and fixing the inline content that should be split out.
Trim the motivational design coaching ('Be adventurous', 'Think beyond defaults', topic-color clichés) to a few concrete rules; Claude already understands design tradeoffs and these tokens do not earn their place.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly operational but carries padding that Claude doesn't need — eighteen inline example color palettes with hex codes (lines 78-95), motivational design coaching ('Be adventurous', 'Think beyond defaults', 'a healthcare presentation doesn't have to be green'), and a long catalog of visual-detail options (lines 97-143). This matches the level-2 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the level-3 'every token earns its place'. | 2 / 3 |
Actionability | Provides concrete, copy-paste-ready commands throughout — `python -m markitdown path-to-file.pptx`, `python scripts/rearrange.py template.pptx working.pptx 0,34,34,50,52`, `python scripts/replace.py working.pptx replacement-text.json output.pptx`, `soffice --headless --convert-to pdf` — plus full executable JSON schemas, matching the level-3 'fully executable code/commands; copy-paste ready' anchor rather than the pseudocode at level 2. | 3 / 3 |
Workflow Clarity | Each workflow is a clearly numbered sequence with explicit validation checkpoints and feedback loops: editing has 'CRITICAL: Validate immediately after each edit ... python ooxml/scripts/validate.py'; creation has 'Repeat until all slides are visually correct'; replacement has shape-existence and overflow validation with error examples. This matches the level-3 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor and is not capped at 2 because validation is present for the destructive/batch OOXML operations. | 3 / 3 |
Progressive Disclosure | Structure and one-level-deep markdown links are well signaled, but the bundle is missing two MANDATORY referenced files the body instructs Claude to read fully — `html2pptx.md` (line 152) and `ooxml.md` (line 177) are not present in the bundle — and large content that should be separate (the 18 palettes, visual-detail catalog, and full JSON schemas) is inlined in SKILL.md. This matches the level-2 'content that should be separate is inline' rather than the level-3 'content appropriately split; easy navigation', and is above level-1 because it is not a monolithic wall with nested references. | 2 / 3 |
Total | 10 / 12 Passed |