CtrlK
BlogDocsLog inGet started
Tessl Logo

spring-boot-skill

Build Spring Boot 4.x applications following the best practices. Use this skill: * When developing Spring Boot applications using Spring MVC, Spring Data JPA, Spring Modulith, Spring Security * To create recommended Spring Boot package structure * To implement REST APIs, entities/repositories, service layer, modular monoliths * To use Thymeleaf view templates for building web applications * To write tests for REST APIs and Web applications * To write ArchUnit tests for testing architecture * To configure the recommended plugins and configurations to improve code quality, and testing while using Maven. * To use Spring Boot's Docker Compose support for local development * To create Taskfile for easier execution of common tasks while working with a Spring Boot application

66

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/spring-boot/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 well-architected progressive-disclosure index: the body stays lean and routes each concern to a dedicated, real reference file, with the Testing section adding genuine decision guidance. Weaker on in-body actionability and sequenced workflow, since most executable detail lives in the references rather than SKILL.md.

Suggestions

For the highest-traffic concerns (e.g., Maven config, package structure), include a 1-2 line inline gist or a minimal code/command snippet so the body is actionable without always opening the reference.

Add a short 'Start here' ordering note (e.g., configure pom.xml → lay out packages → implement layers → test) so readers get an explicit workflow sequence across the area sections.

Tighten the repeated 'Read [references/X.md](references/X.md) for ...' pattern and the opening sentence, which partly duplicates the per-section pointers, to recover a few tokens.

DimensionReasoningScore

Conciseness

Lean body that assumes Claude's competence — no explanation of what Spring Boot or its libraries are — with the only mild redundancy being the repeated 'Read [references/...]' formula and an opening sentence that partially restates the section pointers.

4 / 5

Actionability

The Testing section gives concrete, actionable routing (specific annotations like @WebMvcTest/@JsonTest/@RestClientTest, 'never in-memory H2', @ServiceConnection vs dynamic-property), but most other sections are one-line 'see reference' pointers rather than executable guidance in the body itself.

3 / 5

Workflow Clarity

Areas are organized as a clear index and the Testing section offers a well-structured decision matrix (what → level → reference), but the skill is area-based rather than a sequenced multi-step process, so explicit sequencing and checkpoints are largely absent.

3 / 5

Progressive Disclosure

Exemplary overview-to-reference structure: a concise SKILL.md points via clear markdown links to 18 verified one-level-deep reference files, each organized under a topical section, making navigation easy and keeping detail out of the index.

5 / 5

Total

15

/

20

Passed

Description

92%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, third-person description that clearly states what the skill does and when to use it, with a comprehensive action list and explicit trigger guidance. Only minor: trigger-term synonyms could be broadened slightly.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — implement REST APIs, entities/repositories, service layer, modular monoliths, Thymeleaf templates, ArchUnit tests, Maven plugins, Docker Compose, Taskfile — giving comprehensive coverage of the Spring Boot 4.x domain.

5 / 5

Completeness

Explicitly answers both 'what' ('Build Spring Boot 4.x applications following the best practices') and 'when' via a multi-bullet 'Use this skill: When developing...' trigger list with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural keyword coverage (Spring Boot, Spring MVC, Spring Data JPA, REST APIs, Thymeleaf, Maven, Docker Compose, Taskfile) that developers would actually say, but missing a few common synonyms like 'Java' or 'web app'.

4 / 5

Distinctiveness Conflict Risk

The specific Spring Boot 4.x niche with its named framework stack (Spring MVC, Spring Data JPA, Spring Modulith, Spring Security) forms a clear, distinct trigger set with minimal overlap risk.

5 / 5

Total

19

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
sivaprasadreddy/sivalabs-agent-skills
Reviewed

Table of Contents

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.