522-frameworks-micronaut-testing-integration-tests

Use when you need to write or improve integration tests for Micronaut — @MicronautTest, HttpClient, TestPropertyProvider with Testcontainers, transactional test mode where appropriate, and Maven Surefire/Failsafe splits for *Test, *Tests, *IT, and *AT. This should trigger for requests such as Add Micronaut integration tests with Testcontainers; Wire dynamic datasource or broker URLs for @MicronautTest; Write @MicronautTest integration tests with Testcontainers; Configure replacement beans for Micronaut integration tests; Review Micronaut integration test lifecycle and resources. Part of Plinth Toolkit

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

75%

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

A well-structured overview that defers detail to a single real reference and includes compile/verify checkpoints in its workflow. Its main weakness is the redundant, repetitive Constraints section and the lack of any inline executable test patterns.

Suggestions

Collapse the six near-identical compilation-safety bullets into one or two statements (e.g. 'Stop if `mvn compile` fails; run `mvn clean verify` after changes') to reduce repetition.

Add at least one small inline example (e.g. a minimal @MicronautTest + TestPropertyProvider snippet) so the body is actionable without forcing a reference read for common cases.

Trim the duplicated 'When to use' list since the same triggers already appear verbatim in the frontmatter description.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, but the Constraints section repeats the same compilation-safety idea six times ('MANDATORY', 'PREREQUISITE', 'CRITICAL SAFETY', 'BLOCKING CONDITION', 'NO EXCEPTIONS', 'VERIFY'), adding unnecessary padding Claude does not need.	2 / 3
Actionability	It gives a few concrete commands ('./mvnw compile', 'mvn clean verify') and names the reference file, but the actual integration-test guidance is deferred to the reference rather than providing executable patterns inline, so it is incomplete as a standalone instruction set.	2 / 3
Workflow Clarity	The Workflow is a clear four-step sequence with explicit compile-before and verify-after checkpoints, satisfying the validation-checkpoint requirement even though the body itself is short.	3 / 3
Progressive Disclosure	The body is a concise overview that points to a single real, one-level-deep reference file (references/522-frameworks-micronaut-testing-integration-tests.md, verified to exist), with the path signaled in both the Workflow and Reference sections.	3 / 3
	Total	10 / 12 Passed

Description

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.

The description is specific, trigger-rich, and clearly answers both what the skill does and when to use it, with a well-scoped Micronaut niche. It is well above the missing-trigger cap and shows no over-claiming or fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and mechanisms — '@MicronautTest, HttpClient, TestPropertyProvider with Testcontainers, transactional test mode' and 'Maven Surefire/Failsafe splits for Test, Tests, IT, and AT' — matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Opens with an explicit 'Use when you need to write or improve integration tests for Micronaut' trigger and lists concrete capabilities plus example requests, clearly answering both what and when.	3 / 3
Trigger Term Quality	Echoes natural request phrasing such as 'Add Micronaut integration tests with Testcontainers' and 'Wire dynamic datasource or broker URLs', giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to Micronaut integration testing with framework-specific triggers (@MicronautTest, TestPropertyProvider, Surefire/Failsafe splits), making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 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.