springboot-tdd

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

1.21x

Quality

85%

Does it follow best practices?

Impact

100%

1.21x

Average score across 6 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

83%Weight 40%Scale 1-5

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

A token-efficient, highly actionable Spring Boot TDD skill with broad executable coverage across test layers. The main gap is the absence of explicit validation/feedback-loop checkpoints in the workflow.

Suggestions

Add an explicit validate-and-retry loop to the workflow, e.g. '4) Run tests; if red, fix and re-run before proceeding'.

Show the JaCoCo coverage-check command and the failure behavior when coverage drops below 80%.

Dimension	Reasoning	Score
Conciseness	Lean body of short sections and executable snippets with no padding or explanation of concepts Claude already knows; nearly every token earns its place.	5 / 5
Actionability	Multiple copy-paste-ready Java/Maven snippets span unit, web, integration, and persistence tests plus builders and CI commands, covering the common cases.	5 / 5
Workflow Clarity	A clear numbered TDD sequence exists, but it lacks explicit validation checkpoints or a labeled fix-and-retry loop, leaving checkpoints implicit.	3 / 5
Progressive Disclosure	Well-organized into clear sections with no nested references and appropriate for a single-purpose skill, though sections like Testcontainers/JaCoCo could potentially be split out.	4 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

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, concise description that pairs a concrete tooling stack with an explicit use-when trigger clause. Minor room to broaden natural trigger-term coverage and enumerate more concrete actions.

Suggestions

Add a few more natural trigger phrases users say, e.g. 'Use when writing or running Spring Boot tests, adding endpoints, or enforcing coverage'.

Consider naming 1-2 more concrete actions (e.g. 'write failing tests, stub collaborators, enforce JaCoCo coverage') alongside the generic TDD phrasing.

Dimension	Reasoning	Score
Specificity	Names the domain and five concrete tools (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo), but the named actions ('Test-driven development', 'adding features, fixing bugs, refactoring') are fairly generic rather than multiple distinct concrete actions.	4 / 5
Completeness	Explicitly answers both what (TDD for Spring Boot using named tools) and when ('Use when adding features, fixing bugs, or refactoring') with a concrete trigger clause.	5 / 5
Trigger Term Quality	'Use when adding features, fixing bugs, or refactoring' provides natural phrases users would say, though the set is limited and misses synonyms like 'writing tests' or 'Spring Boot tests'.	4 / 5
Distinctiveness Conflict Risk	The Spring Boot + JUnit 5/Mockito/MockMvc/Testcontainers/JaCoCo framing carves a sharp niche with minimal overlap risk against other skills.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: affaan-m/ECC
Path: docs/ja-JP/skills/springboot-tdd/SKILL.md
Commit: e04ea0b

Reviewed: 2 days 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.