Content
52%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 a strong decision tree, concrete commands, and a well-sequenced redlining workflow with verification, but it is undermined by broken bundle navigation — every referenced file and script path (ooxml.md, docx-js.md, ooxml/scripts/unpack.py and pack.py) is absent, and the actual bundled scripts are never surfaced. Moderate redundancy (duplicated overview, repeated batching guidance, a filler 'When to Use' section) also costs tokens without adding guidance.
Suggestions
Fix progressive disclosure first: either add the missing ooxml.md, docx-js.md, and ooxml/scripts/unpack.py & pack.py files, or rewrite the references to point at the actual bundle (e.g. scripts/document.py, scripts/utilities.py) so the mandatory "READ ENTIRE FILE" steps resolve.
Trim redundancy: drop the verbatim duplicate of the description in the Overview, merge the duplicated batching guidance (steps 2 and 4), and delete the empty "When to Use" section.
Close the feedback loop in the redlining workflow's final verification: state explicitly what to do when a grep check finds the original phrase or an unintended change (e.g. re-grep the batch, fix, re-pack, and re-verify).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient commands, but it re-explains a concept Claude already knows ("A .docx file is essentially a ZIP archive containing XML files and other resources"), duplicates the frontmatter description verbatim in the Overview, repeats batching guidance twice ("Batch organization" in step 2 and "Suggested batch groupings" in step 4), and ends with a vacuous section ("This skill is applicable to execute the workflow or actions described in the overview."). This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' (3); it is above 2 because the bulk is actionable commands, not padding. | 3 / 5 |
Actionability | There is concrete, executable guidance (pandoc flags, soffice/pdftoppm commands, a GOOD/BAD OOXML tracked-changes example, dependency installs, grep-based verification), but the core workflows hinge on files that do not exist in the bundle: "Read [`ooxml.md`](ooxml.md)", "Read [`docx-js.md`](docx-js.md)", and "python ooxml/scripts/unpack.py" / "pack.py" are all missing, and the bundled scripts/document.py and scripts/utilities.py are never referenced. This lands at 3 ('some concrete guidance but incomplete; missing key details') rather than 4 because the primary editing/creation paths cannot actually be executed as written. | 3 / 5 |
Workflow Clarity | A decision tree routes each task type, the redlining workflow is well sequenced with batching ("Test each batch before moving to the next"), a just-in-time checkpoint ("Always grep word/document.xml immediately before writing a script"), and an explicit final verification (pandoc conversion plus grep checks for original/replacement phrases and unintended changes). It falls short of 5 because the verification step has no explicit fix-and-retry loop if a check fails, and the create/edit workflows have no verification at all — 'clear sequence with most checkpoints present; minor validation gaps' (4). | 4 / 5 |
Progressive Disclosure | Scored against the actual bundle: the body's references — docx-js.md, ooxml.md, ooxml/scripts/unpack.py, ooxml/scripts/pack.py — point to files that do not exist anywhere in the skill, while the real bundle contents (scripts/document.py, scripts/utilities.py, scripts/templates/) are never mentioned in SKILL.md. Navigation is therefore broken in both directions, matching the anchor for 2 ('minimal structure; references are buried/lead nowhere'); it is not 1 because the body itself is well sectioned and self-contained. | 2 / 5 |
Total | 12 / 20 Passed |