CtrlK
BlogDocsLog inGet started
Tessl Logo

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 cursor-rules-java project

59

Quality

67%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/503-frameworks-micronaut-validation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

35%

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

This skill functions primarily as a pointer to an external reference file rather than providing standalone actionable guidance. While it has reasonable structure and includes important safety constraints (compile before, verify after), it lacks any concrete code examples, specific validation patterns, or executable snippets that would make it immediately useful. The content is a thin orchestration layer that depends entirely on the referenced file for substance.

Suggestions

Add at least 2-3 concrete, executable code examples inline — e.g., a DTO with Bean Validation annotations, a controller method with @Valid @Body, and a basic ExceptionHandler for ConstraintViolationException — so the skill is actionable without reading the reference file.

Consolidate the 'What is covered' and 'When to use this skill' sections into a single concise list to reduce redundancy.

Add explicit validation/error-recovery steps in the workflow, such as 'If tests fail after applying validation changes, check for missing @Introspected annotations on DTOs' with specific diagnostic commands.

Include a minimal but complete example of the expected validation error response payload (JSON) so Claude knows the target output format.

DimensionReasoningScore

Conciseness

The skill is reasonably concise but includes some unnecessary content: the 'What is covered' bullet list largely duplicates the 'When to use this skill' section, and the 'Scope' line adds little value. The description of what the skill covers is somewhat redundant given Claude's existing knowledge of Micronaut validation concepts.

2 / 3

Actionability

The skill provides no concrete code examples, no executable commands beyond generic Maven invocations, and no specific validation patterns. All substantive guidance is deferred to the reference file. The body itself describes rather than instructs — it tells Claude to 'follow the reference patterns' without showing any actual patterns.

1 / 3

Workflow Clarity

The workflow has a clear 4-step sequence with compilation checks before and verification after changes, which is good. However, the steps are vague ('Apply framework-aligned changes', 'Gather scope and decide target improvements') and lack explicit validation checkpoints or error recovery loops between steps. The mandatory compile/verify constraints partially compensate.

2 / 3

Progressive Disclosure

The skill correctly references a single external file for detailed guidance, which is good one-level-deep disclosure. However, since no bundle files were provided, we cannot verify the reference exists or is well-structured. The SKILL.md itself is essentially a thin wrapper that defers almost all actionable content to the reference, making the main file too sparse to be useful on its own.

2 / 3

Total

7

/

12

Passed

Description

100%

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 skill description that clearly defines its scope (Micronaut validation), lists specific concrete capabilities, and provides explicit trigger examples. It effectively combines a 'Use when' clause with example trigger phrases, making it easy for Claude to select this skill appropriately. The only minor weakness is that it leads with 'Use when' rather than a brief capability summary first, but the content is comprehensive and well-structured.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: Bean Validation on @Controller methods, @Body @Valid, query/path parameter validation, @ConfigurationProperties validation, custom constraints, nested DTO validation, and ExceptionHandler mapping for constraint violations.

3 / 3

Completeness

Clearly answers both 'what' (design, review, or improve validation in Micronaut applications with specific validation types listed) and 'when' (explicit 'Use when' clause at the start plus 'This should trigger for requests such as...' with concrete examples).

3 / 3

Trigger Term Quality

Includes strong natural trigger terms users would say: 'Add validation support in Micronaut', 'Review Micronaut validation rules', 'Improve request validation in Micronaut REST APIs', 'Add custom validation constraints', 'Validate Micronaut configuration properties'. Covers multiple natural phrasings and variations.

3 / 3

Distinctiveness Conflict Risk

Highly specific to Micronaut framework validation, with distinct triggers like '@ConfigurationProperties validation', 'Bean Validation on @Controller methods', and Micronaut-specific terminology that would not overlap with generic validation or other framework skills.

3 / 3

Total

12

/

12

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/cursor-rules-java
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.