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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

A well-structured, lean overview with strong workflow validation and clean progressive disclosure to a real reference file. Its one gap is standalone actionability: the body holds build commands but no representative REST code examples before deferring to the reference.

Suggestions

Add one minimal inline @Controller/DTO snippet (e.g. a representative route with @Valid and an HttpResponse return) so the body is actionable on its own before the user opens the reference.

Consider trimming the 'When to use this skill' section, which duplicates the description's trigger list and slightly reduces token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is lean — bullet lists and short constraints with no concept over-explanation (it does not explain what REST or Micronaut is), and every section earns its place; the only mild redundancy is 'When to use this skill' mirroring the description's triggers.	3 / 3
Actionability	Concrete executable commands are present ('./mvnw compile', './mvnw clean verify') and the reference path is specific, but the body defers all actual REST API code/examples to the reference file, so standalone actionable guidance is incomplete for a code-centric skill.	2 / 3
Workflow Clarity	A clear 4-step sequence is paired with explicit validation checkpoints and a feedback loop: 'MANDATORY: Run ./mvnw compile before applying any change', 'SAFETY: If compilation fails, stop immediately', 'VERIFY: Run ./mvnw clean verify after applying improvements', plus edge-case handling.	3 / 3
Progressive Disclosure	The body is an overview that points to a single, real, one-level-deep reference via a clearly signaled markdown link ([references/502-frameworks-micronaut-rest.md](references/502-frameworks-micronaut-rest.md)), with detail appropriately split out.	3 / 3
	Total	11 / 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 specific, well-triggered description with strong what/when coverage and a clear framework niche. Its only real flaw is second-person voice, which caps the specificity dimension.

Suggestions

Rewrite in third person to remove the second-person penalty, e.g. 'Designs, reviews, or improves REST APIs with Micronaut. Use when the user asks to...'.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities ('@Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match'), which would be a 3, but the second-person voice ('Use when you need to design, review, or improve') triggers the mandated -1 specificity penalty.	2 / 3
Completeness	Explicitly answers both what ('design, review, or improve REST APIs with Micronaut — including...') and when ('Use when you need to...' plus 'This should trigger for requests such as...'), with explicit trigger guidance.	3 / 3
Trigger Term Quality	Natural phrases a user would actually say are well covered — 'Review or improve Micronaut @Controller REST APIs', 'Add validation, error handling', 'Design Micronaut controllers', 'Add Micronaut exception handlers', 'pagination filtering or OpenAPI alignment'.	3 / 3
Distinctiveness Conflict Risk	The Micronaut framework niche is clearly named and triggers are Micronaut-specific ('Micronaut @Controller REST APIs', 'micronaut-openapi'), making conflict with other skills unlikely; 'Part of Plinth Toolkit' reinforces the distinct niche.	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.