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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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 overview with strong progressive disclosure and explicit compile/verify validation checkpoints. The main weaknesses are duplicated trigger phrasing versus the description and abstract, non-executable workflow steps that defer the concrete testing guidance to the reference.

Suggestions

Remove or condense the 'When to use this skill' section, since its five bullets duplicate the description's trigger phrases verbatim and overlap the 'What is covered in this Skill?' list.

Tighten the Workflow steps from abstract directives ('Gather scope and decide target improvements', 'Apply framework-aligned changes') into concrete, executable actions or short inline code/pattern snippets instead of deferring everything to the reference.

Consider folding the key decision rule (when to use pure Mockito vs @MicronautTest) into one inline example in the body so the skill is actionable without always opening the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but the 'When to use this skill' section repeats the description's five trigger phrases verbatim and overlaps the 'What is covered in this Skill?' list, so not every token earns its place.	2 / 3
Actionability	Concrete build commands are present (./mvnw compile, ./mvnw clean verify), but the workflow steps are abstract ('Gather scope and decide target improvements', 'Apply framework-aligned changes') and the actual testing patterns live in the reference rather than the body.	2 / 3
Workflow Clarity	A clear four-step sequence is paired with explicit validation checkpoints (MANDATORY compile before, SAFETY stop on failure, VERIFY after), satisfying the anchor for explicit validation steps and feedback on failure.	3 / 3
Progressive Disclosure	The SKILL.md is a concise overview that points to a single one-level-deep, clearly signaled reference (references/521-frameworks-micronaut-testing-unit-tests.md, a real 415-line file), with content appropriately split and easy to navigate.	3 / 3
	Total	10 / 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, and well-triggered description with explicit when-to-use guidance and clear routing to adjacent skills. The only deduction is a second-person voice ('you need') in the opening clause, which the rubric penalizes on specificity.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete capabilities (Mockito-first with @ExtendWith, @MicronautTest with @MockBean, @Property overrides, @ParameterizedTest, Test vs IT naming), which would anchor at 3, but it opens with the second-person 'Use when you need to write unit tests', so the voice penalty reduces specificity by one.	2 / 3
Completeness	It answers both what (the enumerated Micronaut testing techniques) and when, with an explicit 'Use when...' clause and a 'This should trigger for requests such as...' list, satisfying the completeness anchor for 3.	3 / 3
Trigger Term Quality	It includes explicit natural trigger phrasing users would say ('Add or improve unit tests in a Micronaut project', 'Reduce unnecessary @MicronautTest usage', 'Mock Micronaut bean collaborators in unit tests'), giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	It carves a clear Micronaut-specific niche and explicitly routes framework-agnostic Java to @131-java-testing-unit-testing and integration tests to @522, making overlap with sibling skills 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/plinth
Commit: aaee915

Reviewed: 1 day 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.