Content
78%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: lean sections, concrete build/test commands with pre- and post-change validation gates, and a clean one-level-deep reference split that was verified against the actual bundle. Main weaknesses are the verbatim duplication of the description's trigger list, the absence of an inline @ChangeUnit example, and the lack of a recovery loop when post-change verification fails.
Suggestions
Add a minimal inline @ChangeUnit example (class, id, order, @Execution method, rollback method) so the most common task can be started without opening references/316-frameworks-spring-mongodb-migrations-mongock.md.
In workflow step 4, add a feedback loop for verification failure: fix and re-run `mvn clean verify`, or stop and report the failure — mirroring the existing SAFETY gate on compilation.
Remove the "When to use this skill" section or compress it to one line, since it duplicates the frontmatter description's trigger phrases word-for-word.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean with no concept teaching and no padding — every section is instructional (constraints, workflow, references). It falls short of a 5 because the "When to use this skill" section repeats the frontmatter description's five trigger phrases verbatim, and the "What is covered" bullets partially duplicate the Constraints and Reference sections. | 4 / 5 |
Actionability | Concrete, executable commands are given ("Run `./mvnw compile` or `mvn compile`", "`./mvnw clean verify`", "`mongock.enabled=false`", "`mongock.migration-scan-package`") plus specific files to inspect and read. Not a 5 because the most common task — writing a `@ChangeUnit` class — has no inline example; the code shape is only available after opening the reference files. | 4 / 5 |
Workflow Clarity | A clear 4-step workflow with explicit validation checkpoints: "MANDATORY: Run `./mvnw compile`... before applying any change", "SAFETY: If compilation fails, stop immediately", and "VERIFY: Run `./mvnw clean verify`... after", plus edge-case and external-runtime gates. Not a 5 because step 4 ("Execute build/tests... Summarize outcomes") is generic and there is no fix-and-retry feedback loop for what to do when verification fails; not a 3 because pre- and post-change validation checkpoints are explicit, so the database/batch cap does not apply. | 4 / 5 |
Progressive Disclosure | The body is a concise overview with three well-signaled, topically split references (main guidelines, antipatterns, parallel change), each linked both in workflow step 1 and in a dedicated Reference section. All three files exist and contain no further nested references, so navigation is exactly one level deep — matching the level-5 anchor. | 5 / 5 |
Total | 17 / 20 Passed |