522-frameworks-micronaut-testing-integration-tests
Use when you need to write or improve integration tests for Micronaut — @MicronautTest, HttpClient, TestPropertyProvider with Testcontainers, transactional test mode where appropriate, and Maven Surefire/Failsafe splits for *Test, *Tests, *IT, and *AT. This should trigger for requests such as Add Micronaut integration tests with Testcontainers; Wire dynamic datasource or broker URLs for @MicronautTest. 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/522-frameworks-micronaut-testing-integration-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 its niche in Micronaut integration testing. It provides specific technologies, concrete trigger examples, and explicit 'Use when' guidance. The description is detailed without being verbose and would allow Claude to confidently select this skill from a large pool.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: @MicronautTest, HttpClient, TestPropertyProvider with Testcontainers, transactional test mode, Maven Surefire/Failsafe splits with specific naming patterns (*Test, *Tests, *IT, *AT). | 3 / 3 |
Completeness | Clearly answers both 'what' (write/improve integration tests for Micronaut with specific technologies and patterns) and 'when' (explicit 'Use when' clause at the start, plus 'This should trigger for requests such as...' with concrete examples). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'integration tests', 'Micronaut', '@MicronautTest', 'Testcontainers', 'HttpClient', 'dynamic datasource', 'broker URLs'. The example requests ('Add Micronaut integration tests with Testcontainers', 'Wire dynamic datasource or broker URLs') closely match real user phrasing. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — narrowly scoped to Micronaut integration testing with specific tools (Testcontainers, TestPropertyProvider, Maven Surefire/Failsafe). Unlikely to conflict with generic testing skills or other framework-specific skills. | 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, properly deferring detailed content to a reference file. However, it is critically lacking in actionability — there are zero code examples, no concrete patterns for any of the listed topics (TestPropertyProvider, HttpClient, @MicronautTest), and the constraints section is excessively repetitive. The skill reads more like a table of contents than an actionable guide.
Suggestions
Add at least one concrete, executable code example showing a minimal @MicronautTest with TestPropertyProvider and a static @Container — this is the core use case and should be immediately visible in the skill body.
Consolidate the 5 redundant compilation-check bullet points into a single clear constraint (e.g., 'MANDATORY: Run `./mvnw compile` before any changes. If it fails, stop immediately and resolve before proceeding.').
Add a brief concrete example of Maven Surefire/Failsafe plugin configuration showing the *Test/*IT naming convention splits, since this is listed as a key topic.
Include a minimal HttpClient assertion example to make the 'full-stack HTTP assertions' bullet point actionable rather than descriptive.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary verbosity, particularly the overly repetitive compilation constraints section (5 bullet points saying essentially the same thing: 'don't proceed if compilation fails'). The 'What is covered' section is reasonably concise but the constraints block is padded. | 2 / 3 |
Actionability | The skill provides no concrete code examples, no executable commands beyond generic `mvn compile`/`mvn clean verify`, and no specific patterns for TestPropertyProvider, HttpClient assertions, or Testcontainers setup. All actual guidance is deferred to the reference file, leaving the skill body as vague direction rather than actionable instruction. | 1 / 3 |
Workflow Clarity | The workflow has a clear 4-step sequence with a compilation prerequisite check and post-verification step, which is good. However, the steps are generic ('Apply framework-aligned changes', 'Gather scope') with no specific validation checkpoints or error recovery loops beyond 'stop if compilation fails'. The actual workflow details are 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 structure is clean with distinct sections (constraints, when to use, workflow, reference) and the reference link is explicit and clearly labeled. | 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.