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

92%

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

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.

The body is a well-organized, concise overview with strong validation checkpoints and a clean single-level reference structure. Its main weakness is slight redundancy with the description's triggers and implementation guidance that is delegated to the reference rather than shown inline.

Suggestions

Remove or condense the 'When to use this skill' section since those trigger phrases already appear in the frontmatter description, avoiding duplication.

Add one small inline code snippet (e.g., a minimal @Body @Valid controller example) in the Workflow so the body is actionable on its own before deferring to the reference.

Dimension	Reasoning	Score
Conciseness	The body is lean with no over-explanation of concepts Claude already knows, but the 'When to use this skill' section duplicates trigger phrases already present in the description, a minor redundancy that keeps it just below fully efficient.	4 / 5
Actionability	Concrete build commands ('./mvnw compile', 'mvn clean verify') and an explicit reference path are given, but the core implementation guidance ('Implement or refactor validation-related configuration/code following the reference patterns') is delegated to the reference rather than providing concrete inline examples.	4 / 5
Workflow Clarity	A clear 4-step sequence is paired with explicit validation checkpoints — 'Run ./mvnw compile before applying any change', 'If compilation fails, stop immediately', and 'Run ./mvnw clean verify after applying improvements' — forming a compile→stop-if-fail→verify feedback loop.	5 / 5
Progressive Disclosure	The short (~53-line) overview is well-sectioned and points to a single one-level-deep reference (references/503-frameworks-micronaut-validation.md, which exists) with no nested references, matching the clear-overview anchor.	5 / 5
	Total	18 / 20 Passed

Description

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

This is a strong, exemplar-style description: it is specific, uses natural trigger phrases, answers both 'what' and 'when' explicitly, and is clearly scoped to Micronaut validation. No changes needed.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete validation capabilities — 'Bean Validation on @Controller methods, @Body @Valid, query/path parameter validation, @ConfigurationProperties validation, custom constraints, nested DTO validation, and ExceptionHandler mapping' — giving comprehensive, specific coverage rather than generic language.	5 / 5
Completeness	It explicitly states both what the skill does (the enumerated validation capabilities introduced by 'including') and when to use it via 'Use when...' plus 'This should trigger for requests such as...' with concrete trigger phrases.	5 / 5
Trigger Term Quality	It lists natural user phrasings verbatim ('Add validation support in Micronaut', 'Review Micronaut validation rules', 'Improve request validation in Micronaut REST APIs', 'Validate Micronaut configuration properties'), which are exactly the phrases a user would say when needing this skill.	5 / 5
Distinctiveness Conflict Risk	'validation in Micronaut applications' with 'Micronaut' repeated throughout every trigger carves a clear niche with minimal overlap risk against generic or other-framework validation skills.	5 / 5
	Total	20 / 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: 05bf9d1

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