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
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 hits all the marks. It provides specific technical details about Micronaut testing patterns, includes natural trigger terms users would actually use, explicitly states when to use it, and even disambiguates from a related skill to prevent conflicts. The description is comprehensive yet focused.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and patterns: Mockito-first approach, @ExtendWith(MockitoExtension.class), @MicronautTest with @MockBean, HttpClient @Client("/") assertions, @Property overrides, @ParameterizedTest, and naming conventions (*Test vs *IT). | 3 / 3 |
Completeness | Clearly answers both what (write unit tests with specific patterns and annotations) and when ('Use when you need to write unit tests for Micronaut applications'). Also provides explicit guidance on when NOT to use it (framework-agnostic Java should use different skill). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'unit tests', 'Micronaut applications', 'Mockito', '@MicronautTest', '@MockBean', 'HttpClient', '@ParameterizedTest'. Also includes helpful disambiguation for 'framework-agnostic Java'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche (Micronaut-specific testing) and explicit disambiguation from the related Java testing skill (@131-java-testing-unit-testing). The Micronaut-specific annotations and patterns make it unlikely to conflict with general Java testing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill that excels at conciseness and workflow clarity with explicit validation checkpoints. The main weakness is the lack of inline code examples - the skill describes what patterns to use but defers all concrete examples to the reference file, which reduces immediate actionability for common cases.
Suggestions
Add at least one inline code example showing the Mockito-first pattern (pure JUnit 5 + Mockito without container boot) as a quick-start reference
Include a minimal @MicronautTest with @MockBean example to demonstrate the pattern without requiring navigation to the reference file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, listing only what Claude needs to know without explaining basic concepts. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | The skill provides clear constraints and workflow steps (compile before, verify after), but lacks concrete code examples - all executable guidance is deferred to the reference file rather than shown inline. | 2 / 3 |
Workflow Clarity | Clear sequence with explicit validation checkpoints: compile first, stop on failure, verify after changes. The MANDATORY/SAFETY/VERIFY structure provides excellent feedback loops for error prevention. | 3 / 3 |
Progressive Disclosure | Well-structured overview with clear one-level-deep reference to detailed guidance. The skill appropriately keeps the overview concise while signaling where to find examples and detailed rules. | 3 / 3 |
Total | 11 / 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
a886986
- 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.