502-frameworks-micronaut-rest

Use when you need to design, review, or improve REST APIs with Micronaut — including @Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, contract-first OpenAPI (OpenAPI Generator), optional runtime OpenAPI via micronaut-openapi, and security annotations. This should trigger for requests such as Review or improve Micronaut @Controller REST APIs; Add validation, error handling, or align controllers with the OpenAPI contract on Micronaut HTTP layer; Design Micronaut controllers and DTO validation; Add Micronaut exception handlers and Problem Details responses; Improve pagination filtering or OpenAPI alignment in Micronaut APIs. Part of Plinth Toolkit

Quality

83%

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

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

A well-structured overview skill: concrete Maven verification commands, a sequenced workflow with explicit safety checkpoints, and exemplary one-level-deep progressive disclosure to a real reference file. Its main weakness is redundancy — the coverage list and 'When to use' section restate the frontmatter description — and a missing post-verify failure-handling step.

Suggestions

Delete the 'When to use this skill' section (or replace it with a pointer to the reference) — it repeats the frontmatter description's trigger list verbatim and adds no new information.

Trim the 'What is covered in this Skill?' bullet list to items not already enumerated in the description, or merge it into a two-line scope statement, to reclaim roughly a third of the body.

Add one line for the verify step's failure path, e.g. 'VERIFY: if verification fails, revert or fix the change and re-run verify before reporting', to close the last validation gap in the workflow.

Dimension	Reasoning	Score
Conciseness	The body avoids explaining known concepts and gives tight commands, but it duplicates content wholesale: the 'What is covered in this Skill?' bullet list restates the frontmatter description's topic enumeration, and the 'When to use this skill' section repeats the description's trigger list verbatim — roughly a third of the body could be trimmed.	3 / 5
Actionability	Concrete, copy-paste-ready commands are present ('Run ./mvnw compile or mvn compile', 'Run ./mvnw clean verify or mvn clean verify') alongside specific technologies (@Valid, @Secured, Pageable, Idempotency-Key, ETag/If-Match), but the workflow steps themselves ('Gather scope and decide target improvements', 'Implement or refactor... following the reference patterns') stay high-level, deferring specifics to the reference.	4 / 5
Workflow Clarity	The 4-step sequence has explicit checkpoints (MANDATORY compile before, 'If compilation fails, stop immediately', VERIFY after) plus edge-case handling (ask a clarifying question when ambiguous; report missing tooling), but there is no instruction for what to do if the post-change verification fails, a minor validation gap versus the top anchor.	4 / 5
Progressive Disclosure	The body is a clean overview that pushes all detail to a single, clearly signaled, one-level-deep reference ('For detailed guidance, examples, and constraints, see references/502-frameworks-micronaut-rest.md'), which exists in the bundle and contains no nested references; sections (coverage, constraints, workflow, reference) are easy to navigate.	5 / 5
	Total	16 / 20 Passed

Description

87%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 answers both what and when with concrete, framework-anchored trigger phrases and a distinctive Micronaut niche. The only deductions are the second-person 'you' in the trigger clause and a few missing natural synonym terms.

Dimension	Reasoning	Score
Specificity	The description lists many concrete capabilities ('design, review, or improve REST APIs with Micronaut', '@Controller routes', 'ETag/If-Match', 'contract-first OpenAPI (OpenAPI Generator)'), matching the comprehensive anchor, but the second-person phrasing 'Use when you need to' triggers the rubric's explicit 1-point voice penalty from 5.	4 / 5
Completeness	Both parts are explicit: the 'what' enumerates the capability surface ('design, review, or improve REST APIs with Micronaut — including @Controller routes, HTTP status codes, DTOs, Bean Validation...') and the 'when' opens with 'Use when you need to...' plus a concrete list of trigger requests, exactly matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger requests are given verbatim ('Review or improve Micronaut @Controller REST APIs; Add validation, error handling...'), and 'Micronaut' is a strong distinctive keyword, but a few natural variations users would say (e.g. 'Java endpoints', 'Micronaut controllers/service', framework synonyms) are missing, fitting the 'good coverage, a few natural terms missing' anchor rather than the fully comprehensive one.	4 / 5
Distinctiveness Conflict Risk	'Micronaut' pins a clear niche with distinct triggers, and the enumerated trigger requests are framework-specific, so conflict risk with sibling skills (e.g. a generic REST or Spring REST skill) is minimal.	5 / 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/502-frameworks-micronaut-rest/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.