Content
71%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 well-structured overview body with excellent progressive disclosure into a single reference file and a validated workflow (compile-before, verify-after). Its main cost is token redundancy: duplicated trigger lists and triple-stated compile constraints that add tokens without new information.
Suggestions
Remove the 'When to use this skill' section (or replace with one line), since it duplicates the frontmatter description's trigger phrases verbatim.
Consolidate the Constraints section: state the compile-before rule once (e.g. 'MANDATORY: run ./mvnw compile before applying changes; if it fails, stop and let the user resolve errors') instead of three overlapping bullets.
Make workflow steps 2–3 slightly more concrete by tying them to the reference's example numbering (e.g. 'match findings against the applicable examples in the reference') so the body instructs rather than describes.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean, but 'When to use this skill' repeats the frontmatter description verbatim and the Constraints section states the compile-before rule three times ('Compile before JDBC refactors', 'MANDATORY: Run ./mvnw compile', 'PREREQUISITE: Project must compile'), which could be tightened into one instruction. | 3 / 5 |
Actionability | Concrete commands are present ('./mvnw compile', 'mvn clean verify') with a real reference path to read first, but workflow steps like 'Gather scope and decide target improvements' and 'Apply framework-aligned changes' remain high-level, delegating specifics entirely to the reference. | 4 / 5 |
Workflow Clarity | The 4-step workflow is clearly sequenced with explicit checkpoints — compile before applying changes, 'If compilation fails, stop immediately', and verify afterward. It falls short of a 5 because error recovery is only 'stop and let the user resolve' rather than a fix-and-revalidate feedback loop. | 4 / 5 |
Progressive Disclosure | The SKILL.md is a concise overview (coverage bullets, constraints, workflow) and all detailed rules/examples live in the single, real, one-level-deep reference file, signaled both in workflow step 1 and in a linked '## Reference' section. | 5 / 5 |
Total | 16 / 20 Passed |