springboot-tdd
tessl i github:ysyecust/everything-claude-code --skill springboot-tddTest-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.
Validation
81%| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 Passed | |
Implementation
80%This is a strong, actionable TDD skill with excellent code examples covering the full Spring Boot testing stack. The content is appropriately concise and assumes Claude's competence. Minor improvements could include explicit validation checkpoints in the workflow (e.g., what to do when coverage drops below 80%) and potentially splitting detailed configurations into referenced files.
Suggestions
Add explicit validation/feedback steps to the workflow section (e.g., 'If coverage < 80%: identify untested paths, add tests, re-run')
Consider extracting JaCoCo configuration and Testcontainers setup to separate reference files to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information without explaining concepts Claude already knows. Every section delivers actionable value without padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for every test type (unit, web layer, integration, persistence). Includes concrete Maven/Gradle commands and complete JaCoCo configuration. | 3 / 3 |
Workflow Clarity | The TDD workflow steps are listed clearly (write tests → implement → refactor → coverage), but lacks explicit validation checkpoints or feedback loops for when tests fail or coverage thresholds aren't met. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but everything is inline in one file. For a skill of this length (~120 lines), some content like the full JaCoCo config or test data builders could be referenced externally. | 2 / 3 |
Total | 10 / 12 Passed |
Activation
67%The description effectively communicates the testing technology stack and includes an explicit 'Use when' clause, which is good for completeness. However, it relies heavily on tool names rather than describing concrete actions, and the trigger conditions are too broad ('adding features, fixing bugs, or refactoring' applies to almost any development task). The description would benefit from more specific actions and narrower, more distinctive trigger terms.
Suggestions
Add concrete actions like 'write unit tests', 'create integration tests with containers', 'mock service dependencies', 'generate test coverage reports'
Include natural trigger terms users would say: 'unit test', 'integration test', 'test coverage', 'mocking', 'write tests for'
Narrow the 'Use when' clause to be more specific to testing scenarios, e.g., 'Use when writing or running tests, checking coverage, or setting up test infrastructure for Spring Boot applications'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Spring Boot testing) and lists specific tools (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo), but doesn't describe concrete actions like 'write unit tests', 'mock dependencies', 'generate coverage reports', or 'set up integration tests'. | 2 / 3 |
Completeness | Clearly answers both what (TDD for Spring Boot with specific tools) and when ('Use when adding features, fixing bugs, or refactoring'), providing explicit trigger guidance for when Claude should select this skill. | 3 / 3 |
Trigger Term Quality | Includes good technical keywords (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo, Spring Boot) that users might mention, but misses common natural terms like 'unit test', 'integration test', 'test coverage', 'mocking', or 'write tests'. | 2 / 3 |
Distinctiveness Conflict Risk | The Spring Boot and specific testing tool stack provides some distinctiveness, but 'adding features, fixing bugs, or refactoring' is very broad and could overlap with general coding skills or other language-specific development skills. | 2 / 3 |
Total | 9 / 12 Passed |
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.