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). This should trigger for requests such as Add or improve integration tests in a Quarkus project; Configure Testcontainers or Dev Services for Quarkus tests; Add WireMock stubs for external HTTP dependencies in Quarkus integration tests; Set up @QuarkusIntegrationTest for packaged artifact or native binary testing; Fix test data isolation or configure Maven Surefire/Failsafe split. Part of Plinth Toolkit

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Well-organized overview with strong progressive disclosure and explicit build/validation checkpoints in the workflow. The body is lean but delegates essentially all executable test patterns to the reference, so its standalone actionability is moderate.

Suggestions

Inline 1-2 short, representative code examples (e.g., a minimal @QuarkusTest with REST Assured and a Testcontainers QuarkusTestResourceLifecycleManager snippet) so the body is actionable without forcing a reference read for the common case.

Remove or compress the 'When to use this skill' section, since its trigger phrases duplicate the frontmatter description.

Tighten the middle workflow steps ('Gather scope', 'Apply framework-aligned changes') with concrete sub-actions tied to the reference's patterns.

Dimension	Reasoning	Score
Conciseness	Lean body with no padding of concepts Claude already knows; organized as bullet overview, constraints, and a short workflow. Minor redundancy: the 'When to use this skill' section restates trigger phrases already present in the description, which could be trimmed.	4 / 5
Actionability	Names concrete annotations, config keys (%test.quarkus.datasource.devservices), and commands (./mvnw compile, mvn clean verify), but defers all executable test-code examples to the reference ('Read the reference for detailed rules and examples'), leaving the body itself without copy-paste patterns.	3 / 5
Workflow Clarity	A clear 4-step sequence (read reference -> gather scope -> apply -> verify) with explicit validation checkpoints (MANDATORY compile before, VERIFY clean verify after, SAFETY stop-on-failure, BLOCKING CONDITION). Not a 5 because the middle steps ('Gather scope', 'Apply framework-aligned changes') remain high-level.	4 / 5
Progressive Disclosure	Clean overview structured into well-labeled sections pointing to a single one-level-deep reference (references/422-frameworks-quarkus-testing-integration-tests.md, which exists), with clear navigation via both the Workflow and a dedicated Reference link.	5 / 5
	Total	16 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, comprehensive description with explicit what/when structure and natural trigger phrases scoped to a well-defined Quarkus niche. The only weakness is second-person voice ('you need'), which triggers the specificity penalty.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (@QuarkusTest, Dev Services, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock, @QuarkusIntegrationTest, REST Assured, data isolation, Maven Surefire/Failsafe split), which is comprehensive; penalized one point because the description uses second-person voice ('Use when you need to write or improve') instead of third person.	4 / 5
Completeness	Explicitly answers both 'what' (write/improve Quarkus integration tests with the enumerated techniques) and 'when' ('Use when...' plus 'This should trigger for requests such as...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrases users would actually say ('Add or improve integration tests in a Quarkus project', 'Configure Testcontainers or Dev Services', 'Add WireMock stubs', 'Fix test data isolation or configure Maven Surefire/Failsafe split'), covering synonyms and concrete variants.	5 / 5
Distinctiveness Conflict Risk	A clear niche (Quarkus integration testing) with distinct, specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/422-frameworks-quarkus-testing-integration-tests/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.