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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

The body is well-structured with a strong verified workflow and clean one-level-deep progressive disclosure, but it loses points on actionability (core guidance is abstract and delegated) and mild conciseness redundancy from re-listing the description's triggers.

Suggestions

Add one or two short inline executable examples (e.g., a @Valid on a request DTO with a @NotBlank field and the resulting 400 body) so the core task guidance is actionable without forcing a round-trip to the reference.

Drop or compress the "When to use this skill" list, since it duplicates the trigger phrases already in the description frontmatter.

Keep the verified workflow as-is; it is the strongest part of the body.

Dimension	Reasoning	Score
Conciseness	The body is generally lean and free of concept explanations Claude already knows, but the "When to use this skill" list repeats verbatim the five trigger phrases already present in the frontmatter description, so some tokens do not earn their place and the section could be tightened.	2 / 3
Actionability	Concrete executable commands are present for the build lifecycle ("./mvnw compile", "mvn clean verify"), but the core validation guidance is abstract ("Apply framework-aligned changes", "Implement or refactor validation-related configuration/code following the reference patterns") with all specifics deferred to the reference file, leaving key details missing inline.	2 / 3
Workflow Clarity	A clear four-step sequence is paired with explicit validation checkpoints and a feedback loop ("MANDATORY: Run ... compile before applying any change", "If compilation fails, stop immediately", "VERIFY: Run ... clean verify after applying improvements"), matching the anchor for explicit validation steps with error recovery.	3 / 3
Progressive Disclosure	The SKILL.md is a concise overview that delegates detail to a single, well-signaled, one-level-deep reference ("see [references/303-frameworks-spring-boot-validation.md]"), and that referenced file exists in the bundle, giving clear navigation with appropriately split content.	3 / 3
	Total	10 / 12 Passed

Description

90%

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, specific description with explicit trigger guidance and a clear niche; its only rubric penalty is the second-person "Use when you need to" phrasing, which costs one specificity point per the voice guideline.

Suggestions

Rewrite the opening in third person to avoid the second-person "you" (e.g., "Use when designing, reviewing, or improving validation in Spring Boot applications") to restore the specificity point.

Consider trimming the trailing "Part of Plinth Toolkit" tag, which adds no trigger value for model selection.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions ("design, review, or improve validation", "Bean Validation on request DTOs", "@Valid/@Validated at API boundaries", "constraint groups", "custom constraints", "@ConfigurationProperties validation", "nested DTO validation", "consistent validation error handling") which would normally anchor at 3, but it opens with second person ("Use when you need to..."), and the rubric guidelines mandate reducing specificity by 1 for second-person voice.	2 / 3
Completeness	It clearly answers both what (the enumerated validation capabilities) and when (an explicit "Use when..." clause plus a "This should trigger for requests such as..." list), matching the anchor for explicit triggers on both dimensions.	3 / 3
Trigger Term Quality	Explicit trigger phrases map to natural user requests ("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"), giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	It carves a clear niche (Spring Boot Bean Validation specifically) with distinct, domain-anchored triggers, making it unlikely to fire for unrelated skills.	3 / 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.