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 skill body: lean constraints, a sequenced workflow with verification checkpoints, and exemplary one-level-deep progressive disclosure into a real, command-rich reference file. Its main weaknesses are redundancy (duplicated trigger list, triple reference pointer, coverage bullets restating the workflow) and the absence of any inline failure-handling guidance.
Suggestions
Remove the 'When to use this skill' section — it duplicates the frontmatter description's trigger phrases verbatim — and drop the 'BEFORE APPLYING' constraint or the '## Reference' section so the reference file is pointed to exactly once.
Replace the 'What is covered in this Skill?' bullet list with the Workflow section itself, since the bullets restate the same steps without adding information.
Add one line of failure guidance to Workflow step 4 (e.g., 'If verification fails, report the failing Maven goal and the corrective action before retrying') so the error-recovery loop exists in the body, not only in the reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | No concept over-explanation, but there is noticeable redundancy: the five trigger phrases from the description are repeated verbatim in 'When to use this skill', the reference file is pointed to three times ('BEFORE APPLYING' constraint, Workflow step 1, and the '## Reference' section), and the 'What is covered in this Skill?' bullets largely restate the Workflow steps. This fits anchor 3 ('could be tightened') better than 4, where only minor trimming would be needed. | 3 / 5 |
Actionability | Concrete commands are present for the checkpoints ('sdk version', './mvnw clean verify', 'mvn clean verify') and constraints are specific (Java 25, Micronaut 4.x, Maven-only, non-empty-directory guard). The core creation command ('mn create-app ... --build=maven --jdk=25 ...') lives only in the reference file — an acceptable progressive-disclosure split since the body mandates reading the reference first, but it leaves a minor gap that keeps this below 5. | 4 / 5 |
Workflow Clarity | The four-step workflow is clearly sequenced with validation on both ends: prerequisite check ('sdk version' before anything else) and post-creation verification ('./mvnw clean verify', with an mvnw fallback), plus a safety checkpoint on non-empty target directories. It falls short of anchor 5 because the body has no error-recovery loop if verification fails — what to do on failure is only in the reference. | 4 / 5 |
Progressive Disclosure | The body is a genuine overview that pushes all command-level detail (SDKMAN candidate management, 'mn create-app' syntax) into exactly one reference file, which exists, is one level deep, and is clearly signaled by a dedicated '## Reference' section with a proper markdown link. This matches the anchor-5 pattern of a clear overview with well-signaled, one-level-deep references. | 5 / 5 |
Total | 16 / 20 Passed |