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. Part of the skills-for-java project
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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 skill description that clearly identifies its purpose (integration testing for Spring Boot 4.0.x), lists specific technologies and annotations, and begins with an explicit 'Use when' clause. The description is technically precise while using natural developer terminology, making it highly discoverable and unlikely to conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: 'Testcontainers with @ServiceConnection', '@DataJdbcTest persistence slices', 'TestRestTemplate or MockMvcTester for HTTP', 'data isolation', and 'container lifecycle management'. | 3 / 3 |
Completeness | Explicitly answers both what (write/improve integration tests with specific technologies) and when ('Use when you need to write or improve integration tests') with clear trigger guidance at the start. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'integration tests', 'Testcontainers', '@DataJdbcTest', 'TestRestTemplate', 'MockMvcTester', 'HTTP', 'Spring Boot 4.0.x'. These are terms developers naturally use when seeking testing help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific Spring Boot 4.0.x version targeting, named annotations (@ServiceConnection, @DataJdbcTest), and specific testing tools (Testcontainers, MockMvcTester). Unlikely to conflict with generic testing or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates strong structure and progressive disclosure, with a clear workflow for safe application of changes. The main weakness is the lack of inline executable examples - all concrete code patterns are deferred to the reference file, which reduces immediate actionability for common scenarios.
Suggestions
Add 1-2 minimal executable code examples inline (e.g., a basic Testcontainers + @ServiceConnection setup) to improve actionability without requiring reference file lookup
Include a quick 'before/after' pattern showing one common anti-pattern and its fix to make the skill immediately useful
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using bullet points to list covered topics without explaining what integration tests are or how Spring Boot works. Every line adds value without padding. | 3 / 3 |
Actionability | Provides clear constraints with specific commands (./mvnw compile, ./mvnw clean verify) but lacks executable code examples. The actual implementation details are deferred to the reference file rather than shown inline. | 2 / 3 |
Workflow Clarity | Clear workflow with explicit validation checkpoints: compile first, stop if fails, apply changes, verify after. The MANDATORY/SAFETY/VERIFY structure provides an unambiguous sequence with error handling. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview of covered topics, clear constraints section, and a single well-signaled reference to the detailed rules file. One level deep, easy to navigate. | 3 / 3 |
Total | 11 / 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.
7772a1b
Table of Contents
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.