422-frameworks-quarkus-testing-integration-tests
Use when you need to write or improve integration tests for Quarkus — including @QuarkusTest, Dev Services for automatic container provisioning, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock for external HTTP stubs, @QuarkusIntegrationTest for black-box testing against packaged artifacts, REST Assured, data isolation strategies (@TestTransaction vs @BeforeEach cleanup), and Maven Surefire/Failsafe three-tier split (*Test, *IT, *AT). 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/422-frameworks-quarkus-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 an excellent skill description that clearly states its purpose upfront with 'Use when', provides comprehensive coverage of specific Quarkus testing technologies and patterns, and uses natural trigger terms that developers would actually search for. The description is highly distinctive and unlikely to conflict with other testing-related skills due to its Quarkus-specific focus.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: @QuarkusTest, Dev Services, Testcontainers, WireMock, @QuarkusIntegrationTest, REST Assured, data isolation strategies, and Maven Surefire/Failsafe configuration. | 3 / 3 |
Completeness | Explicitly answers both what (write/improve integration tests with specific technologies) and when ('Use when you need to write or improve integration tests for Quarkus') with clear trigger guidance at the start. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'integration tests', 'Quarkus', '@QuarkusTest', 'Testcontainers', 'WireMock', 'REST Assured', '@TestTransaction', plus specific file patterns like '*Test, *IT, *AT'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Quarkus-specific terminology (@QuarkusTest, @QuarkusIntegrationTest, Dev Services) that clearly separates it from generic Java testing or other framework testing 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.
This skill functions primarily as a table of contents pointing to a reference file, with good structure and clear navigation but lacking actionable content. The constraints section provides useful workflow guidance, but the complete absence of code examples or concrete patterns means Claude must always consult the reference file to do anything useful. The skill would benefit significantly from at least one executable example demonstrating a core pattern.
Suggestions
Add at least one concrete, executable code example showing a basic @QuarkusTest with REST Assured to demonstrate the core pattern without requiring reference file lookup
Include a minimal QuarkusTestResourceLifecycleManager example for Testcontainers or WireMock to make the skill immediately actionable
Condense the 'What is covered' bullet list into the 'When to use this skill' section to reduce redundancy and improve token efficiency
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes a verbose 'What is covered' section that largely duplicates information Claude could infer from the reference file. The bullet list of topics adds some value but could be more condensed. | 2 / 3 |
Actionability | The skill provides no concrete code examples, commands beyond basic Maven invocations, or executable guidance. It describes what topics are covered but delegates all actual implementation details to a reference file without showing any patterns. | 1 / 3 |
Workflow Clarity | The constraints section provides a clear sequence (compile → apply → verify) with explicit validation checkpoints, but lacks error recovery guidance beyond 'stop immediately' and 'resolved by the user.' The workflow is present but incomplete. | 2 / 3 |
Progressive Disclosure | The skill appropriately serves as an overview with a single, clearly signaled reference to detailed documentation. The structure is clean with well-organized sections and one-level-deep navigation to the reference file. | 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
b36efb2
- 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.