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.
A strong, highly actionable skill body with excellent workflow sequencing and validated destructive-operation handling, backed by a genuine, well-organized reference bundle. Its main cost is length: the duplicated intro and reference-grade table detail inflate the always-loaded context beyond what an overview needs.
Suggestions
Delete the opening paragraph that duplicates the frontmatter description word-for-word, or reduce it to one sentence.
Trim the Commands and MCP Tools table cells to a purpose plus a pointer (e.g., 'see references/cli-reference.md#security') — move suppression syntax, rule catalogues, and tuning-knob defaults into the CLI reference.
Move the full Issue Types catalogue and Node.js Bindings field reference into references/ and keep only the most common issue types and a minimal bindings example inline.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with genuinely tool-specific facts, but the opening paragraph restates the frontmatter description verbatim, and the Commands and MCP Tools tables carry paragraph-length digressions (the `security` and `health` rows embed suppression syntax and rule catalogues; `ci reconcile-review` embeds a full behavior spec) that belong in references/cli-reference.md. Mostly efficient, but more than minor tightening is possible. | 3 / 5 |
Actionability | Every section gives copy-paste-ready commands with exact flags (`fallow dead-code --format json --quiet --workspace 'apps/*'`), concrete exit-code semantics, JSON envelope shapes, and executable Node.js binding examples. The Instructions section converts user requests directly into specific commands. | 5 / 5 |
Workflow Clarity | Multi-step processes are explicitly sequenced with validation checkpoints: the Safe auto-fix cycle is preview (--dry-run) → review → apply (--yes) → verify, Agent Rule 6 mandates dry-run before fix, and the destructive-fix path documents the non-TTY exit-code-2 failure mode with recovery guidance. | 5 / 5 |
Progressive Disclosure | Three well-signaled, one-level-deep references (cli-reference.md, gotchas.md, patterns.md) exist on disk with clear purpose descriptions and no nested chaining beyond a sibling cross-link. However, a substantial amount of reference-grade detail (full flag inventories, MCP parameter defaults, the issue-type catalogue) is inlined in SKILL.md rather than split out, keeping it short of fully appropriate placement. | 4 / 5 |
Total | 17 / 20 Passed |