303-frameworks-spring-boot-validation

Use when you need to design, review, or improve validation in Spring Boot applications — including Bean Validation on request DTOs, @Valid/@Validated at API boundaries, constraint groups, custom constraints, @ConfigurationProperties validation, nested DTO validation, and consistent validation error handling. This should trigger for requests such as Add validation support in Spring Boot; Review Spring Boot validation rules; Improve request validation in Spring Boot REST APIs; Add custom Bean Validation constraints in Spring Boot; Validate configuration properties in Spring Boot. Part of Plinth Toolkit

Quality

81%

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

Quality

Content

78%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, lean skill body that appropriately delegates detail to a single clearly signaled reference and gates work behind compile/verify validation. Weaknesses are mild: duplicated trigger phrasing and failure handling that stops rather than retries.

Suggestions

Turn the 'If compilation fails, stop immediately' guidance into an explicit fix-and-revalidate feedback loop to reach the top workflow-clarity anchor.

Drop or compress the 'When to use this skill' list since it repeats the frontmatter description's triggers, recovering token budget.

Include one or two inline annotation examples (e.g., a @Valid controller snippet) so the body is actionable without forcing a reference round-trip for the common case.

Dimension	Reasoning	Score
Conciseness	The body is lean with bullet lists and short steps and assumes Claude's knowledge of Spring Boot/Bean Validation, but the 'When to use this skill' list duplicates the frontmatter trigger phrases, a minor redundancy that could be trimmed.	4 / 5
Actionability	Concrete executable commands are present ('./mvnw compile', 'mvn clean verify') and the workflow is directive, but the actual validation code patterns are deferred to the reference rather than shown inline, leaving minor gaps.	4 / 5
Workflow Clarity	A clear 4-step sequence is paired with explicit validation checkpoints ('MANDATORY: Run compile before any change', 'SAFETY: If compilation fails, stop immediately', 'VERIFY: Run clean verify after'), but the failure handling is a hard stop rather than a fix-and-retry feedback loop.	4 / 5
Progressive Disclosure	The body is a concise overview that signals a single one-level-deep reference via a markdown link to references/303-frameworks-spring-boot-validation.md (verified to exist), with well-organized sections and easy navigation.	5 / 5
	Total	17 / 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, well-scoped description with explicit 'what' and 'when' coverage and natural trigger phrases. The main deduction is the second-person voice ('you need to'), which the rubric penalizes on specificity.

Suggestions

Rewrite the description in third person (e.g., 'Use when designing, reviewing, or improving validation in Spring Boot applications') to avoid the second-person specificity penalty.

Add synonyms or token variants (e.g., 'Jakarta Bean Validation', 'Hibernate Validator', 'JSR-380') to push trigger-term coverage toward the comprehensive anchor.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities ('Bean Validation on request DTOs, @Valid/@Validated at API boundaries, constraint groups, custom constraints, @ConfigurationProperties validation, nested DTO validation, and consistent validation error handling') approaching the comprehensive anchor, but reduced by 1 per the second-person penalty since it opens 'Use when you need to design, review, or improve'.	4 / 5
Completeness	Explicitly answers both what (the validation capabilities enumerated) and when ('Use when you need to design, review, or improve validation in Spring Boot applications' plus a concrete 'This should trigger for requests such as' list), matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases are well covered ('Add validation support in Spring Boot; Review Spring Boot validation rules; Improve request validation in Spring Boot REST APIs; Add custom Bean Validation constraints in Spring Boot; Validate configuration properties in Spring Boot'), but synonyms and file extensions are absent, keeping it just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	The Spring Boot validation niche is clearly scoped with distinct triggers, but 'validation' broadly overlaps with general Java/Bean Validation skills, so minor overlap risk remains.	4 / 5
	Total	17 / 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: jabrena/plinth
Path: skills/303-frameworks-spring-boot-validation/SKILL.md
Commit: 05bf9d1

Reviewed: 4 minutes 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.