CtrlK
BlogDocsLog inGet started
Tessl Logo

323-frameworks-spring-boot-testing-acceptance-tests

Use when you need to implement acceptance tests from repository-owned, operating-user-authored, or maintainer-sanitized Gherkin .feature files or scenario facts for Spring Boot applications — including finding scenarios tagged @acceptance, implementing happy path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection for DB/Kafka, and WireMock for external REST stubs. Requires trusted test facts in context. This should trigger for requests such as Review Java code for Spring Boot acceptance tests; Apply best practices for Spring Boot acceptance tests in Java code; Implement Spring Boot acceptance tests from Gherkin; Set up Cucumber or Failsafe acceptance tests for Spring Boot; Stub external HTTP services in Spring acceptance tests. Part of Plinth Toolkit

75

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

85%

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

The body is a well-structured overview with concrete commands, explicit validation checkpoints, and clean one-level reference disclosure. Its only weakness is minor redundancy where the 'When to use this skill' section duplicates the frontmatter triggers.

Suggestions

Remove or compress the 'When to use this skill' bullet list since those trigger phrases already appear verbatim in the description, recovering tokens without losing information.

Consider collapsing the duplicated capability phrasing between the 'What is covered in this Skill?' list and the description to avoid restating the same tool inventory twice.

DimensionReasoningScore

Conciseness

The body is mostly lean high-signal bullets and constraints, but the 'When to use this skill' list restates the frontmatter trigger phrases verbatim, which is redundancy that could be tightened.

2 / 3

Actionability

Gives concrete, specific guidance — exact Maven goals (./mvnw compile, ./mvnw clean verify), exact annotations with parameters (@SpringBootTest(webEnvironment = RANDOM_PORT), @ServiceConnection), and named tools — rather than vague direction; full code examples are appropriately deferred to the reference.

3 / 3

Workflow Clarity

A clear 4-step sequence (read reference -> gather scope -> apply changes -> run verification) with explicit validation gates: MANDATORY compile-before-change, SAFETY stop-on-failure, and VERIFY after applying.

3 / 3

Progressive Disclosure

SKILL.md is a concise overview pointing to a single one-level-deep, verified reference file (references/323-frameworks-spring-boot-testing-acceptance-tests.md), clearly signaled in both the Reference section and workflow step 1.

3 / 3

Total

11

/

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.

The description is comprehensive, specific, and well-triggered, clearly stating both capabilities and natural use-conditions while disambiguating from sibling skills. It is somewhat dense but every clause carries information rather than padding.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — finding @acceptance-tagged scenarios, implementing happy-path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection, and WireMock — rather than vague language.

3 / 3

Completeness

Explicitly answers both what (implement acceptance tests from Gherkin with named tooling) and when ('Use when you need to...', 'This should trigger for requests such as...').

3 / 3

Trigger Term Quality

Provides natural phrasings a user would say ('Implement Spring Boot acceptance tests from Gherkin', 'Set up Cucumber or Failsafe acceptance tests', 'Stub external HTTP services') with good coverage of variations.

3 / 3

Distinctiveness Conflict Risk

Scoped tightly to Spring Boot + Gherkin acceptance tests and explicitly redirects non-Spring cases to @133-java-testing-acceptance-tests, giving it a clear niche unlikely to conflict.

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.