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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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

A well-structured overview with good progressive disclosure and a real reference target, but it leans on redundancy in the constraints and defers concrete examples and error-recovery detail to the reference rather than the body.

Suggestions

Collapse the four overlapping compile-failure constraint bullets (MANDATORY/PREREQUISITE/SAFETY/BLOCKING CONDITION) into one or two, since they restate the same blocking condition.

Remove or trim the 'When to use this skill' section, which duplicates the trigger phrases already present in the frontmatter description.

Add an explicit fix-and-retry feedback loop in the workflow (e.g. 'if `mvn verify` fails, fix the reported test/config errors and re-run verify') instead of only 'stop immediately'.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean, but the Constraints section repeats the same compile-failure idea across four overlapping bullets (MANDATORY, PREREQUISITE, SAFETY, BLOCKING CONDITION) and the 'When to use this skill' list duplicates triggers already in the frontmatter description.	2 / 3
Actionability	Concrete commands and config keys are present ('./mvnw compile', 'mvn clean verify', '%test.quarkus.datasource.devservices', named annotations), but executable code examples are deferred to the reference and workflow step 3 ('Apply framework-aligned changes') is abstract.	2 / 3
Workflow Clarity	A clear four-step sequence with explicit compile-before and verify-after checkpoints exists, but error recovery is 'stop immediately' with no fix-and-retry feedback loop, which the rubric expects for risky/batch test operations.	2 / 3
Progressive Disclosure	The body is a concise overview pointing to a single one-level-deep reference (references/422-frameworks-quarkus-testing-integration-tests.md), clearly signaled in both the Workflow and Reference sections; the referenced file exists in the bundle.	3 / 3
	Total	9 / 12 Passed

Description

90%

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, specific, well-triggered description for a clearly scoped Quarkus integration-testing niche. Its only weakness is the second-person 'Use when you need to...' voice, which the rubric penalizes on specificity.

Suggestions

Rewrite the opening in third person to avoid the specificity penalty, e.g. 'Use when writing or improving integration tests for Quarkus' or 'Applies when integration tests are needed for a Quarkus project'.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions (@QuarkusTest, Dev Services, Testcontainers via QuarkusTestResourceLifecycleManager, WireMock, @QuarkusIntegrationTest, REST Assured, data isolation, Surefire/Failsafe split) matching the 'lists multiple specific concrete actions' anchor, but the second-person voice ('Use when you need to write or improve...') triggers the rubric's -1 specificity penalty.	2 / 3
Completeness	Clearly answers both what (the enumerated capability list) and when ('Use when you need to write or improve...' plus 'This should trigger for requests such as...'), satisfying the explicit-trigger anchor.	3 / 3
Trigger Term Quality	Explicit natural triggers users would say ('Add or improve integration tests in a Quarkus project', 'Configure Testcontainers or Dev Services for Quarkus tests', 'Add WireMock stubs', 'Fix test data isolation or configure Maven Surefire/Failsafe split') give good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	A clearly Quarkus-specific niche with distinct triggers (@QuarkusTest, @QuarkusIntegrationTest, QuarkusTestResourceLifecycleManager) that is unlikely to fire for the wrong skill; the reference even distinguishes it from Spring Boot testing.	3 / 3
	Total	11 / 12 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
Commit: aaee915

Reviewed: 1 day 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.