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 tight, high-signal skill body: correct routing across create/edit/read, precise gotchas, executable pipelines with built-in validation and repair loops, and a well-structured script bundle. The two minor gaps are the absence of any assembled creation example and small redundancies in the redlining/tracked-changes discussion.
Suggestions
Add a minimal complete docx-js 'hello world' script (page size, one heading, one styled paragraph) under the gotchas so the Create path is executable end-to-end like the edit path.
Dedupe the redlining --author guidance: keep it either in the pipeline code comment or the Tracked changes prose, not both, and tighten the accept_changes/pandoc empty-bullet discussion to one statement plus the two tool-specific bullets.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and assumes competence ('The model knows the API; these are the footguns') with exact, non-obvious values (DXA 1440 = 1″, ShadingType.CLEAR vs SOLID, w:delText vs w:t), but has minor trimmable redundancy — e.g. the --author redlining validation is stated in the pipeline comment and restated in prose in the same section. | 4 / 5 |
Actionability | The edit, verify, and comment workflows give copy-paste-ready bash with real script paths and flags, but the Create path — one of the three task types in the routing table — provides precise API gotchas without even a minimal assembled example script. | 4 / 5 |
Workflow Clarity | Sequences are explicit with validation checkpoints and feedback loops: the edit pipeline embeds validate.py --original with --auto-repair for error recovery and an --author check that every edit is tracked, and created files get a render-to-PDF → rasterize → visually inspect verification loop. | 5 / 5 |
Progressive Disclosure | A task→approach routing table up front, all referenced bundle files (scripts/office/soffice.py, scripts/office/validate.py, scripts/merge_runs.py, scripts/accept_changes.py, scripts/comment.py, scripts/templates/) exist one level deep, and implementation detail appropriately lives in the scripts rather than being inlined. | 5 / 5 |
Total | 18 / 20 Passed |