tdg-personal/springboot-tdd
Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.
78
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
67%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description correctly identifies the technology stack and includes an explicit 'Use when' clause, which is good. However, it lacks concrete action verbs describing what the skill actually does (e.g., writing tests, generating mocks, configuring test containers), and the trigger conditions are too broad—'adding features, fixing bugs, or refactoring' applies to nearly all development skills, creating high conflict risk.
Suggestions
Add specific concrete actions like 'Writes unit and integration tests, generates mock configurations, sets up Testcontainers for database testing, and configures JaCoCo coverage reports'.
Narrow the 'Use when' clause to testing-specific triggers: 'Use when the user asks to write tests, add test coverage, set up integration tests, or follow TDD practices in a Spring Boot project'.
Include natural user terms like 'unit test', 'integration test', 'test coverage', 'mock', 'TDD' to improve trigger term matching.
| 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', 'generate mock configurations', 'set up integration tests with containers', or 'measure code coverage'. | 2 / 3 |
Completeness | Explicitly answers both 'what' (test-driven development for Spring Boot with specific tools) and 'when' ('Use when adding features, fixing bugs, or refactoring'). The 'Use when' clause is present and explicit, though the triggers are quite broad. | 3 / 3 |
Trigger Term Quality | Includes good technical keywords (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo, Spring Boot) that users familiar with the stack would use, but the trigger terms 'adding features, fixing bugs, or refactoring' are overly generic and would match nearly any development skill. Missing natural terms like 'unit test', 'integration test', 'test coverage', 'write tests'. | 2 / 3 |
Distinctiveness Conflict Risk | The Spring Boot + specific testing tools combination creates some distinctiveness, but the 'Use when adding features, fixing bugs, or refactoring' trigger is extremely broad and would conflict with virtually any development-related skill. A general Spring Boot development skill or a code refactoring skill would easily overlap. | 2 / 3 |
Total | 9 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent concrete examples covering all major Spring Boot testing layers. Its main weakness is the lack of explicit validation checkpoints and feedback loops in the TDD workflow—the four steps are listed but not elaborated with error recovery guidance. The content could benefit from splitting detailed configuration (JaCoCo, Testcontainers setup) into referenced files.
Suggestions
Add explicit validation checkpoints to the workflow, e.g., 'Run `mvn test` and confirm failures before implementing; after implementing, confirm all tests pass before refactoring; run `mvn verify` and check JaCoCo report meets 80% threshold before committing.'
Consider extracting JaCoCo configuration and Testcontainers setup into separate referenced files (e.g., JACOCO_SETUP.md, TESTCONTAINERS.md) to keep the main skill focused on the TDD workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what JUnit, Mockito, or Spring Boot are. Every section provides concrete code or terse guidance without padding. The brief patterns lists and one-liner tips respect Claude's intelligence. | 3 / 3 |
Actionability | Every major testing layer (unit, web, integration, persistence) has a fully executable, copy-paste-ready Java code example with proper annotations and assertions. The JaCoCo Maven snippet and CI commands are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | The TDD workflow (write failing tests → implement → refactor → enforce coverage) is listed but lacks explicit validation checkpoints or feedback loops. There's no guidance on what to do when tests fail unexpectedly, how to verify coverage thresholds are met before proceeding, or how to iterate on failures. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers, but it's a moderately long monolithic file (~120 lines of content). The Testcontainers section hints at a TestContainersConfig class without linking to a reference, and the JaCoCo config could be split out. No external references are provided for advanced topics. | 2 / 3 |
Total | 10 / 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