133-java-testing-acceptance-tests
Use when you need to implement acceptance tests from a Gherkin .feature file for framework-agnostic Java (no Spring Boot, Quarkus, Micronaut) — finding @acceptance scenarios, happy path with RestAssured, Testcontainers for DB/Kafka, WireMock for external REST. Requires .feature file in context. Part of the skills-for-java project
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/133-java-testing-acceptance-tests/SKILL.mdQuality
Discovery
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.
This is a strong, well-crafted skill description that clearly defines its scope, trigger conditions, and specific capabilities. It effectively distinguishes itself from similar Java testing skills by explicitly scoping to framework-agnostic Java and naming the exact tools used. The explicit 'Use when' clause and rich set of natural trigger terms make it highly effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: implementing acceptance tests from Gherkin .feature files, finding @acceptance scenarios, happy path with RestAssured, Testcontainers for DB/Kafka, WireMock for external REST. Very concrete and actionable. | 3 / 3 |
Completeness | Clearly answers both what (implement acceptance tests from Gherkin .feature files using RestAssured, Testcontainers, WireMock) and when ('Use when you need to implement acceptance tests from a Gherkin .feature file for framework-agnostic Java'). Has an explicit 'Use when' clause with clear trigger conditions. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would use: 'acceptance tests', 'Gherkin', '.feature file', '@acceptance', 'RestAssured', 'Testcontainers', 'WireMock', 'Java', 'DB/Kafka'. These are precisely the terms a developer would mention when needing this skill. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive: scoped to framework-agnostic Java (explicitly excludes Spring Boot, Quarkus, Micronaut), specifically for acceptance tests from Gherkin .feature files, with a specific tech stack (RestAssured, Testcontainers, WireMock). Very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has good structure and progressive disclosure, clearly pointing to a reference file for detailed content. However, it is critically lacking in actionability — there are zero code examples, no sample test class structure, and no concrete RestAssured/Testcontainers/WireMock snippets. The body reads more like a table of contents than an actionable skill, with all substantive guidance deferred to the reference file.
Suggestions
Add at least one concrete, executable code example showing a minimal acceptance test class with RestAssured + Testcontainers setup (BaseAcceptanceTest pattern) so Claude has immediate actionable guidance without needing to read the reference.
Include a brief but explicit numbered workflow: (1) Read .feature file → (2) Identify @acceptance scenarios → (3) Run mvn compile → (4) Create BaseAcceptanceTest → (5) Implement test per scenario → (6) Run mvn clean verify.
Remove the redundant 'What is covered' bullet list or merge it into the constraints/workflow — the current format restates the description without adding actionable value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list is somewhat verbose and partially redundant with the description and reference file. The constraints section repeats the precondition information already stated above. However, it's not egregiously padded — it stays reasonably focused. | 2 / 3 |
Actionability | There are no concrete code examples, no executable commands beyond generic 'mvn compile', no sample test structure, no RestAssured/WireMock/Testcontainers code snippets. Everything actionable is deferred to the reference file, leaving the skill body as abstract description rather than instruction. | 1 / 3 |
Workflow Clarity | There is a sequence implied (check preconditions → compile → apply changes → verify), and validation steps are mentioned (compile before, verify after, stop on failure). However, the workflow is scattered across bullet points rather than a clear numbered sequence, and the actual test implementation steps are entirely absent — delegated to the reference. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep reference to the detailed guidance file. The split between overview/constraints in SKILL.md and detailed examples in the reference file is appropriate and clearly navigable. | 3 / 3 |
Total | 8 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
9ec21dd
- 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.