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.
This is a strong, expert-oriented skill body: a sequenced workflow with real validation checkpoints and feedback loops, concrete tooling and path guidance, and disciplined routing to adjacent skills. The few gaps are cosmetic — slight reinforcement redundancy of the two-hats rule, deferred commands in reference files that are not part of this bundle, and a broken bullet list in the References section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and expert-level, assuming competence (Mikado method, Hyurn-aware contracts, Rule of Three, SATD, expand-contract are invoked without explanation) and wasting no tokens teaching known concepts. It stays below anchor 5 only because the two-hats rule ("never mix behavior changes") is restated in the Goal, When NOT to use, workflow steps 1 and 9, and Guardrail 5 — reinforcement that could be trimmed. | 4 / 5 |
Actionability | As an instruction-only skill the guidance is concrete: named tools (lizard, radon, jscodeshift, OpenRewrite, ast-grep, comby), concrete paths (`.agents/results/refactor/*.md`, `.git-blame-ignore-revs`), an output contract, and a decision procedure per workflow step. It misses anchor 5 mainly because executable commands (e.g., the git forensics commands) are deferred to `resources/measurement.md`, which is not present in this bundle. | 4 / 5 |
Workflow Clarity | The canonical workflow is a clearly sequenced 9-step path with explicit validation (re-run existing tests unchanged after each single transformation, commit separately), an explicit feedback loop (Mikado: record prerequisite, undo only that transformation, recurse), a failure/recovery table covering seven failure modes, and explicit exit criteria. This matches anchor 5's "clear sequence with explicit validation steps; feedback loops for error recovery". | 5 / 5 |
Progressive Disclosure | The body is well structured with clear sections and a References list that signals each external resource with a one-line description, all one level deep (e.g., "Invariant definition (5 properties, boundaries, destination, naming roles...): `resources/definition.md`"). It falls short of anchor 5 because the referenced files (`resources/*.md`, `../_shared/core/*.md`) do not resolve within this bundle, and a stray blank line between the first and second reference bullets breaks the list rendering. | 4 / 5 |
Total | 17 / 20 Passed |