springboot-tdd

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

Install with Tessl CLI

npx tessl i github:ysyecust/everything-claude-code --skill springboot-tdd

What are skills?

Quality

73%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/springboot-tdd/SKILL.md

SKILL.md

Review

Evals

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 has a solid structure with an explicit 'Use when' clause and names specific technologies, but lacks concrete action verbs describing what the skill actually does. The trigger conditions are too broad and could cause conflicts with general development skills. Adding specific testing actions and more natural language trigger terms would improve skill selection accuracy.

Suggestions

Add concrete actions like 'write unit tests', 'create integration tests with containers', 'mock service dependencies', 'generate coverage reports'

Narrow the 'Use when' clause to testing-specific triggers: 'Use when writing tests, checking coverage, mocking dependencies, or setting up test containers for Spring Boot applications'

Include natural language variations users might say: 'unit test', 'integration test', 'test coverage', 'TDD', 'mock'

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', 'mock dependencies', 'generate coverage reports', or 'run integration tests'.	2 / 3
Completeness	Clearly answers both what (TDD for Spring Boot with specific tools) and when ('Use when adding features, fixing bugs, or refactoring'), providing explicit trigger guidance for when Claude should select this skill.	3 / 3
Trigger Term Quality	Includes good technical keywords (JUnit 5, Mockito, MockMvc, Testcontainers, JaCoCo, Spring Boot) but misses common natural language terms users might say like 'unit test', 'integration test', 'test coverage', 'mock', or 'TDD'.	2 / 3
Distinctiveness Conflict Risk	The Spring Boot and specific testing tool stack provides some distinctiveness, but 'adding features, fixing bugs, or refactoring' are very broad triggers that could overlap with general coding skills or other language-specific testing skills.	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 TDD skill with excellent code examples covering the full Spring Boot testing stack. The content is appropriately concise and assumes Claude's competence. The main weakness is the lack of explicit validation checkpoints in the workflow and missing guidance for error recovery when tests fail or coverage goals aren't met.

Suggestions

Add explicit validation checkpoints to the workflow, e.g., 'Run tests after each implementation change: `mvn test -Dtest=ClassName`; if red, fix before proceeding'

Include a troubleshooting section or feedback loop for common TDD issues (flaky tests, coverage gaps, test isolation problems)

Consider extracting the JaCoCo configuration and Testcontainers setup to separate reference files to keep the main skill more focused on the TDD workflow

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient, providing only essential information without explaining concepts Claude already knows. Every section delivers actionable value without padding or unnecessary context.	3 / 3
Actionability	All code examples are complete and executable, from unit tests to integration tests to Maven configuration. The examples are copy-paste ready with realistic domain objects and proper annotations.	3 / 3
Workflow Clarity	The TDD workflow steps are listed but lack explicit validation checkpoints. There's no feedback loop for when tests fail unexpectedly or coverage thresholds aren't met, and no guidance on what to do if the red-green-refactor cycle encounters issues.	2 / 3
Progressive Disclosure	Content is well-organized with clear section headers, but everything is inline in one file. For a skill of this length (~120 lines), some content like the full JaCoCo configuration or test data builders could be referenced externally to keep the main skill focused.	2 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 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: 5 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.