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 *IT naming with Failsafe. 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/522-frameworks-micronaut-testing-integration-tests/SKILL.mdQuality
Discovery
85%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 with excellent specificity and completeness. It clearly identifies the Micronaut integration testing niche with concrete technologies and includes an explicit 'Use when' clause. The main weakness is trigger term quality - while technically accurate, it relies heavily on framework jargon that users may not naturally use when requesting help.
Suggestions
Add natural language trigger terms like 'test my Micronaut API', 'integration testing for microservices', or 'test endpoints with containers'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: '@MicronautTest, HttpClient, TestPropertyProvider with Testcontainers, transactional test mode, *IT naming with Failsafe'. These are precise, actionable capabilities. | 3 / 3 |
Completeness | Explicitly answers both what ('write or improve integration tests for Micronaut' with specific techniques) and when ('Use when you need to write or improve integration tests for Micronaut'). The 'Use when' clause is present and clear. | 3 / 3 |
Trigger Term Quality | Includes good technical terms like 'integration tests', 'Micronaut', 'Testcontainers', 'Failsafe', but these are framework-specific jargon. Missing natural user phrases like 'test my API', 'write tests for my service', or 'testing endpoints'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically Micronaut integration tests with named conventions (*IT, Failsafe). Unlikely to conflict with general Java testing or unit testing skills due to framework-specific terminology. | 3 / 3 |
Total | 11 / 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 excels at being concise and well-structured with appropriate progressive disclosure to a reference file. However, it critically lacks actionable content - there are no code examples showing TestPropertyProvider patterns, HttpClient assertions, or @MicronautTest configurations. The skill tells Claude what concepts matter but doesn't show how to implement them.
Suggestions
Add at least one complete, executable code example showing a @MicronautTest with TestPropertyProvider and a static @Container
Include a concrete HttpClient assertion example demonstrating full-stack HTTP testing
Add a numbered workflow with explicit validation steps for creating integration tests (e.g., 1. Create test class, 2. Add container, 3. Implement TestPropertyProvider, 4. Verify with mvn verify)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using bullet points to convey key concepts without explaining what Micronaut, Testcontainers, or integration tests are. Every line adds value for someone who already knows the domain. | 3 / 3 |
Actionability | The skill provides no executable code examples, no concrete commands beyond generic mvn invocations, and no specific test patterns. It describes what to do conceptually but doesn't show how with copy-paste ready examples. | 1 / 3 |
Workflow Clarity | The constraints section provides a clear compile-then-verify sequence, but lacks validation checkpoints or error recovery guidance. The workflow is implicit rather than explicit with numbered steps and feedback loops. | 2 / 3 |
Progressive Disclosure | The skill serves as a clear overview with a well-signaled one-level-deep reference to the detailed guidance file. Content is appropriately split between the overview and the reference document. | 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
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.