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
77
71%
Does it follow best practices?
Impact
Pending
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 communicates its specific purpose, includes abundant natural trigger terms, and explicitly states both what it does and when to use it. The description is highly distinctive due to its precise technology stack and naming conventions. The only minor note is that it's somewhat dense, but the information density is appropriate for disambiguation among many skills.
| 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 .feature files for Micronaut apps with specific patterns) and 'when' (explicit 'Use when' clause at the start specifying the trigger scenario, plus the requirement that the .feature file must be in context). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms a developer would use: 'acceptance tests', 'Gherkin', '.feature file', 'Micronaut', 'Testcontainers', 'WireMock', '@MicronautTest', 'HttpClient', 'Failsafe'. These are all terms a Java developer would naturally mention when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very specific niche: Micronaut acceptance tests from Gherkin files using a particular stack (Testcontainers, WireMock, BaseAcceptanceTest, *AT suffix). Unlikely to conflict with other testing or Java skills due to the precise combination of technologies and conventions. | 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.
This skill functions primarily as a thin pointer to a reference file, with constraints and preconditions listed but almost no actionable content in the body itself. While the progressive disclosure structure is good, the lack of any concrete code examples, specific patterns, or executable guidance in the main skill file means Claude would need to read the reference before being able to do anything useful. The 'What is covered' section adds little value beyond a table of contents.
Suggestions
Add at least one concrete, executable code example showing the BaseAcceptanceTest pattern (e.g., the class skeleton with @MicronautTest, HttpClient injection, and TestPropertyProvider) so the skill body is actionable on its own.
Replace the 'What is covered in this Skill?' bullet list with a minimal quick-start workflow showing numbered steps: check .feature file → compile → implement base class → implement *AT class → verify.
Include a small Given/When/Then → code mapping example showing how a Gherkin scenario translates to setup/HttpClient exchange/AssertJ assertions, rather than just describing the pattern abstractly.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered in this Skill?' section is somewhat redundant with the rest of the content and reads like a table of contents rather than actionable guidance. The bullet list restates things that could be inferred from the reference. However, it's not excessively verbose. | 2 / 3 |
Actionability | There is no executable code, no concrete examples, no specific commands beyond generic './mvnw compile' and './mvnw clean verify'. The actual implementation guidance is entirely deferred to the reference file. The skill body describes what to do abstractly rather than instructing concretely. | 1 / 3 |
Workflow Clarity | There is a sequence implied (precondition check → compile → apply changes → verify), and validation steps are mentioned (compile before, verify after). However, the steps are not clearly numbered or sequenced, and there's no feedback loop for handling failures. The actual multi-step workflow for implementing tests is entirely in the reference file. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep reference to the detailed guidance file. The split between overview/constraints in SKILL.md and detailed implementation in the reference file is appropriate and clearly navigable. | 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
1847adc
- 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.