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
59
67%
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 skill description that clearly defines its niche in Micronaut integration testing. It opens with an explicit 'Use when' clause, lists specific technologies and patterns, and provides concrete example trigger requests. The description is well-targeted and distinctive, making it easy for Claude to select appropriately from a large skill set.
| 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' (opens with 'Use when' and provides explicit trigger examples like 'Add Micronaut integration tests with Testcontainers'). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'integration tests', 'Micronaut', '@MicronautTest', 'Testcontainers', 'HttpClient', 'datasource', 'broker URLs', and explicit example requests like 'Add Micronaut integration tests with Testcontainers' and 'Wire dynamic datasource or broker URLs'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — narrowly scoped to Micronaut integration testing specifically, with unique triggers like @MicronautTest, TestPropertyProvider, Testcontainers, and Maven Surefire/Failsafe splits. Unlikely to conflict with generic testing or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a table of contents pointing to a reference file, with an overly repetitive constraints section and no concrete code examples. While the workflow structure and safety checks show good intent, the complete absence of actionable code snippets (e.g., a TestPropertyProvider example, an HttpClient test pattern, or a Maven plugin configuration) means Claude would need to read the reference file to do anything useful. The five-bullet compilation check is redundant and wastes tokens.
Suggestions
Add at least 2-3 concrete, executable code examples inline — e.g., a minimal @MicronautTest with TestPropertyProvider and static @Container, an HttpClient assertion, and a Maven Surefire/Failsafe plugin configuration snippet.
Consolidate the five compilation-check bullets into a single clear constraint: 'MANDATORY: Run `./mvnw compile` before any changes. If it fails, stop immediately and do not proceed.'
Include a concrete good/bad example pair showing the difference between a poorly-wired integration test and a properly-configured one with TestPropertyProvider.
Add specific workflow details in steps 2-3, such as which files to inspect, what patterns to look for, and what the expected test class structure should look like.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' section is reasonably efficient, but the Constraints section is extremely verbose and repetitive — five bullet points all saying 'don't proceed if compilation fails' in slightly different ways. The introductory line is lean, but overall there's significant redundancy. | 2 / 3 |
Actionability | The skill contains no executable code examples, no concrete test patterns, no copy-paste ready snippets. Everything actionable is deferred to the reference file. The body describes what to do abstractly ('Apply framework-aligned changes') without showing how. | 1 / 3 |
Workflow Clarity | The four workflow steps provide a reasonable sequence with compilation pre-checks and post-verification, but the steps themselves are generic ('Gather scope', 'Apply framework-aligned changes') rather than specific. The validation checkpoint (compile before, verify after) is present but the actual testing workflow lacks detail. | 2 / 3 |
Progressive Disclosure | There is a clear reference to a single detailed file, which is good structure. However, since no bundle files were provided, we can't verify the reference exists. The SKILL.md itself is essentially a thin wrapper that delegates almost everything to the reference — it provides too little inline content to be useful on its own, making the disclosure feel hollow rather than progressive. | 2 / 3 |
Total | 7 / 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.