CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

66

Quality

83%

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

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.

A well-structured instruction-only skill: lean body, concrete build commands with validation gates, and clean delegation to a single real reference file. Scores are capped at 4 by duplicate trigger lists, a missing fix-and-revalidate loop, and a monolithic reference file.

Suggestions

Drop the 'When to use this skill' section (it duplicates the frontmatter description verbatim) to reclaim tokens and remove redundancy.

Add an explicit error-recovery loop after verification (e.g. 'If verification fails, fix the reported issues and re-run verification before reporting') to close the feedback-loop gap.

Split references/301-frameworks-spring-boot-core.md into per-topic files (e.g. beans.md, configuration.md, concurrency.md) and link them from the coverage list so navigation scales with the 15 examples.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, delegating detail to the reference; the only waste is the 'When to use this skill' list duplicating the frontmatter triggers and overlapping the coverage list.

4 / 5

Actionability

Concrete executable commands ('./mvnw compile or mvn compile', './mvnw clean verify') and explicit stop/ask conditions, but steps like 'inspect the current project setup' remain high-level.

4 / 5

Workflow Clarity

A clear 4-step sequence with an explicit pre-change compile gate, a blocking condition ('If compilation fails, stop immediately'), post-change verification, and ambiguity/missing-input handling — but no fix-and-revalidate retry loop is spelled out.

4 / 5

Progressive Disclosure

SKILL.md is a proper overview pointing to a single, clearly signaled, one-level-deep reference file (verified to exist with all examples inline); the reference is a ~1400-line monolith whose 15 examples could be split per topic for easier navigation.

4 / 5

Total

16

/

20

Passed

Description

83%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 description: comprehensive, concrete, with an explicit use-when clause and enumerated trigger phrases. Main deductions are the second-person trigger phrasing and minor gaps in natural keyword variants.

DimensionReasoningScore

Specificity

Lists many concrete capabilities (@SpringBootApplication, @ConfigurationProperties with @Validated, @Primary/@Qualifier, graceful shutdown, virtual threads), matching the comprehensive anchor, but the second-person 'Use when you need to' phrasing triggers the guideline's -1 specificity penalty.

4 / 5

Completeness

Explicitly answers both what ('review, improve, or build Spring Boot 4.0.x applications — including...') and when ('Use when you need to...' plus 'This should trigger for requests such as...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural phrases users would say ('Review Java code for Spring Boot application', 'Tune Spring Boot graceful shutdown or virtual threads') with verb variations (review/improve/build/tune), but a few natural phrasings like 'dependency injection' or 'bean wiring' are missing.

4 / 5

Distinctiveness Conflict Risk

A clearly-scoped Spring Boot core niche with distinct framework-specific triggers, but 'Part of Plinth Toolkit' implies sibling Spring skills with which minor overlap risk exists.

4 / 5

Total

17

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

jabrena/plinth

Path

skills/301-frameworks-spring-boot-core/SKILL.md

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.