CtrlK
BlogDocsLog inGet started
Tessl Logo

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

69

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

70%

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 clear navigation to a one-level-deep reference and a validation-backed workflow. The main weaknesses are repetition between the body and the description (and within the Constraints section) and the lack of in-body executable code, which lives in the reference instead.

Suggestions

Remove the 'When to use this skill' section or replace it with a pointer to the description, since it duplicates the same five trigger phrasings verbatim and adds no new information.

Consolidate the overlapping Constraints entries about scenario-facts and compilation (PRECONDITION, NO EXCEPTIONS, BLOCKING CONDITION, NO RAW THIRD-PARTY GHERKIN) into a single concise set to cut redundancy.

Add one small copy-paste-ready example inline (e.g. a minimal *AT class skeleton or a WireMock mapping JSON snippet) so the body is actionable without requiring the reference for the common case.

DimensionReasoningScore

Conciseness

The body is mostly efficient and assumes Claude's competence, but the 'When to use this skill' section duplicates the description's trigger list verbatim and the Constraints section restates the compile/scenario-facts preconditions several times (PRECONDITION, NO EXCEPTIONS, BLOCKING CONDITION, NO RAW THIRD-PARTY GHERKIN), so not every token earns its place.

2 / 3

Actionability

Concrete executable commands are present ('Run ./mvnw compile or mvn compile', './mvnw clean verify or mvn clean verify') along with specific classes and paths, but the actual acceptance-test code and WireMock mapping JSON are delegated to the reference rather than given copy-paste-ready in-body, leaving the core implementation guidance incomplete here.

2 / 3

Workflow Clarity

The four-step Workflow is clearly sequenced (read reference → gather scope → apply → verify) with explicit validation checkpoints and a feedback loop: 'compile before and verify after', 'BLOCKING CONDITION: Compilation errors must be resolved by the user before proceeding', and 'VERIFY: Run ./mvnw clean verify'.

3 / 3

Progressive Disclosure

The body is an overview that points to a single one-level-deep reference (references/423-frameworks-quarkus-testing-acceptance-tests.md, verified to exist and to contain no further nested references), clearly signaled via 'BEFORE APPLYING: Read the reference' and a Reference link section, with detail appropriately split into the bundle.

3 / 3

Total

10

/

12

Passed

Description

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.

A strong, specific, and complete description that names concrete actions, supplies explicit trigger phrasings, and occupies a distinct niche. Its only weakness is verbosity: the trigger list and capability list are long and somewhat repetitive, though no dimension drops below 3.

DimensionReasoningScore

Specificity

Lists multiple concrete actions and stack specifics: '@QuarkusTest, BaseAcceptanceTest with QuarkusTestResourceLifecycleManager for Testcontainers and WireMock, REST Assured ... WireMock JSON mapping files (classpath:wiremock/mappings/), *AT suffix naming, and Maven Surefire/Failsafe three-tier split', matching the anchor for listing multiple specific concrete actions.

3 / 3

Completeness

It opens with an explicit 'Use when you need to implement acceptance tests...' clause (the when) and follows with 'This should trigger for requests such as...' triggers, while the body of the sentence states exactly what the skill does, answering both what and when explicitly.

3 / 3

Trigger Term Quality

Natural request-style triggers are given verbatim ('Implement Quarkus acceptance tests from sanitized Gherkin scenario facts', 'Set up BaseAcceptanceTest with Testcontainers and WireMock for Quarkus', 'Configure Maven *AT naming convention and Failsafe plugin'), which are phrasings a user would actually say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

The Quarkus + @QuarkusTest + BaseAcceptanceTest + *AT suffix + Surefire/Failsafe three-tier split niche is highly specific and unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/plinth
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.