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

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 clean, well-structured skill overview with a strong validation-gated workflow and good one-level-deep progressive disclosure. It loses points on conciseness (duplication of the description) and actionability (the core REST guidance lives entirely in the reference rather than the body).

Suggestions

Remove or condense the 'What is covered in this Skill?' bullet list and 'When to use this skill' section, since they duplicate the frontmatter description, to tighten the body.

Add one small, concrete in-body example (e.g., a minimal @Controller snippet with @Valid and an HttpResponse status) so the body carries at least some executable guidance instead of deferring everything to the reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient, but the 'What is covered in this Skill?' bullet list and the 'When to use this skill' section largely duplicate the frontmatter description, and the opener 'Apply REST design principles for Micronaut HTTP applications.' is light padding, so it could be tightened.	2 / 3
Actionability	It provides concrete, copy-paste-ready commands ('Run `./mvnw compile` or `mvn compile`', 'Run `./mvnw clean verify`') and a specific file to read, but the substantive REST design guidance is deferred entirely to the reference rather than being present in the body, leaving the core instruction incomplete here.	2 / 3
Workflow Clarity	The four-step workflow is clearly sequenced and backed by explicit validation checkpoints (MANDATORY compile-before, SAFETY stop-on-fail, VERIFY after), forming a compile -> stop-on-failure -> verify feedback loop that matches the anchor for full marks.	3 / 3
Progressive Disclosure	The body is a concise overview that points to a single, verified, well-organized reference (references/502-frameworks-micronaut-rest.md) one level deep, with clear signaling in both the Workflow and Reference sections, matching the well-signaled one-level-deep anchor.	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, and well-triggered description that clearly answers both what the skill does and when to use it, with a distinct Micronaut REST niche. Its only real weakness is the second-person 'you' phrasing, which costs it a specificity point under the rubric.

Suggestions

Rewrite 'Use when you need to design, review, or improve...' in the third person (e.g., 'Use when designing, reviewing, or improving REST APIs with Micronaut...') to avoid the second-person penalty.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions and technical areas ('design, review, or improve REST APIs', '@Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match'), which would be a 3, but the description uses second-person voice ('Use when you need to...'), which the rubric penalizes by reducing specificity by 1.	2 / 3
Completeness	It clearly answers both 'what' (the capability list) and 'when' via an explicit 'Use when...' clause plus a 'This should trigger for requests such as...' enumeration, satisfying the explicit-trigger requirement.	3 / 3
Trigger Term Quality	Natural user phrasings are explicitly enumerated ('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'), giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	It is tightly niched to Micronaut ('REST APIs with Micronaut', 'Micronaut @Controller REST APIs', 'OpenAPI contract on Micronaut HTTP layer'), making it unlikely to trigger for the wrong 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/cursor-rules-java
Commit: 159e7ce

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.