jbvc/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 its 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 its trigger conditions are too broad—'adding features, fixing bugs, or refactoring' could apply to almost any development skill, creating significant 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 with more specific triggers like 'Use when writing or updating tests for Spring Boot applications, setting up test infrastructure, improving test coverage, or when the user mentions JUnit, Mockito, MockMvc, or Testcontainers'.
Include natural user terms like 'unit test', 'integration test', 'test coverage', 'mock', 'test class' 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 mention, 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 + testing tools combination creates a reasonably distinct niche, but the 'Use when adding features, fixing bugs, or refactoring' triggers are extremely broad and would overlap with virtually any development-related skill. A general Spring Boot development skill or a code refactoring skill would easily conflict. | 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 workflow section, which lists the TDD cycle but lacks explicit validation checkpoints (e.g., verifying coverage thresholds, what to do on failure). The content could benefit from slightly better progressive disclosure by extracting detailed configs into referenced files.
Suggestions
Add explicit validation checkpoints to the workflow, e.g., 'Run `mvn verify` and check JaCoCo report meets 80% threshold before committing; if below, identify untested paths and add tests.'
Consider extracting the JaCoCo Maven/Gradle config and Testcontainers setup into separate referenced files (e.g., JACOCO.md, TESTCONTAINERS.md) to keep the main skill as a concise overview.
| 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 pattern notes (e.g., 'Arrange-Act-Assert', 'Avoid partial mocks') add value without over-explaining. | 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. CI commands, JaCoCo Maven config, and test data builder patterns are all concrete and specific. | 3 / 3 |
Workflow Clarity | The TDD workflow (write failing tests → implement → refactor → enforce coverage) is listed but lacks explicit validation checkpoints. There's no feedback loop for what to do when coverage falls below 80%, no 'verify before committing' step, and no explicit sequencing between the different test layers. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers, but it's a single monolithic file with substantial inline code. The Testcontainers section hints at a TestContainersConfig class without linking to a reference. Sections like JaCoCo config and test data builders could be split into referenced files for a cleaner overview. | 2 / 3 |
Total | 10 / 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.
Reviewed
Table of Contents