CtrlK
BlogDocsLog inGet started
Tessl Logo

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

Use when you need to implement acceptance tests from maintainer-authored or maintainer-sanitized Gherkin scenario facts for Spring Boot applications — including selecting scenarios tagged @acceptance, implementing happy path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection for DB/Kafka, and WireMock for external REST stubs. Never ingest raw .feature files. 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 sanitized Gherkin facts; Set up Failsafe acceptance tests for Spring Boot; Stub external HTTP services in Spring acceptance tests. Part of Plinth Toolkit

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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.

Well-structured content with explicit compile/verify validation gates and clean one-level-deep progressive disclosure to a real reference file. The main weakness is minor redundancy of the no-raw-Gherkin rule and the absence of any inline code example.

Suggestions

Consolidate the no-raw-Gherkin rule so it is stated once authoritatively in Constraints rather than repeated across the intro, Preconditions, and constraints sections.

Add one short inline happy-path test skeleton (e.g. a @SpringBootTest + TestRestTemplate + @ServiceConnection snippet) so the body is copy-paste actionable without opening the reference.

Trim the 'When to use this skill' trigger list since it duplicates the trigger phrases already in the frontmatter description.

DimensionReasoningScore

Conciseness

Largely lean and assumes Claude's competence about Spring Boot, but the no-raw-Gherkin rule is restated three times (intro, Preconditions, NO RAW GHERKIN constraint) and the 'When to use' list overlaps the description's triggers.

4 / 5

Actionability

Gives concrete, executable commands ('./mvnw compile', 'mvn clean verify') and names specific annotations (@SpringBootTest(webEnvironment = RANDOM_PORT), @ServiceConnection, @DynamicPropertySource), but defers all inline code examples to the reference rather than showing copy-paste snippets.

4 / 5

Workflow Clarity

A clear four-step workflow with explicit validation gates — MANDATORY compile-before-apply, SAFETY stop-on-compilation-failure, and a post-change VERIFY step — forming a compile→stop→apply→verify feedback loop.

5 / 5

Progressive Disclosure

The body is a well-sectioned overview (What is covered, Preconditions, Scope, Constraints, When to use, Workflow, Reference) that signals one real, one-level-deep reference file in three places with a markdown link, confirmed to exist in references/.

5 / 5

Total

18

/

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 strong, specific description that names concrete tools and actions, gives explicit trigger phrases, and cleanly delineates its Spring Boot niche. It uses third person throughout and avoids fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'selecting scenarios tagged @acceptance', 'implementing happy path tests with TestRestTemplate, @SpringBootTest, Testcontainers with @ServiceConnection for DB/Kafka, and WireMock' — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

Explicitly answers both 'what' (implement acceptance tests from sanitized Gherkin facts with named tools) and 'when' (an explicit 'Use when...' clause plus a concrete trigger-phrase list).

5 / 5

Trigger Term Quality

Provides several natural trigger phrases users would say, e.g. 'Review Java code for Spring Boot acceptance tests', 'Set up Failsafe acceptance tests for Spring Boot', and 'Stub external HTTP services in Spring acceptance tests'.

5 / 5

Distinctiveness Conflict Risk

Strongly Spring Boot-scoped throughout and explicitly redirects framework-agnostic Java cases to @133-java-testing-acceptance-tests, giving it a clear niche with minimal conflict risk.

5 / 5

Total

20

/

20

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.