CtrlK
BlogDocsLog inGet started
Tessl Logo

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

71

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

85%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, well-structured overview that assumes Claude's knowledge and routes detail to a single one-level-deep reference, with an explicit compile/verify validation loop and clarifying-question guardrails. Its only weakness is actionability: the body states commands but no executable Spring Boot code or annotation patterns, deferring all examples to the reference.

Suggestions

Add 1-2 short inline code/annotation snippets (e.g., a minimal @ConfigurationProperties + @Validated example or a constructor-injection snippet) so the most common changes are actionable without opening the reference.

Show a concrete @Primary/@Qualifier disambiguation example inline, since that is a frequently-needed and self-contained pattern.

DimensionReasoningScore

Conciseness

The body is lean — it lists capability areas and a short workflow without explaining what Spring Boot or its annotations are, and offloads detail to the reference file; every section earns its place and assumes Claude's competence.

5 / 5

Actionability

It provides concrete commands (./mvnw compile, mvn clean verify) but no executable code or annotation examples in the body — concrete guidance is delegated to the reference file, so it instructs where to look rather than giving copy-paste-ready steps for the common cases.

3 / 5

Workflow Clarity

The Constraints section defines an explicit validation feedback loop (compile before changes -> stop on failure -> clean verify after -> ask on ambiguity/missing inputs), and the four-step Workflow sequences these checkpoints; validation is explicit with error-recovery guidance.

5 / 5

Progressive Disclosure

The body is an overview with well-signaled one-level-deep references (links to references/301-frameworks-spring-boot-core.md, which exists as a real bundle file), keeping detailed rules/examples out of SKILL.md; navigation is clear and shallow.

5 / 5

Total

18

/

20

Passed

Description

88%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 thorough, third-person description that pairs concrete Spring Boot 4.0.x capabilities with explicit verbatim trigger phrases, satisfying both the 'what' and 'when' requirements. It is slightly long and lists feature names alongside actions, which keeps specificity just below the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete capability areas (@SpringBootApplication, component annotations, @ConfigurationProperties with @Validated, @Primary/@Qualifier, graceful shutdown, virtual threads, scheduled tasks); coverage is comprehensive but some items are feature names rather than discrete actions, leaving minor gaps versus the score-5 anchor.

4 / 5

Completeness

Opens with 'Use when you need to review, improve, or build Spring Boot 4.0.x applications' (clear when) and enumerates concrete capabilities (clear what), then reinforces with 'This should trigger for requests such as...'; both what and when are explicit with concrete trigger phrases.

5 / 5

Trigger Term Quality

Embeds explicit verbatim trigger phrases ('Review Java code for Spring Boot application', 'Apply best practices for Spring Boot application in Java code') that match natural user requests, plus synonyms for each scenario; comprehensive natural-language coverage.

5 / 5

Distinctiveness Conflict Risk

The Spring Boot 4.0.x framing and specific annotations carve a clear niche distinct from generic Java skills, but it could overlap with sibling Spring skills (e.g., Spring Data/Security) in the same toolkit; minor overlap risk with closely related skills.

4 / 5

Total

18

/

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
jabrena/plinth
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.