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

—

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.

A well-structured overview with strong workflow validation and clean progressive disclosure, but it loses points on actionability (core test code deferred to the reference) and mild redundancy with the description. The Constraints section is its strongest part.

Suggestions

Remove or condense the 'When to use this skill' section, since its five trigger phrases duplicate the description's trigger list and add token cost without new information.

Add a minimal concrete example in the body (e.g., a @SpringBootTest + @ServiceConnection Testcontainers skeleton) so the skill is actionable without forcing a reference read for the most common case.

Trim overlap between the 'What is covered in this Skill?' list and the description's capability enumeration to keep the overview distinct from the frontmatter.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and avoids explaining concepts Claude already knows, but the 'When to use this skill' section restates the five trigger phrases already present in the description, and the 'What is covered' list overlaps it, so it could be tightened.	2 / 3
Actionability	It gives concrete executable commands ('mvn compile', 'mvn clean verify') and specific edge-case handling, but the actual test patterns and code are deferred to the reference and the workflow steps are abstract ('Apply framework-aligned changes'), so it is not copy-paste ready.	2 / 3
Workflow Clarity	It provides a clear numbered sequence with explicit validation checkpoints (compile before changes, stop on failure, verify after) and feedback loops for ambiguous scope or missing inputs, matching the anchor-3 example.	3 / 3
Progressive Disclosure	The body is a clear overview that points to a single real, well-signaled, one-level-deep reference (references/322-frameworks-spring-boot-testing-integration-tests.md), with content appropriately split and no nested references.	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 strong, specific description with explicit triggers and a clear niche; its only weakness is second-person phrasing ('you need') where third-person voice is preferred. It is dense and informative rather than padded.

Dimension	Reasoning	Score
Specificity	It lists multiple concrete actions and tools ('Testcontainers with @ServiceConnection', '@DataJdbcTest persistence slices', 'TestRestTemplate or MockMvcTester'), which meets the anchor-3 bar, but the rubric penalizes second-person voice by one point and 'Use when you need to write or improve integration tests' uses 'you', reducing it to 2.	2 / 3
Completeness	It clearly answers both what (the enumerated integration-test capabilities) and when, with an explicit 'Use when' clause and a 'This should trigger for requests such as' list, so it is not capped at 2.	3 / 3
Trigger Term Quality	It provides good coverage of natural request phrasings a user would say ('Review Java code for Spring Boot integration tests', 'Write @SpringBootTest integration tests with Testcontainers'), matching the anchor-3 example.	3 / 3
Distinctiveness Conflict Risk	It occupies a clear niche (Spring Boot 4.0.x integration testing) with distinct triggers that are unlikely to fire for unrelated skills.	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/plinth
Commit: aaee915

Reviewed: 1 day 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.