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. Part of the skills-for-java project
83
78%
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/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 identifies its niche (Micronaut integration testing), lists specific technologies and patterns, and opens with an explicit 'Use when' trigger clause. The description is concise yet comprehensive, covering the testing framework, tools, and build configuration aspects. The only minor note is the trailing 'Part of the skills-for-java project' which adds context but doesn't contribute to skill selection.
| 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 conventions (*Test, *Tests, *IT, *AT). | 3 / 3 |
Completeness | Explicitly answers both 'what' (write or improve integration tests for Micronaut with specific tools and patterns) and 'when' (opens with 'Use when you need to write or improve integration tests for Micronaut'), providing clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes highly relevant natural keywords a user would say: 'integration tests', 'Micronaut', '@MicronautTest', 'HttpClient', 'Testcontainers', 'Maven Surefire', 'Failsafe', and specific test file patterns. These are terms developers naturally use when discussing Micronaut testing. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets Micronaut-specific testing with named annotations, libraries, and Maven plugin configurations. Unlikely to conflict with generic Java testing skills or other framework-specific testing skills due to the Micronaut-specific terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%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 appropriate progressive disclosure by delegating details to a reference file. However, it is weakened by redundant safety constraints (five bullets saying the same thing) and a complete lack of concrete code examples in the body itself — all actionable content is deferred. The workflow would benefit from being presented as a clear numbered sequence rather than scattered constraint bullets.
Suggestions
Consolidate the five compilation-safety bullets into a single clear constraint (e.g., 'MANDATORY: Run `./mvnw compile` before any changes. If it fails, stop immediately. Run `./mvnw clean verify` after applying improvements.').
Add at least one concrete, executable code example in the body — e.g., a minimal @MicronautTest with TestPropertyProvider and a static @Container — so the skill is actionable without requiring the reference file.
Restructure the workflow as a numbered sequence: 1. Compile → 2. Read reference → 3. Apply changes → 4. Run verify → 5. If failures, fix and re-verify.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The constraints section is excessively repetitive — five bullet points all say 'compilation must pass before proceeding' in slightly different ways. The 'What is covered' section is reasonably concise but the safety constraints could be condensed to 2 bullets without losing meaning. | 2 / 3 |
Actionability | Provides concrete commands (`./mvnw compile`, `mvn clean verify`) but lacks any executable code examples for the actual testing patterns (TestPropertyProvider, HttpClient, @MicronautTest). All substantive guidance is deferred to the reference file, leaving the skill body without copy-paste-ready examples. | 2 / 3 |
Workflow Clarity | There is a clear compile-first → apply changes → verify sequence, but it's buried in repetitive constraint bullets rather than presented as a numbered workflow. No explicit validation checkpoints or feedback loops for the test-writing process itself (e.g., run tests, check failures, iterate). | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview of what's covered and appropriately delegates detailed rules and examples to a single reference file with a well-signaled link. This is a clean one-level-deep reference structure. | 3 / 3 |
Total | 9 / 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.