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

83%

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

71%Weight 40%Scale 1-5

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

Well-structured overview with strong progressive disclosure and explicit validation checkpoints, but the body delegates the actual test-writing examples to the reference, leaving its actionability moderate.

Suggestions

Inline one minimal executable example (e.g., a Mockito-first @ExtendWith(MockitoExtension.class) test or an @MicronautTest + @MockBean snippet) so the body is actionable without requiring the reference read for common cases.

Tighten the 'What is covered' list to avoid restating techniques already enumerated in the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The body is efficient with bullet lists and a short 4-step workflow, assuming Claude's competence; minor overlap between the 'What is covered' list and the frontmatter description could be trimmed.	4 / 5
Actionability	Concrete build commands are present (./mvnw compile, mvn clean verify) but the core test-writing guidance (@MockBean, @MicronautTest, @ParameterizedTest examples) is delegated to the reference with only vague phrasing like 'following the reference patterns', leaving key details out of the body.	3 / 5
Workflow Clarity	A clear 4-step sequence with explicit validation gates (MANDATORY compile before, stop on compilation failure, VERIFY clean verify after) acting as checkpoints; the individual workflow steps themselves are somewhat abstract ('Apply framework-aligned changes'), keeping it just below 5.	4 / 5
Progressive Disclosure	The body is a concise overview pointing to a single one-level-deep reference (references/521-frameworks-micronaut-testing-unit-tests.md, verified to exist), clearly signaled in both Workflow step 1 and the Reference section with a markdown link; content is appropriately split.	5 / 5
	Total	16 / 20 Passed

Description

95%Weight 40%Scale 1-5

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 concrete capabilities, natural trigger phrases, and explicit sibling-skill disambiguation. The only weakness is second-person voice in the opening clause, which caps specificity at 4.

Suggestions

Rephrase the opening to third-person/impersonal voice (e.g., 'Use when writing unit tests for Micronaut applications') to avoid the second-person specificity penalty.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete techniques (@ExtendWith(MockitoExtension.class), @MockBean, @Client(/) assertions, @Property, @ParameterizedTest, Test vs IT naming) covering the domain comprehensively; reduced from 5 because the opening 'Use when you need to write' uses second-person voice, which the rubric penalizes by one point on specificity.	4 / 5
Completeness	Explicitly answers both what (Micronaut unit testing with the enumerated techniques) and when (a dedicated 'This should trigger for requests such as...' clause with concrete trigger phrases).	5 / 5
Trigger Term Quality	Includes natural request phrasings a user would say ('Add or improve unit tests in a Micronaut project', 'Write Mockito-first unit tests for Micronaut services', 'Mock Micronaut bean collaborators', 'Review fast Micronaut tests without application context') with synonym coverage across add/improve/write/mock/review.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Micronaut unit testing) and explicitly disambiguates with 'For framework-agnostic Java use @131-java-testing-unit-testing', minimizing overlap with sibling skills.	5 / 5
	Total	19 / 20 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/plinth
Path: skills/521-frameworks-micronaut-testing-unit-tests/SKILL.md
Commit: 05bf9d1

Reviewed: 8 minutes 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.