503-frameworks-micronaut-validation

Use when you need to design, review, or improve validation in Micronaut applications — including Bean Validation on @Controller methods, @Body @Valid, query/path parameter validation, @ConfigurationProperties validation, custom constraints, nested DTO validation, and ExceptionHandler mapping for constraint violations. This should trigger for requests such as Add validation support in Micronaut; Review Micronaut validation rules; Improve request validation in Micronaut REST APIs; Add custom validation constraints in Micronaut; Validate Micronaut configuration properties. Part of Plinth Toolkit

Quality

82%

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

63%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.

The body is a well-structured overview with excellent progressive disclosure (a real, one-level-deep, clearly linked reference) and a workflow with explicit compile/verify checkpoints. Its weaknesses are duplication (reference-reading and trigger phrases repeated across sections) and thin actionability — the concrete validation guidance lives entirely in the reference while the body's steps stay generic.

Suggestions

Consolidate the repeated 'read the reference' instruction into one place (e.g., keep it only in Workflow step 1 or the Reference section) and drop the 'When to use this skill' list that duplicates the frontmatter description.

Add one small concrete example to the body (e.g., a minimal @Valid @Body DTO snippet or an ExceptionHandler mapping) so the skill is actionable without opening the reference.

Convert the 'SAFETY: If compilation fails, stop immediately' rule into a fix-and-retry loop (diagnose the error, fix, re-run compile) to strengthen the workflow's feedback checkpoints.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no concept over-explanation, but noticeably redundant: the instruction to read the reference appears in Constraints ('BEFORE APPLYING: Read the reference'), Workflow step 1, and the Reference section, and the 'When to use this skill' list duplicates the trigger phrases already in the description.	3 / 5
Actionability	Concrete build commands are present ('./mvnw compile', 'mvn clean verify'), but the core validation how-to (annotation patterns, exception handler code) is entirely delegated to the reference, and workflow steps like 'Identify requested outcomes, constraints, and the minimum safe set of changes' remain generic — key executable details are missing from the body.	3 / 5
Workflow Clarity	A clear 4-step sequence with explicit checkpoints (MANDATORY compile-before, SAFETY stop-on-failure, VERIFY-after), but the failure path is 'stop immediately' rather than a fix-and-retry feedback loop, leaving a minor validation gap versus the top anchor.	4 / 5
Progressive Disclosure	Verified against the actual bundle: references/503-frameworks-micronaut-validation.md exists, is exactly one level deep, and is clearly signaled via a dedicated Reference section with a proper link; the body is a well-organized overview with content appropriately split out.	5 / 5
	Total	15 / 20 Passed

Description

91%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 that explicitly covers both what the skill does and when to trigger it, with concrete, natural trigger phrases and a well-defined Micronaut validation niche. The only deductions are the second-person phrasing ('you need to') and minor overlap risk with closely related toolkit skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities (Bean Validation on @Controller methods, @Body @Valid, query/path parameter validation, @ConfigurationProperties validation, custom constraints, nested DTO validation, ExceptionHandler mapping) with comprehensive coverage, which would score 5; reduced by 1 per guideline because the description uses second person ('Use when you need to design...').	4 / 5
Completeness	Both questions are answered explicitly: the 'what' via the detailed action list ('design, review, or improve validation in Micronaut applications — including...') and the 'when' via 'Use when you need to...' plus the concrete 'This should trigger for requests such as...' phrases.	5 / 5
Trigger Term Quality	Explicit natural user requests ('Add validation support in Micronaut', 'Review Micronaut validation rules', 'Improve request validation in Micronaut REST APIs', 'Add custom validation constraints in Micronaut', 'Validate Micronaut configuration properties') comprehensively cover the natural phrasings a user would say, matching the top anchor.	5 / 5
Distinctiveness Conflict Risk	A clear niche (Micronaut validation) with triggers that all name Micronaut explicitly, but as 'Part of Plinth Toolkit' it has minor overlap risk with closely related sibling skills (e.g., the referenced 502-frameworks-micronaut-rest) and generic Bean Validation requests.	4 / 5
	Total	18 / 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/503-frameworks-micronaut-validation/SKILL.md
Commit: dca88dc

Reviewed: 3 hours 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.