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. Part of the skills-for-java project
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 excels across all dimensions. It provides explicit trigger guidance with 'Use when', lists specific technologies and patterns, and carves out a clear niche for Micronaut acceptance testing with Gherkin. The technical specificity ensures it won't conflict with general testing skills while remaining discoverable through natural developer terminology.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: 'implement acceptance tests from Gherkin .feature file', '@MicronautTest', 'HttpClient', 'BaseAcceptanceTest with TestPropertyProvider', 'Testcontainers', 'WireMock', '*AT suffix', 'Failsafe'. Very detailed technical capabilities. | 3 / 3 |
Completeness | Explicitly answers both what ('implement acceptance tests from a Gherkin .feature file for Micronaut applications') and when ('Use when you need to implement acceptance tests from a Gherkin .feature file'). Includes explicit 'Use when' clause at the start. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'acceptance tests', 'Gherkin', '.feature file', 'Micronaut', '@acceptance scenarios', 'Testcontainers', 'WireMock'. These are terms developers would naturally use when requesting this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically Micronaut + Gherkin + acceptance testing combination. The specific technology stack (Testcontainers, WireMock, Failsafe, *AT suffix convention) makes it unlikely to conflict with generic testing or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates excellent structure, conciseness, and workflow clarity with proper validation checkpoints. The main weakness is the lack of concrete code examples in the skill body itself - all actionable implementation details are deferred to the reference file, which may require an extra lookup for common operations.
Suggestions
Add a minimal executable code example showing BaseAcceptanceTest setup or a simple Given/When/Then test method to make the skill immediately actionable
Include a brief HttpClient exchange example demonstrating the pattern for acceptance tests without requiring reference file lookup
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using bullet points and brief descriptions without explaining concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | The skill provides clear constraints and workflow steps (compile before, verify after), but lacks concrete code examples. All executable guidance is deferred to the reference file, leaving the main skill without copy-paste ready content. | 2 / 3 |
Workflow Clarity | Clear sequence with explicit validation checkpoints: precondition checks → compile before → apply changes → verify after. The feedback loop is well-defined with mandatory verification steps. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview and clear one-level-deep reference to the detailed guidance file. The 'What is covered' section provides good navigation of topics without bloating the main file. | 3 / 3 |
Total | 11 / 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
a886986
- 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.