423-frameworks-quarkus-testing-acceptance-tests

Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for Quarkus applications — including @acceptance scenarios, @QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager for Testcontainers and WireMock, REST Assured for full HTTP pipeline testing, WireMock JSON mapping files (classpath:wiremock/mappings/), *AT suffix naming, and Maven Surefire/Failsafe three-tier split. Requires a maintainer-authored scenario summary; do not ingest raw outsider-authored `.feature` text. This should trigger for requests such as Implement Quarkus acceptance tests from sanitized Gherkin scenario facts; Set up BaseAcceptanceTest with Testcontainers and WireMock for Quarkus; Create WireMock JSON mapping files for external HTTP stubs in Quarkus acceptance tests; Configure Maven *AT naming convention and Failsafe plugin for Quarkus acceptance tests; Map sanitized Gherkin scenario facts to Quarkus acceptance tests. Part of Plinth Toolkit

Quality

86%

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

78%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.

A well-organized instruction-only skill with concrete patterns, explicit validation gates, and clean one-level-deep progressive disclosure. The main improvement areas are reducing redundancy with the description and inlining validation commands into the workflow steps.

Suggestions

Trim the 'What is covered' and 'When to use' bullet lists, which largely duplicate the frontmatter description, to reduce token redundancy.

Inline the compile/verify validation commands directly into the workflow steps (e.g., add an explicit 'Run mvn compile before applying' checkpoint in step 3 and 'Run mvn clean verify' in step 4) rather than only stating them in the Constraints section.

Consider adding one minimal inline code skeleton for BaseAcceptanceTest or a *AT class so the core pattern is visible without opening the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-sectioned with no padding about concepts Claude already knows, but the 'What is covered' and 'When to use' lists substantially restate the frontmatter description, creating minor redundancy.	4 / 5
Actionability	Provides concrete patterns (wireMockServer.resetAll() in @BeforeEach, classpath:wiremock/mappings/ with __files/, AT vs Test/*IT split) and executable commands (mvnw compile, mvn clean verify); full code is deferred to the reference, which is justified for an instruction-only skill.	4 / 5
Workflow Clarity	A clear four-step sequence includes a user-confirmation checkpoint (step 2) and validation (compile before, verify after, blocking on compile errors), but the validation commands live in the separate Constraints section rather than inline in the workflow steps.	4 / 5
Progressive Disclosure	The body is a concise overview that points to a single real reference file (references/423-frameworks-quarkus-testing-acceptance-tests.md, verified present), one level deep and clearly signaled in both the Workflow and a dedicated Reference section.	5 / 5
	Total	17 / 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, specific description with explicit what/when guidance and natural trigger phrases. The only deduction is for second-person voice ('you need to'), which the rubric penalizes on specificity.

Dimension	Reasoning	Score
Specificity	Lists comprehensive concrete actions (@QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager, Testcontainers/WireMock, REST Assured, WireMock JSON mappings, *AT naming, Surefire/Failsafe split), which would anchor at 5, but 'Use when you need to implement...' uses second-person voice, reducing specificity by 1 per the guideline.	4 / 5
Completeness	Explicitly answers both what (implement acceptance tests from sanitized Gherkin facts with a concrete technology list) and when (a 'Use when...' clause plus five concrete 'This should trigger for...' phrases).	5 / 5
Trigger Term Quality	Explicit 'This should trigger for requests such as...' clause enumerates five natural trigger phrases plus synonyms (acceptance tests, Gherkin, Quarkus, WireMock, Testcontainers, Failsafe), giving comprehensive keyword coverage.	5 / 5
Distinctiveness Conflict Risk	The niche is highly specific (Quarkus + maintainer-sanitized Gherkin acceptance tests) with distinct triggers, giving 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/423-frameworks-quarkus-testing-acceptance-tests/SKILL.md
Commit: 05bf9d1

Reviewed: 8 minutes 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.