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
77
71%
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 domain (Micronaut acceptance testing from Gherkin files) with specific technologies and conventions. It includes explicit 'Use when' guidance, concrete trigger examples, and enough technical detail to distinguish it from other testing or Micronaut skills. The description is dense but appropriately so for a highly specialized skill.
| 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 tooling) and 'when' (explicit 'Use when' clause at the start, plus 'This should trigger for requests such as...' with concrete examples). Both dimensions are well-covered. | 3 / 3 |
Trigger Term Quality | Includes highly specific natural keywords users would say: 'acceptance tests', 'Gherkin', '.feature file', 'Micronaut', 'Testcontainers', 'WireMock', 'BaseAcceptanceTest', 'Failsafe'. The explicit trigger examples ('Implement Micronaut acceptance tests from a Gherkin feature file') further strengthen coverage. | 3 / 3 |
Distinctiveness Conflict Risk | Extremely narrow niche: Micronaut-specific acceptance testing with Gherkin, Testcontainers, WireMock, and specific conventions like *AT suffix. This is highly unlikely to conflict with other skills due to the very specific technology stack and pattern combination. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has good structure and progressive disclosure, clearly pointing to a detailed reference file. However, it critically lacks actionable content — no code examples, no concrete patterns for BaseAcceptanceTest or test classes, and no specific Gherkin-to-test mapping examples. The workflow steps are too generic and read more like a project management checklist than technical guidance.
Suggestions
Add a concrete, executable code example of a BaseAcceptanceTest class showing @MicronautTest, TestPropertyProvider, HttpClient injection, and wireMock.resetAll() in @BeforeEach — this is the core value of the skill.
Include a specific example mapping a Gherkin scenario (Given/When/Then) to a concrete *AT test method with HttpClient exchange and AssertJ assertions.
Make workflow step 3 specific: show the exact files to create/modify (e.g., BaseAcceptanceTest.java, *AT.java, pom.xml Failsafe config) rather than the generic 'implement or refactor following reference patterns'.
Add an explicit feedback loop in the workflow: if `mvn clean verify` fails, specify how to diagnose (check compilation errors vs test failures) and retry.
| 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 reference file. The introductory sentence and 'Scope' line add little value. Overall mostly efficient but could be tightened. | 2 / 3 |
Actionability | There are no concrete code examples, no executable commands beyond generic mvnw invocations, and no specific patterns for BaseAcceptanceTest, HttpClient usage, or test class structure. All substantive guidance is deferred to the reference file, leaving the skill body vague and abstract. | 1 / 3 |
Workflow Clarity | The workflow has a clear 4-step sequence with compile-before and verify-after checkpoints, which is good. However, the steps are generic ('apply framework-aligned changes', 'gather scope') rather than specific to the acceptance test implementation process, and there's no explicit error recovery/feedback loop if verification fails. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with a single, well-signaled reference to the detailed file. Navigation is straightforward with one level of depth, and the content is appropriately split between overview and detailed reference. | 3 / 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
899d988
- 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.