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

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

92%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 content is a tight, well-structured overview with a validated workflow and a cleanly signaled single reference. Its only gap is that the substantive API code patterns live entirely in the reference rather than being previewed inline, which lightly limits actionability of the body alone.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: it lists capabilities and constraints without explaining what Micronaut, REST, or Bean Validation are, and every section earns its place.	5 / 5
Actionability	Provides concrete executable build commands (./mvnw compile, mvn clean verify) and a clearly pointed-to real reference holding the API patterns, but the body itself carries no inline controller/DTO code examples, leaving a minor gap.	4 / 5
Workflow Clarity	A clear four-step sequence is paired with a Constraints block that adds explicit validation checkpoints and an error-recovery feedback loop (compile before, stop immediately if it fails, verify after).	5 / 5
Progressive Disclosure	SKILL.md is an overview that signals a single one-level-deep reference (references/502-frameworks-micronaut-rest.md, verified present) in both the workflow and a dedicated Reference section, keeping navigation easy and the body uncluttered.	5 / 5
	Total	19 / 20 Passed

Description

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

The description is specific, comprehensive, and clearly scoped to Micronaut REST APIs, with explicit trigger guidance covering both what and when. It is slightly jargon-forward and lacks broader synonym/extension coverage, which keeps trigger term quality just below the top anchor.

Dimension	Reasoning	Score
Specificity	Lists numerous concrete actions and capabilities (design/review/improve REST APIs, @Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, OpenAPI Generator, security annotations), giving comprehensive coverage rather than just several.	5 / 5
Completeness	Explicitly answers both what (design/review/improve Micronaut REST APIs with the listed capabilities) and when ('This should trigger for requests such as...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases a user would say ('Review or improve Micronaut @Controller REST APIs', 'Add validation, error handling', 'Improve pagination filtering or OpenAPI alignment'), but is somewhat framework-jargon heavy and lacks the synonym/file-extension breadth that defines the top anchor.	4 / 5
Distinctiveness Conflict Risk	Targets a clear, specific niche (the Micronaut framework's HTTP/REST layer) with distinct triggers, making conflict with other skills minimal.	5 / 5
	Total	19 / 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: 77b8825

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