133-java-testing-acceptance-tests

Use when you need to implement acceptance tests from maintainer-sanitized Gherkin scenario facts for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) — confirming @acceptance scenarios before coding, happy path with RestAssured, DB/Kafka test fixtures, WireMock for external REST only, and *AT classes run by Failsafe. This should trigger for requests such as Review Java code for acceptance tests; Apply best practices for acceptance tests in Java code; Implement acceptance tests from Gherkin scenarios in Java; Map feature files to Java step definitions; Review Cucumber acceptance tests for Java services. Part of Plinth Toolkit

Quality

85%

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.

A well-structured, actionable skill body with clear validation checkpoints and a clean single-reference progression. The main weakness is redundancy — preconditions restated four times and the "When to use" section duplicating the description's triggers — plus a lack of inline code examples.

Suggestions

Collapse the repeated "maintainer-sanitized Gherkin scenario facts must be in context" precondition into a single statement in the Constraints section and reference it elsewhere rather than restating it in What is covered, Preconditions, Scope, and Workflow step 1.

Remove or condense the "When to use this skill" section since its five bullets duplicate the trigger phrases already in the frontmatter description, freeing token budget.

Add one short inline RestAssured given/when/then snippet or a minimal *AT class skeleton so the body is copy-paste ready rather than relying entirely on the reference for code.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and does not explain concepts Claude already knows, but the precondition "maintainer-sanitized Gherkin scenario facts must be in context" is repeated across four sections and the "When to use this skill" list duplicates the description's trigger phrases verbatim, so it could be tightened.	3 / 5
Actionability	Names concrete tooling (RestAssured, WireMock, maven-failsafe-plugin) and exact commands ("./mvnw compile", "./mvnw clean verify") with the *AT naming convention, but provides no inline Java/code example — actual test code is deferred to the reference, leaving a minor gap.	4 / 5
Workflow Clarity	A clear four-step sequence with compile-before and verify-after checkpoints plus "stop if any precondition fails" and "stop immediately" on compilation failure; however it lacks an explicit fix-and-revalidate retry loop, so it sits just below the top anchor.	4 / 5
Progressive Disclosure	The body is a well-organized overview (What is covered, Preconditions, Scope, Constraints, Workflow) that points to a single one-level-deep reference, references/133-java-testing-acceptance-tests.md, which exists and is clearly linked — easy to navigate with no nesting.	5 / 5
	Total	16 / 20 Passed

Description

100%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 high-quality description: third-person voice, concrete actions, explicit trigger phrases, and tight framework scoping that distinguishes it from sibling skills. It answers both what and when unambiguously.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "implement acceptance tests from maintainer-sanitized Gherkin scenario facts", "confirming @acceptance scenarios before coding", "happy path with RestAssured, DB/Kafka test fixtures, WireMock for external REST only", "*AT classes run by Failsafe" — covering the domain comprehensively.	5 / 5
Completeness	Explicitly answers both what ("implement acceptance tests from maintainer-sanitized Gherkin scenario facts…") and when ("Use when you need to…" plus the "This should trigger for requests such as" list) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides an explicit "This should trigger for requests such as" clause with five natural phrases users would say ("Review Java code for acceptance tests", "Implement acceptance tests from Gherkin scenarios in Java", "Review Cucumber acceptance tests for Java services") plus synonyms like Cucumber, Gherkin, feature files, and step definitions.	5 / 5
Distinctiveness Conflict Risk	Sharply scoped to framework-agnostic Java with explicit exclusions ("no Spring Boot, Quarkus, Micronaut") and a distinct Gherkin/acceptance-test niche, minimizing overlap with framework-specific sibling skills.	5 / 5
	Total	20 / 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/133-java-testing-acceptance-tests/SKILL.md
Commit: 05bf9d1

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