322-frameworks-spring-boot-testing-integration-tests

Use when you need to write or improve integration tests — including Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate or MockMvcTester for HTTP, data isolation, and container lifecycle management for Spring Boot 4.0.x. This should trigger for requests such as Review Java code for Spring Boot integration tests; Apply best practices for Spring Boot integration tests in Java code; Write @SpringBootTest integration tests with Testcontainers; Configure dynamic properties for Spring integration tests; Review Spring Boot integration test profiles. Part of Plinth Toolkit

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/322-frameworks-spring-boot-testing-integration-tests/SKILL.md

Quality

Content

63%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 overview with strong progressive disclosure and explicit compile/verify validation checkpoints, but it lacks inline executable test examples and carries time-sensitive version info plus redundant trigger-phrase duplication.

Suggestions

Inline 1-2 minimal executable integration-test snippets (e.g. a @SpringBootTest + @ServiceConnection Testcontainers example) so the body is actionable without forcing a reference read.

Move the 'Spring Boot 4.0.x' version pin into a dedicated version/deprecation note so time-sensitive info does not penalize conciseness, and drop the duplicated 'When to use this skill' list since those triggers already live in the description.

Tighten the generic workflow steps ('Apply framework-aligned changes', 'Run verification and report results') into specific actions that reference the concrete techniques listed in the 'What is covered' section.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no padding of basic concepts, but the version number 'Spring Boot 4.0.x' appears twice outside any deprecated/old-patterns section (time-sensitive info penalizes conciseness) and the 'When to use this skill' list duplicates trigger phrases already in the description.	3 / 5
Actionability	Provides concrete commands (./mvnw compile, mvn clean verify) and names specific annotations, but offers no executable test code inline — the core writing guidance is deferred entirely to the reference file, leaving key details missing from the body.	3 / 5
Workflow Clarity	Four-step workflow is clearly sequenced with explicit validation checkpoints (MANDATORY compile before, SAFETY stop-on-failure, VERIFY after) and a feedback loop, but the workflow steps themselves remain somewhat generic ('Apply framework-aligned changes').	4 / 5
Progressive Disclosure	Body is a clean overview pointing to a single one-level-deep reference (references/322-frameworks-spring-boot-testing-integration-tests.md, verified to exist) that is signaled both in the Workflow and a dedicated Reference section; content is appropriately split.	5 / 5
	Total	15 / 20 Passed

Description

95%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 with explicit what/when structure and natural trigger phrases. The only weakness is second-person voice in the opening clause, which costs it the top specificity score.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities (Testcontainers with @ServiceConnection, @DataJdbcTest persistence slices, TestRestTemplate/MockMvcTester for HTTP, data isolation, container lifecycle) matching the 'several specific actions' anchor; capped at 4 because the opening 'Use when you need to' is second-person voice, which the guidelines penalize by one point.	4 / 5
Completeness	Explicitly answers both 'what' (write/improve integration tests with the listed techniques) and 'when' ('Use when you need to...' plus a concrete 'This should trigger for requests such as...' list), matching the top anchor.	5 / 5
Trigger Term Quality	Provides comprehensive natural trigger phrases users would actually say — 'Review Java code for Spring Boot integration tests', 'Write @SpringBootTest integration tests with Testcontainers', 'Configure dynamic properties for Spring integration tests' — with several synonym variations.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Spring Boot 4.0.x integration testing specifically) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 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/322-frameworks-spring-boot-testing-integration-tests/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours 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.