523-frameworks-micronaut-testing-acceptance-tests
Use when you need to implement acceptance tests from a Gherkin .feature file for Micronaut applications — @acceptance scenarios, @MicronautTest, HttpClient, BaseAcceptanceTest with TestPropertyProvider for Testcontainers and WireMock, *AT suffix, Failsafe. Requires the .feature file in context. This should trigger for requests such as Implement Micronaut acceptance tests from a Gherkin feature file; Set up BaseAcceptanceTest with Testcontainers and WireMock for Micronaut. Part of cursor-rules-java project
64
75%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/523-frameworks-micronaut-testing-acceptance-tests/SKILL.mdQuality
Discovery
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.
This is a strong, well-crafted skill description that clearly defines a narrow niche (Micronaut acceptance testing from Gherkin files) with specific technologies and conventions. It includes explicit 'Use when' guidance and example trigger phrases, making it easy for Claude to select appropriately. The description is dense with relevant trigger terms and concrete details without being padded with fluff.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: implementing acceptance tests from Gherkin .feature files, @MicronautTest, HttpClient, BaseAcceptanceTest with TestPropertyProvider, Testcontainers, WireMock, *AT suffix, Failsafe. Very concrete and detailed. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement acceptance tests from Gherkin files with specific technologies) and 'when' (opens with 'Use when...' and provides explicit trigger examples like 'This should trigger for requests such as...'). Both dimensions are well-covered. | 3 / 3 |
Trigger Term Quality | Includes many natural keywords a user would say: 'acceptance tests', 'Gherkin', '.feature file', 'Micronaut', 'Testcontainers', 'WireMock', 'BaseAcceptanceTest', 'Failsafe'. Also includes explicit example trigger phrases like 'Implement Micronaut acceptance tests from a Gherkin feature file'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche: Micronaut-specific acceptance testing with Gherkin, Testcontainers, WireMock, and specific conventions like *AT suffix. Very unlikely to conflict with other skills due to the narrow, well-defined scope. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill establishes clear preconditions, verification steps, and a reasonable workflow structure, but defers nearly all substantive implementation guidance to an external reference file without providing any inline code examples or concrete patterns. The body reads more like a routing document than an actionable skill. Adding at least one concrete code example (e.g., BaseAcceptanceTest skeleton or a sample Given/When/Then mapping) would significantly improve actionability.
Suggestions
Add a concrete, executable code example showing the BaseAcceptanceTest class skeleton with @MicronautTest, HttpClient injection, and TestPropertyProvider — this is the core pattern and should be visible in the skill body.
Include a brief example mapping a Gherkin Given/When/Then scenario to the corresponding test method structure with HttpClient exchange and AssertJ assertions.
Add an explicit feedback loop in the workflow: if `./mvnw clean verify` fails after step 3, specify how to diagnose and retry (e.g., check compilation errors, review test output, fix and re-run).
Trim the 'What is covered' bullet list — it largely duplicates information from the constraints and workflow sections and could be removed or condensed to save tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list is somewhat useful as a table of contents but borders on redundant given the workflow and constraints sections. The summary section explaining scope and coverage adds moderate overhead without adding much actionable value. | 2 / 3 |
Actionability | The skill provides concrete commands (./mvnw compile, ./mvnw clean verify) and names specific patterns (BaseAcceptanceTest, TestPropertyProvider, *AT suffix), but lacks any executable code examples. The actual implementation guidance is entirely deferred to the reference file, so the skill body itself gives incomplete guidance. | 2 / 3 |
Workflow Clarity | The four-step workflow is clearly sequenced and includes pre/post verification commands, which is good. However, the steps are quite generic (read reference, gather scope, apply changes, verify) and lack explicit validation checkpoints or error recovery loops between steps. The destructive/batch nature of code generation warrants more explicit feedback loops. | 2 / 3 |
Progressive Disclosure | The skill correctly references a single external file (references/523-frameworks-micronaut-testing-acceptance-tests.md) for detailed guidance, which is good one-level-deep disclosure. However, no bundle files were provided to verify the reference exists, and the skill body itself contains very little substantive content — almost everything is deferred, making the SKILL.md feel like a thin wrapper rather than a useful overview with key patterns inline. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
3b97275
- Reviewed
Table of Contents
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.