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.
A dense, highly actionable CLI reference with excellent executable examples and a clear layering strategy. Its weaknesses are organization rather than content: the giant inline element-type tables belong in split reference files, and the bundle assets are unused, which caps progressive disclosure.
Suggestions
Move the per-format element-type tables (pptx/docx/xlsx rows) into separate reference files (e.g. references/docx-types.md) and link to them one level deep, leaving SKILL.md as an overview.
Add an explicit gated validation loop for destructive/batch operations — e.g. "After edits: run `validate`; if errors, fix and re-validate; only when valid, run `save`/`close`" — to turn the post-step verify hint into a checkpoint sequence.
Either reference the assets/ and showcase/ files where relevant (e.g. example output screenshots) or remove them from the bundle so the file structure matches the body's navigation.
Tighten the dense parenthetical feature lists in the element-type tables by promoting only the common cases inline and pointing to help output for the long tail.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence — no concept re-explanation, just command syntax, value formats, and pitfalls — but the monolithic per-format element-type tables cram an enormous feature inventory into dense parentheticals that could be trimmed or split out. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready commands throughout (Quick Start for all three formats, get/query/set/add examples, batch JSON, pivot-table construction) with specific examples covering the common cases. | 5 / 5 |
Workflow Clarity | Clear L1→L2→L3 strategy layering, an explicit help-first feedback philosophy ("One help query beats guess-fail-retry loops"), and verification guidance ("verify with validate and/or view issues"), plus batch atomic-rollback error handling — but verification is framed as a post-step rather than a strict gated validate→fix→retry loop. | 4 / 5 |
Progressive Disclosure | Section structure is clear and the load_skill sub-skills are well-signaled with "When to use" tables, but the bulk element-type reference is inlined in a single monolithic file with no per-format reference files, and the provided assets/ bundle is not referenced or wired into the body. | 3 / 5 |
Total | 16 / 20 Passed |