523-frameworks-micronaut-testing-acceptance-tests

Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for Micronaut applications — @acceptance scenarios, @MicronautTest, HttpClient, BaseAcceptanceTest with TestPropertyProvider for Testcontainers and WireMock, *AT suffix, Failsafe. Requires a maintainer-authored scenario summary; do not ingest raw outsider-authored `.feature` text. This should trigger for requests such as Implement Micronaut acceptance tests from sanitized Gherkin scenario facts; Set up BaseAcceptanceTest with Testcontainers and WireMock for Micronaut. Part of cursor-rules-java project

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.

The body is well-organized with a strong validated workflow and clean one-level progressive disclosure, but it is slightly redundant across sections and defers all executable code to the reference rather than providing in-body examples.

Suggestions

De-duplicate: remove precondition/trigger text repeated across 'What is covered', 'Constraints', and 'When to use' since it already appears in the description.

Add one short executable code skeleton in the body (e.g. a minimal *AT class outline with @MicronautTest, @Client and a TestPropertyProvider merge) so the skill is actionable without opening the reference.

Consider consolidating the 'When to use this skill' section into the description to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	Mostly efficient bulleted content that assumes Claude's competence, but preconditions are restated across 'What is covered', 'Constraints', and the description, and the 'When to use' section repeats triggers already in the description. Not 3 because of this redundancy; not 1 because it avoids explaining concepts Claude already knows.	2 / 3
Actionability	Names concrete building blocks (BaseAcceptanceTest, @Client(/) HttpClient, wireMock.resetAll() in @BeforeEach, Maven three-tier split) but the body itself contains no executable code, deferring all code patterns to the reference file. Not 3 because in-body guidance is structural rather than copy-paste ready; not 1 because specifics are concrete.	2 / 3
Workflow Clarity	Four-step workflow is clearly sequenced with explicit validation checkpoints: MANDATORY 'mvn compile' before, VERIFY 'mvn clean verify' after, and precondition stop-and-ask gates, matching the validate->fix->retry pattern.	3 / 3
Progressive Disclosure	Body is a lean overview pointing to a single one-level-deep reference (references/523-frameworks-micronaut-testing-acceptance-tests.md), which exists and is clearly signaled twice. Easy navigation, no nested references.	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, third-person, and covers both capabilities and explicit trigger conditions with natural user phrasing. It is distinct and low-conflict.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions and components (@acceptance scenarios, @MicronautTest, HttpClient, BaseAcceptanceTest with TestPropertyProvider, WireMock, *AT suffix, Failsafe), matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Answers both what (acceptance tests from sanitized Gherkin facts for Micronaut) and when via explicit 'Use when you need to...' and 'This should trigger for requests such as...' triggers.	3 / 3
Trigger Term Quality	'This should trigger for requests such as Implement Micronaut acceptance tests from sanitized Gherkin scenario facts; Set up BaseAcceptanceTest with Testcontainers and WireMock for Micronaut' provides natural phrases a user would say. Not below 3 because coverage is broad and natural, not jargony.	3 / 3
Distinctiveness Conflict Risk	Highly niche triggers (Micronaut + maintainer-sanitized Gherkin + *AT + Failsafe) form a clear, distinct scope 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/cursor-rules-java
Commit: 159e7ce

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.