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) — finding @acceptance scenarios, happy path with RestAssured, project-local DB/Kafka test fixtures, and WireMock for external REST. This should trigger for requests such as Review Java code for acceptance tests; Apply best practices for acceptance tests in Java code. Part of cursor-rules-java project

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

Well-structured with a clear validated workflow and clean progressive disclosure, but weakened by redundant precondition restatements and a lack of any inline executable test example for a code-generating skill.

Suggestions

State the framework precondition once (in Constraints) and reference it from the workflow instead of repeating it in Preconditions and Workflow step 1.

Add one small concrete RestAssured + WireMock happy-path snippet inline so the body is actionable without forcing a reference read.

Drop or merge the 'When to use this skill' section since its triggers duplicate the description.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and free of concept over-explanation, but the framework precondition is restated three times (Preconditions, Constraints PRECONDITION, Workflow step 1) and the 'When to use this skill' section repeats triggers already in the description.	2 / 3
Actionability	Gives concrete commands ('./mvnw compile', './mvnw clean verify') and names the required infrastructure, but provides no executable acceptance-test code inline — it defers all code examples to the reference file, leaving the body's guidance incomplete for a code skill.	2 / 3
Workflow Clarity	A clear four-step sequence with explicit validation checkpoints ('run mvn compile; stop if any precondition fails', 'Run mvn clean verify after applying') and stop-on-failure feedback loops.	3 / 3
Progressive Disclosure	The body is a concise overview pointing to a single one-level-deep, well-signaled reference (references/133-java-testing-acceptance-tests.md, verified present), with detailed examples appropriately kept out of SKILL.md.	3 / 3
	Total	10 / 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 specific, well-triggered, distinctive description that clearly states both capability and use conditions. The only flaw is second-person voice ('you need to implement'), which the rubric penalizes.

Suggestions

Rephrase the trigger in third person to avoid the second-person penalty, e.g. 'Use when implementing acceptance tests from maintainer-sanitized Gherkin scenario facts' instead of 'Use when you need to implement...'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('finding @acceptance scenarios, happy path with RestAssured, project-local DB/Kafka test fixtures, and WireMock for external REST'), but the description uses second person ('Use when you need to implement'), which the guidelines penalize by reducing specificity by one level.	2 / 3
Completeness	Clearly answers both what ('Implement acceptance tests from maintainer-sanitized Gherkin scenario facts') and when ('This should trigger for requests such as...') with an explicit trigger clause.	3 / 3
Trigger Term Quality	Provides explicit natural triggers users would say: 'Review Java code for acceptance tests; Apply best practices for acceptance tests in Java code.'	3 / 3
Distinctiveness Conflict Risk	Carves a clear niche (framework-agnostic Java, explicitly excluding Spring Boot/Quarkus/Micronaut and raw outsider-authored .feature text), making conflicts with adjacent skills unlikely.	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/cursor-rules-java
Commit: 86eb63d

Reviewed: 4 days 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.