tessl-labs/springboot-testing
Spring Boot testing — @WebMvcTest for controllers, @DataJpaTest for repositories, @SpringBootTest only for integration, MockMvc, @MockBean vs @Mock, AssertJ, @Transactional rollback, @ActiveProfiles, TestContainers
93
89%
Does it follow best practices?
Impact
100%
1.09xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
82%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, technically detailed description that thoroughly covers Spring Boot testing capabilities with specific annotations, tools, and patterns. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others. The technical specificity is excellent but could benefit from explicit trigger guidance.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when writing tests for Spring Boot applications, setting up test slices, or configuring test databases'
Consider adding common user phrasings like 'unit testing Spring', 'testing REST controllers', or 'database testing in Spring'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: WebMvcTest, DataJpaTest, SpringBootTest, MockMvc, MockBean, slice test annotations, AssertJ assertions, Transactional rollback, Sql test data, TestContainers, and ActiveProfiles. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with comprehensive coverage of testing concepts, but lacks an explicit 'Use when...' clause or equivalent trigger guidance to indicate when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms developers would use: 'Spring Boot testing', 'WebMvcTest', 'DataJpaTest', 'MockMvc', 'MockBean', 'TestContainers', 'AssertJ', 'integration' - these are all terms users would naturally mention when seeking testing help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Spring Boot-specific testing terminology (WebMvcTest, DataJpaTest, TestContainers) that clearly differentiates it from generic testing or other framework skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that provides comprehensive, actionable Spring Boot testing guidance with excellent code examples and clear decision frameworks. The content respects Claude's intelligence by avoiding basic explanations while providing concrete, executable patterns. The main weakness is the document length—some sections like TestContainers and detailed examples could be extracted to separate files for better progressive disclosure.
Suggestions
Consider extracting TestContainers setup and SQL test data examples into separate reference files (e.g., TESTCONTAINERS.md, TEST-DATA.md) with links from the main skill
The verifiers section at the end references files that may not exist—ensure these paths are valid or remove the section
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing direct guidance without explaining basic concepts Claude already knows. Tables summarize choices quickly, and code examples are minimal but complete. | 3 / 3 |
Actionability | Every section provides fully executable, copy-paste ready code examples with proper imports and realistic test scenarios. The Maven dependencies, YAML configs, and SQL scripts are all complete and usable. | 3 / 3 |
Workflow Clarity | Clear decision tables guide test slice selection, explicit rules distinguish @MockBean vs @Mock usage, and the final checklist provides validation checkpoints. The progression from narrow slices to integration tests is well-sequenced. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a summary checklist, but the document is quite long (~300 lines) and could benefit from splitting detailed examples (TestContainers setup, SQL scripts) into separate reference files. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents