521-frameworks-micronaut-testing-unit-tests
Use when you need to write unit tests for Micronaut applications — Mockito-first with @ExtendWith(MockitoExtension.class), @MicronautTest with @MockBean, HttpClient @Client(/) assertions, @Property overrides, @ParameterizedTest, and *Test vs *IT naming. For framework-agnostic Java use @131-java-testing-unit-testing. This should trigger for requests such as Add or improve unit tests in a Micronaut project; Reduce unnecessary @MicronautTest usage with Mockito-first tests. Part of cursor-rules-java project
59
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/521-frameworks-micronaut-testing-unit-tests/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its scope (Micronaut-specific unit testing), lists concrete patterns and annotations, provides explicit trigger guidance with example requests, and proactively distinguishes itself from a related skill. The cross-reference to the framework-agnostic Java testing skill is a particularly strong differentiator.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and patterns: Mockito-first with @ExtendWith(MockitoExtension.class), @MicronautTest with @MockBean, HttpClient @Client(/) assertions, @Property overrides, @ParameterizedTest, and *Test vs *IT naming conventions. | 3 / 3 |
Completeness | Clearly answers both 'what' (Mockito-first testing patterns, @MicronautTest with @MockBean, HttpClient assertions, etc.) and 'when' with an explicit 'Use when' clause at the start and concrete trigger examples ('Add or improve unit tests in a Micronaut project; Reduce unnecessary @MicronautTest usage'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'unit tests', 'Micronaut', 'Mockito', '@MicronautTest', '@MockBean', 'HttpClient', '@ParameterizedTest', plus explicit example triggers like 'Add or improve unit tests in a Micronaut project'. Also distinguishes from framework-agnostic Java testing with a cross-reference. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Micronaut unit testing and explicitly differentiates from framework-agnostic Java testing by referencing '@131-java-testing-unit-testing' as the alternative. This cross-reference significantly reduces conflict risk. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is structured as a lightweight dispatcher to a reference file, but it offloads too much — there are no concrete code examples, patterns, or executable guidance in the SKILL.md itself. The workflow and constraints provide reasonable safety guardrails, but the lack of any inline examples (e.g., a Mockito-first test skeleton, a @MockBean pattern, an HttpClient assertion) means Claude would need to read the reference file before being able to do anything useful. The skill would benefit significantly from including at least one or two key code patterns inline.
Suggestions
Add at least 2-3 concrete, executable code examples inline: a Mockito-first test (no @MicronautTest), a @MicronautTest with @MockBean, and an HttpClient blocking exchange test pattern.
Integrate the compile/verify commands directly into the workflow steps rather than separating them into a constraints section, and add an explicit feedback loop for test failures.
Replace the 'What is covered in this Skill?' bullet list with a concise quick-start section showing the most common pattern (Mockito-first test), saving the full catalog for the reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably concise but includes some unnecessary elements like the 'What is covered in this Skill?' bullet list that largely duplicates the description and workflow. The 'Scope' line is also somewhat redundant. However, it avoids explaining concepts Claude already knows. | 2 / 3 |
Actionability | The skill contains no concrete code examples, no executable commands beyond generic mvnw invocations, and no specific patterns for Mockito-first testing, @MockBean usage, or HttpClient assertions. All actionable content is deferred to the reference file, making the SKILL.md itself vague and descriptive rather than instructive. | 1 / 3 |
Workflow Clarity | The workflow has a clear 4-step sequence with compilation and verification checkpoints mentioned in constraints. However, the steps themselves are abstract ('Apply framework-aligned changes', 'Gather scope') rather than concrete, and the validation steps in the constraints section are separated from the workflow, reducing clarity. The compile-before/verify-after pattern is good but lacks an explicit feedback loop for test failures. | 2 / 3 |
Progressive Disclosure | The skill references a single detailed reference file with a clear path, which is good one-level-deep disclosure. However, since no bundle files were provided, we cannot verify the reference exists. The SKILL.md itself is too thin — it offloads nearly all actionable content to the reference, leaving the main file as mostly a table of contents rather than a useful quick-start overview with key patterns inline. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
3b97275
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.