spring-boot-3

Spring Boot 3 patterns for configuration, DI, and web services. Trigger: When building or refactoring Spring Boot 3 applications.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./community/spring-boot-3/SKILL.md

Quality

Content

75%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.

The body is an efficient, well-structured reference with executable Java examples and concrete anti-patterns. It lacks explicit sequencing across patterns and defines some helper types only by reference.

Suggestions

Remove the 'Quick Reference' table or fold it into 'Critical Patterns' to eliminate redundancy and recover tokens.

Define or stub the referenced helper types (OrderRepository, OrderCommand, OrderEntity) so the service/controller examples compile standalone.

Add a short ordering note in 'Critical Patterns' indicating how the patterns compose (e.g. configure properties, then wire services, then expose controllers).

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding about what Spring Boot is, but the 'Quick Reference' table largely restates the 'Critical Patterns' section, a minor redundancy that keeps it just below a 5.	4 / 5
Actionability	Three complete, idiomatic Java examples (typed config properties, service with constructor injection + @Transactional, REST controller with DTO records) plus concrete anti-patterns are mostly copy-paste ready; minor gaps are the undefined helper types (OrderRepository, OrderCommand, OrderEntity).	4 / 5
Workflow Clarity	This is a patterns/reference skill rather than a multi-step workflow, and the 'When to Use' triggers plus numbered patterns give clear, unambiguous guidance; it is not a 5 because there is no explicit ordering or sequencing of how to apply the patterns together.	4 / 5
Progressive Disclosure	No bundle files exist, but the body is well-organized under clear section headers (When to Use, Critical Patterns, Code Examples, Anti-Patterns, Quick Reference, Resources) with no nested references; it is a 4 rather than 5 because the skill exceeds 50 lines with substantial inline code that could plausibly live in reference files.	4 / 5
	Total	16 / 20 Passed

Description

73%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.

The description cleanly states both purpose and an explicit trigger for a well-scoped Spring Boot 3 niche. Its main weakness is a generic action verb ('patterns for') where concrete capabilities would sharpen specificity.

Suggestions

Replace the generic 'patterns for' framing with concrete actions, e.g. 'Configure beans, validate typed properties, and build REST controllers in Spring Boot 3.'

Broaden the trigger with natural synonyms users say, such as 'Spring Boot service', 'REST API', or 'Spring beans'.

Dimension	Reasoning	Score
Specificity	Names the domain ('Spring Boot 3') plus several concrete sub-areas ('configuration, DI, and web services'), but the action verb is generic ('patterns for') rather than a concrete capability, so it sits between the minimal-actions anchor (2) and the multi-action anchor (4).	3 / 5
Completeness	Both 'what' ('Spring Boot 3 patterns for configuration, DI, and web services') and an explicit 'when' ('Trigger: When building or refactoring Spring Boot 3 applications') are present; the trigger is clear but offers only one scenario rather than the varied trigger phrases of a 5.	4 / 5
Trigger Term Quality	'building or refactoring Spring Boot 3 applications' supplies natural phrases a user would actually say; coverage is good but missing common synonyms like 'Spring Boot service', 'REST API', or 'Spring beans', so it is not a 5.	4 / 5
Distinctiveness Conflict Risk	The 'Spring Boot 3' framing carves a clear, version-pinned niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	16 / 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: Gentleman-Programming/Gentleman-Skills
Path: community/spring-boot-3/SKILL.md
Commit: c8036a3

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.