Content
85%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 highly actionable, well-validated skill body with excellent code coverage and a clear verification feedback loop, but the advanced OOXML/tracked-changes/comments material is inlined in SKILL.md with no bundle files to offload it, weakening progressive disclosure.
Suggestions
Move the lengthy 'Raw OOXML (advanced)' tracked-changes, comments, and traps detail into a reference file (e.g. references/ooxml-advanced.md) and link to it from a short summary, reducing SKILL.md token load.
Keep only a one-paragraph orientation plus a single small code example in the advanced section, pointing to the reference for the full XML patterns and ID rules.
Consider splitting the LibreOffice conversion block into a small scripts/ helper or reference note so the main body stays focused on the primary python-docx workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and mostly lean — code is presented without explaining what python-docx or OOXML are — but the advanced tracked-changes/comments section is long and carries detail (e.g. full pPr ordering, paraId bounds) that is borderline over-explanation for a top-level SKILL.md, keeping it just below score 5. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready code blocks for read, create, page setup, find-and-replace, conversion, and raw OOXML, plus specific traps and verify commands, covering the common and advanced cases. | 5 / 5 |
Workflow Clarity | Destructive/batch XML operations get an explicit validation feedback loop: the raw-OOXML workflow is sequenced (read part → edit → re-zip) and the 'Verify before returning' section mandates reopening, testzip, and lxml parse with implied fix-and-retry, matching the score-5 anchor with explicit checkpoints. | 5 / 5 |
Progressive Disclosure | There are no bundle files (references/, scripts/, assets/ all absent) and the body is a single ~150-line monolith with the advanced tracked-changes/comments material inlined rather than split into a separate reference file; structure via headers exists but content that belongs in a separate file is inline, matching the score-3 anchor. | 3 / 5 |
Total | 17 / 20 Passed |