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

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

The canonical home for this skill is jbvc/springboot-tdd

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 tight, executable reference that scores well on conciseness and actionability. The main gap is workflow clarity: the TDD steps read as a checklist without explicit validation/recovery checkpoints.

Suggestions

Add an explicit validation checkpoint to the TDD workflow (e.g., 'Confirm the new test fails for the right reason before implementing').

Note how to recover when a test stays green unexpectedly or when coverage drops below 80% (the fix -> re-run loop).

Signal where deeper material lives if the skill grows (e.g., a short 'See references/ for extended patterns' line) to keep the overview scannable.

Dimension	Reasoning	Score
Conciseness	Lean, code-first content that assumes Claude's competence with Java/Spring; every section earns its place with minimal narration.	5 / 5
Actionability	Copy-paste ready executable examples for each test layer plus concrete Maven/Gradle and JaCoCo snippets cover the common cases.	5 / 5
Workflow Clarity	The four TDD steps are sequenced but lack explicit validation checkpoints beyond 'they should fail'; sequence is present yet feedback loops are only implicit.	3 / 5
Progressive Disclosure	Well-organized single-file skill with clear section headers; no bundle files exist, and for this scope the inlined material is appropriately contained.	4 / 5
	Total	17 / 20 Passed

Description

83%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 focused, third-person description that clearly pairs a Spring Boot TDD capability set with explicit 'Use when' triggers. Minor gains are possible by adding synonym triggers and enumerating concrete test actions.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete tools (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo), though the action framing stays at 'Test-driven development' rather than enumerating distinct test actions.	4 / 5
Completeness	Explicitly states what it does (TDD with named tools) and when to use it (adding features, fixing bugs, refactoring), answering both what and when concretely.	5 / 5
Trigger Term Quality	'Use when adding features, fixing bugs, or refactoring' gives natural triggers users would say, but it lacks common synonyms and file/extension cues.	4 / 5
Distinctiveness Conflict Risk	The Spring Boot TDD niche with this tool stack is mostly distinct from generic skills, with only minor overlap risk against broader Java/TDD skills.	4 / 5
	Total	17 / 20 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: affaan-m/everything-claude-code
Path: skills/springboot-tdd/SKILL.md
Commit: 06c5e11

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.