301-frameworks-spring-boot-core

Use when you need to review, improve, or build Spring Boot 4.0.x applications — including proper usage of @SpringBootApplication, component annotations (@Controller, @Service, @Repository), bean definition and scoping, configuration classes and @ConfigurationProperties (with @Validated), component scanning, conditional configuration and profiles, constructor injection, @Primary and @Qualifier for multiple beans of the same type, bean minimization, graceful shutdown, virtual threads, Jakarta EE namespace consistency, and scheduled tasks. This should trigger for requests such as Review Java code for Spring Boot application; Apply best practices for Spring Boot application in Java code; Improve Spring Boot configuration properties and beans; Review Spring Boot component scanning and profiles; Tune Spring Boot graceful shutdown or virtual threads. Part of Plinth Toolkit

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

Well-structured and lean with strong validation checkpoints and clean progressive disclosure to one reference file; the main gap is actionability, since the actual Spring Boot refactoring guidance lives entirely in the reference with only abstract pointers inline.

Suggestions

Add one or two short inline good/bad Spring Boot code snippets (e.g. constructor injection with @Qualifier, or @ConfigurationProperties with @Validated) so the most common patterns are actionable without opening the reference.

Make workflow step 4 as concrete as the Constraints section by naming the exact command ("Run ./mvnw clean verify") rather than "Execute appropriate build/tests".

The "When to use this skill" section duplicates the description's triggers; consider replacing it with a brief pointer to avoid redundant tokens.

Dimension	Reasoning	Score
Conciseness	The body is a lean overview: a topic list, constraints, when-to-use, and a short workflow, with no padding explaining what Spring Boot or basic concepts are; detail is delegated to a 49KB reference so nearly every token earns its place.	3 / 3
Actionability	Concrete build commands ("./mvnw compile", "mvn clean verify") are executable, but the core refactoring guidance is abstract and delegated ("Implement or refactor configuration/code following the reference patterns and project conventions") with no inline good/bad Spring Boot code examples.	2 / 3
Workflow Clarity	A clear 4-step sequence pairs with an explicit validation feedback loop: compile before changes, stop immediately on compile failure, then verify after applying — matching the rubric's checkpoint-with-error-recovery anchor.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview that points to a single, clearly-signaled, one-level-deep reference (references/301-frameworks-spring-boot-core.md, verified to exist), with no nested reference chains.	3 / 3
	Total	11 / 12 Passed

Description

92%

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, comprehensive description with explicit triggers and a clear what/when structure; its only weakness is that the two most prominent triggers are generic across all Spring Boot skills rather than scoped to the Core niche.

Suggestions

Tighten the leading triggers to scope them to core concerns, e.g. "Review Java code for Spring Boot core configuration and beans" instead of the generic "Review Java code for Spring Boot application", to reduce overlap with sibling Plinth skills.

The long inline topic enumeration inflates the description; consider trimming to the highest-signal capabilities and relying on the body's coverage list for the rest.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("review, improve, or build") alongside an extensive enumeration of specific capabilities (@SpringBootApplication, bean definition and scoping, @ConfigurationProperties with @Validated, @Primary/@Qualifier, graceful shutdown, virtual threads).	3 / 3
Completeness	Explicitly answers both what (the enumerated Spring Boot capabilities) and when via "Use when you need to..." plus "This should trigger for requests such as...", satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would actually say ("Review Java code for Spring Boot application", "Improve Spring Boot configuration properties and beans", "Tune Spring Boot graceful shutdown or virtual threads") with good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	Core-specific triggers (component scanning, profiles, virtual threads) are distinct, but the leading triggers "Review Java code for Spring Boot application" and "Apply best practices for Spring Boot application in Java code" are broad enough to overlap with sibling Plinth Spring Boot skills.	2 / 3
	Total	11 / 12 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: jabrena/plinth
Commit: aaee915

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.