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. Part of the skills-for-java project
74
67%
Does it follow best practices?
Impact
Pending
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 unit testing), lists specific concrete patterns and annotations, provides explicit 'Use when' guidance, and even includes disambiguation from a related skill. The only minor issue is the use of second person 'you' in 'you need to', but since the rubric penalizes first/second person on specificity and the rest of the description is so strong, the impact is minimal.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and patterns: Mockito with @ExtendWith(MockitoExtension.class), @MicronautTest with @MockBean, HttpClient @Client("/") assertions, @Property overrides, @ParameterizedTest, and naming conventions (*Test vs *IT). These are highly specific technical capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (write unit tests for Micronaut apps using specific patterns and annotations) and 'when' (opens with 'Use when you need to write unit tests for Micronaut applications'). Also provides explicit disambiguation guidance pointing to a different skill for framework-agnostic Java testing. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms: 'unit tests', 'Micronaut applications', 'Mockito', '@MicronautTest', '@MockBean', 'HttpClient', '@ParameterizedTest'. Users asking about Micronaut testing would naturally use these terms. Also distinguishes from framework-agnostic Java testing with a cross-reference. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Micronaut testing with explicit differentiation from framework-agnostic Java testing ('For framework-agnostic Java use @131-java-testing-unit-testing'). The Micronaut-specific annotations and patterns create a clear niche unlikely to conflict with other skills. | 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 body functions primarily as a pointer to a reference file rather than a standalone actionable guide. While the constraints section is well-structured with clear safety steps, the complete absence of code examples, patterns, or concrete guidance means Claude must always load the reference file to do anything useful. The skill would benefit significantly from including at least minimal executable examples for the core patterns (Mockito-first test, @MicronautTest with @MockBean, HttpClient test).
Suggestions
Add at least 2-3 minimal but complete code examples inline: a pure Mockito test with @ExtendWith(MockitoExtension.class), a @MicronautTest with @MockBean, and an HttpClient blocking exchange test.
Include a brief decision guide (e.g., a 3-line flowchart or table) for when to use Mockito-first vs @MicronautTest vs escalating to @522, rather than deferring all decision logic to the reference.
Add a concrete example of @Property usage and @ParameterizedTest with @CsvSource since these are listed as covered but have zero actionable content in the body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but the 'What is covered in this Skill?' bullet list is somewhat redundant with the reference file and the description. The constraints section is lean and useful. Some tokens spent on meta-description rather than actionable content. | 2 / 3 |
Actionability | No concrete code examples, no executable commands beyond mvnw compile/verify, and no specific patterns shown. Everything actionable is deferred to the reference file. The skill body describes rather than instructs — there's no copy-paste ready code for Mockito-first tests, @MockBean usage, or HttpClient assertions. | 1 / 3 |
Workflow Clarity | The constraints section provides a clear compile-before-change and verify-after sequence with a stop condition on failure, which is good. However, the actual testing workflow (when to use Mockito-first vs @MicronautTest, how to structure tests) is entirely absent from the body and deferred to the reference. | 2 / 3 |
Progressive Disclosure | There is a clear reference to a single detailed file, which is good one-level-deep disclosure. However, the overview/quick-start layer is too thin — it provides no substantive content before sending the reader to the reference, making the skill body feel like a table of contents rather than a useful overview. | 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
1847adc
- 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.