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; Write Mockito-first unit tests for Micronaut services; Mock Micronaut bean collaborators in unit tests; Review fast Micronaut tests without application context. Part of Plinth Toolkit

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, concise body with a clear validated workflow and clean one-level progressive disclosure, held back only by deferring all code examples to the reference rather than including any inline executable snippet.

Suggestions

Add one short inline Mockito-first example (e.g. a @ExtendWith(MockitoExtension.class) test stub) so the body is actionable without requiring the reference read for common cases.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Claude's knowledge of Micronaut/JUnit/Mockito, and never explains basic concepts; every section earns its place, with only mild redundancy from the trigger list recurring from the description.	3 / 3
Actionability	Concrete commands are present (./mvnw compile, mvn clean verify) and specific annotations are named, but all executable code examples are deferred to the reference file rather than shown inline, leaving the body without copy-paste-ready code.	2 / 3
Workflow Clarity	The four-step workflow is clearly sequenced with explicit validation checkpoints (MANDATORY compile before, VERIFY clean verify after) and a stop-on-failure feedback loop ('If compilation fails, stop immediately').	3 / 3
Progressive Disclosure	SKILL.md is a concise overview that points to a single one-level-deep reference (references/521-frameworks-micronaut-testing-unit-tests.md), referenced multiple times and clearly signaled; navigation is easy and the bundle path is real.	3 / 3
	Total	11 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description with explicit triggers and clear disambiguation against a sibling skill, weakened only by second-person phrasing that costs it a specificity point.

Suggestions

Rewrite the opening in third person to avoid the second-person penalty, e.g. 'Use when writing unit tests for Micronaut applications — Mockito-first with ...'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities (@ExtendWith(MockitoExtension.class), @MockBean, HttpClient @Client(/), @Property, @ParameterizedTest, Test vs IT naming), which would warrant a 3, but the description uses second-person voice ('Use when you need to write...'), which the rubric penalizes by reducing specificity by one point.	2 / 3
Completeness	Clearly answers both 'what' (Mockito-first unit tests with named Micronaut annotations) and 'when' ('Use when you need to write unit tests for Micronaut applications' plus an explicit trigger list).	3 / 3
Trigger Term Quality	Natural user phrasings are explicitly enumerated ('Add or improve unit tests in a Micronaut project', 'Reduce unnecessary @MicronautTest usage', 'Mock Micronaut bean collaborators'), giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Niche is clearly scoped to Micronaut and explicitly disambiguated from the framework-agnostic counterpart ('For framework-agnostic Java use @131-java-testing-unit-testing'), making wrong-skill triggering unlikely.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Path: skills/521-frameworks-micronaut-testing-unit-tests/SKILL.md
Commit: fdaf68c

Reviewed: about 3 hours ago

Table of Contents

Discovery Implementation Validation

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.