springboot-tdd

Test-driven development for Spring Boot using JUnit 5, Mockito, MockMvc, Testcontainers, and JaCoCo. Use when adding features, fixing bugs, or refactoring.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, concise skill body packed with executable examples across every Spring Boot test layer. Its weaknesses are the absence of explicit validation/feedback checkpoints in the TDD workflow and a lack of progressive disclosure for a 150+ line skill.

Suggestions

Add explicit validation checkpoints to the Workflow loop, e.g. 'Run `mvn test`; if tests fail, return to step 2' and 'Check JaCoCo report against the 80% threshold; if below, add tests before proceeding'.

Move the full code examples (JaCoCo plugin XML, complete test classes) into reference files under ./references/ and link to them from SKILL.md so the main file stays a lean overview.

Add a one-line navigation section pointing to those reference files (e.g. 'See references/jacoco-setup.md for full coverage config') to support progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: short section intros followed by executable code, with no explanation of what JUnit/Mockito/Spring Boot are and no padded concept descriptions. Every example demonstrates a distinct test layer, so the length earns its place.	3 / 3
Actionability	Provides fully executable, copy-paste-ready Java test classes for each layer (Mockito, MockMvc, SpringBootTest, DataJpaTest), a complete JaCoCo Maven plugin XML, concrete CI commands, and a test-data builder class.	3 / 3
Workflow Clarity	The TDD workflow is a clear 4-step sequence (write failing tests, implement, refactor, enforce coverage), but it lacks explicit validation checkpoints or feedback loops (e.g. 'run tests; if failing, fix and re-run'), which the rubric caps at 2 for test/batch workflows.	2 / 3
Progressive Disclosure	Sections are well-organized, but the file is 150+ lines with multiple full test classes and a complete plugin XML all inline and no external reference files or navigation; the 'under 50 lines' exemption for a 3 does not apply, and content that could be split out is kept inline.	2 / 3
	Total	10 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that clearly states what the skill does and when to use it with an explicit trigger clause. The only gap is that it names the tool stack rather than enumerating multiple concrete testing actions.

Dimension	Reasoning	Score
Specificity	Names the Spring Boot TDD domain and a comprehensive tool stack (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo), but the only concrete action stated is 'Test-driven development' rather than multiple specific verbs, so it falls short of listing several distinct concrete actions.	2 / 3
Completeness	It explicitly answers both 'what' (TDD for Spring Boot with the listed stack) and 'when' via an explicit 'Use when adding features, fixing bugs, or refactoring' trigger clause.	3 / 3
Trigger Term Quality	'adding features, fixing bugs, or refactoring' plus the named frameworks (Spring Boot, JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo) are natural terms practitioners actually say, giving good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The distinct Spring Boot + specific testing-stack niche makes it unlikely to trigger for unrelated skills, though the somewhat generic 'when' triggers (adding features, fixing bugs, refactoring) create minor overlap risk with a general Spring Boot development skill.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: ysyecust/everything-claude-code
Commit: a9cbecb

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.