403-frameworks-quarkus-validation

Use when you need to design, review, or improve validation in Quarkus applications — including Bean Validation on JAX-RS resources, @Valid on parameters and CDI beans, constraint groups, @ConfigMapping validation, custom constraints, nested DTO validation, and ExceptionMapper-based error mapping. This should trigger for requests such as Add validation support in Quarkus; Review Quarkus validation rules; Improve request validation in Quarkus REST APIs; Add custom validation constraints in Quarkus; Validate Quarkus @ConfigMapping properties. 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.

A well-structured overview with excellent workflow checkpoints and clean one-level-deep progressive disclosure into a real, organized reference. Its weaker spots are mild redundancy with the description and abstract deferral of the actual implementation guidance to the reference.

Suggestions

Remove or compress the 'When to use this skill' section since its trigger list duplicates the frontmatter description, reclaiming tokens.

Make workflow step 3 more concrete by naming the specific reference patterns to apply (e.g. '@Valid on request bodies, @ConfigMapping constraints, quarkus-http-problem for RFC 7807') rather than 'following the reference patterns'.

Add a one-line pointer to the reference's Example table of contents so Claude can navigate directly to the relevant pattern.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining concepts Claude already knows, but the 'When to use this skill' section duplicates the description's trigger list and 'What is covered' restates the same capabilities, so it could be tightened.	2 / 3
Actionability	Concrete build commands are present, but the core implementation guidance is deferred entirely to the reference and workflow step 3 ('Implement or refactor... following the reference patterns and project conventions') is abstract rather than instructive.	2 / 3
Workflow Clarity	Four clearly sequenced steps with explicit validation checkpoints and a feedback loop (MANDATORY compile before, SAFETY stop on failure, VERIFY after), matching the anchor for clear sequence with error-recovery checkpoints.	3 / 3
Progressive Disclosure	A concise overview pointing one level deep to the verified reference file references/403-frameworks-quarkus-validation.md, clearly signaled via the ## Reference link and 'BEFORE APPLYING: Read the reference' instruction.	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, well-triggered description that clearly communicates both capability and activation conditions for Quarkus validation work. Its only real weakness is the second-person 'you need' phrasing, which the rubric penalizes.

Suggestions

Rewrite in third person to avoid the voice penalty, e.g. 'Use when designing, reviewing, or improving validation in Quarkus applications' (drop 'you need to').

Consider noting the sibling @402-frameworks-quarkus-rest relationship explicitly in the description to sharpen distinctiveness against a general Quarkus REST skill.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions (Bean Validation on JAX-RS resources, @ConfigMapping validation, custom constraints, nested DTO validation, ExceptionMapper-based error mapping) which would merit a 3, but the second-person phrasing 'Use when you need to design...' triggers the rubric's -1 voice penalty.	2 / 3
Completeness	Explicitly states both what it does (the enumerated validation capabilities) and when to use it ('This should trigger for requests such as...' plus 'Use when...'), satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Includes natural user phrases such as 'Add validation support in Quarkus', 'Review Quarkus validation rules', and 'Validate Quarkus @ConfigMapping properties' that a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The niche is tightly scoped to Quarkus validation and all triggers are Quarkus-validation-specific, making it unlikely to fire for a different skill.	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.