Content
50%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 content is well-structured with concrete commands and a thorough redlining workflow, but its two main workflows depend on mandatory-read files (docx-js.md, ooxml.md) and scripts (ooxml/scripts/unpack.py, pack.py) that are absent from the bundle, and the basic editing workflow lacks a validation checkpoint. This makes otherwise actionable guidance incomplete in practice.
Suggestions
Ship the referenced docx-js.md and ooxml.md files (or correct the references to point at the actual bundle, e.g. scripts/document.py for the Document library), since both creation and editing workflows mark them MANDATORY.
Fix the script paths: the bundle uses 'scripts/' and contains document.py/utilities.py but no unpack.py or pack.py — either add those scripts or point the unpack/pack commands at the real files.
Add an explicit validate-and-retry checkpoint to the 'Basic OOXML editing' workflow so destructive edits are checked before repacking, mirroring the redlining final-verification step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient with concrete commands, but includes unnecessary repetition (batch-grouping options 'By section/By type/By proximity' are listed in both step 2 and step 4) and padding ('A .docx file is essentially a ZIP archive containing XML files...' repeats what Claude knows, plus a vague 'When to Use' line), keeping it at 'mostly efficient but could be tightened' rather than the lean 4. | 3 / 5 |
Actionability | Concrete executable commands are present (pandoc, soffice, pdftoppm, a real tracked-changes XML example), but the two primary workflows gate their detail behind files that do not exist in the bundle ('docx-js.md', 'ooxml.md') and invoke scripts at a path that is absent ('ooxml/scripts/unpack.py', 'pack.py'), so key execution details are missing — incomplete rather than just minor gaps. | 3 / 5 |
Workflow Clarity | The redlining workflow is well-sequenced with a final verification step (pandoc + grep checks) and grep-before-script guidance, but the 'Basic OOXML editing' workflow is a destructive operation with no validation checkpoint, triggering the destructive/batch cap that precedence-forces workflow clarity to 3. | 3 / 5 |
Progressive Disclosure | Structure is good (clear decision tree, well-organized sections) and the references to docx-js.md/ooxml.md are clearly signaled and one level deep, but those referenced files do not exist in the actual bundle and the cited script paths ('ooxml/scripts/...') do not match the provided 'scripts/' directory, so navigation is broken rather than merely having minor gaps. | 3 / 5 |
Total | 12 / 20 Passed |