Content
81%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 is a strong, fully executable single-command skill with excellent failure-mode documentation via the exit-code table and clear scope boundaries. Its main weaknesses are a repetitively over-explained conditional-governance paragraph and an entrypoint script reference (`helpers/fill_docx.py`) that is not included in the bundle.
Suggestions
Collapse the conditional-governance explanation to a single statement, e.g. 'The IF_<X> marker is governed exclusively by <X>_PACKAGE (required when the conditional appears); a bare <X> key is unused and never affects keep/drop.'
Include the referenced `helpers/fill_docx.py` in the skill bundle (or state where the pinned runtime provides it) so the CLI usage and frontmatter entrypoint resolve to a real file.
Add a short example of the input JSON data object (2-3 fields) so the expected data shape is executable without inference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient (CLI block, exit-code table, tight scope lists), but the conditional-governance paragraph restates the same rule roughly three times — "never acts as an alias or fallback", "never affects keep/drop", and "so an unused bare RELOCATION key cannot stand in for a missing RELOCATION_PACKAGE" — which could be tightened to one sentence. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trim level of 4. | 3 / 5 |
Actionability | The guidance is fully executable: a copy-paste-ready CLI invocation with all three required arguments, a concrete worked example with real paths, a complete exit-code table mapping every failure mode, and explicit dependencies. This matches the 'fully executable; copy-paste ready; specific examples cover the common cases' anchor. | 5 / 5 |
Workflow Clarity | This is a simple single-action skill (run one CLI command) and the action is unambiguous; the exit-code table provides explicit validation semantics and error-recovery guidance for every failure mode (invalid JSON, mismatched conditionals, missing fields, unresolved markers). The destructive-operation cap does not apply since inputs are never modified and a new output file is written. | 5 / 5 |
Progressive Disclosure | Sections are well-organized and appropriately placed for a self-contained single-purpose skill (when-to-use, scope, guarantees, CLI, example, dependencies) with no nested references. It falls short of 5 because the entrypoint referenced in frontmatter and CLI usage, `helpers/fill_docx.py`, is not present in the bundle (no references/, scripts/, or assets/ directories exist), leaving a dangling reference — a minor organization gap matching 'good structure; most content appropriately placed; minor organization gaps'. | 4 / 5 |
Total | 17 / 20 Passed |