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

81%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

62%

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

This skill has a well-structured workflow with strong safety constraints and clear verification steps, which is its main strength. However, it lacks concrete code examples or executable patterns in the body itself—all substantive guidance is deferred to a reference file that cannot be verified. The topic coverage list is informative but adds verbosity without actionability.

Suggestions

Add at least one or two concrete, executable code examples (e.g., a minimal @Controller with @Valid and HttpResponse usage) directly in the SKILL.md to improve actionability without requiring the reference file.

Consider moving the 'What is covered' bullet list into the reference file or condensing it to 3-4 key categories to improve conciseness.

Include a brief 'bad pattern → good pattern' example inline to make the skill immediately useful even before reading the reference.

Dimension	Reasoning	Score
Conciseness	The 'What is covered' bullet list is somewhat verbose and reads like a feature catalog rather than actionable guidance. The constraints and workflow sections are reasonably tight, but the overall content could be leaner—e.g., the bullet list could be collapsed or moved to the reference file.	2 / 3
Actionability	The skill provides concrete build commands (./mvnw compile, mvn clean verify) and a clear workflow, but lacks any executable code examples, specific controller patterns, or copy-paste-ready snippets. All actual guidance is deferred to the reference file, making the SKILL.md itself more of a pointer than an actionable guide.	2 / 3
Workflow Clarity	The workflow is clearly sequenced with four numbered steps, includes explicit validation checkpoints (compile before, verify after), has safety stops (stop if compilation fails), and handles edge cases (ambiguous scope, missing inputs). The feedback loop of compile → apply → verify is well-defined.	3 / 3
Progressive Disclosure	The skill correctly references a single detailed reference file (references/502-frameworks-micronaut-rest.md) for deeper content, which is good one-level-deep disclosure. However, since no bundle files were provided, we cannot verify the reference exists or is well-structured. The SKILL.md itself includes a long inline bullet list of topics that could arguably live in the reference, slightly undermining the split.	2 / 3
	Total	9 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that excels across all dimensions. It provides comprehensive enumeration of specific capabilities, includes natural trigger terms users would use, explicitly states both what the skill does and when to use it, and is clearly scoped to the Micronaut REST API domain. The only minor weakness is that it's somewhat dense and could benefit from slightly better formatting for readability.

Dimension	Reasoning	Score
Specificity	Lists many specific concrete actions and technologies: @Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, contract-first OpenAPI, security annotations. Very comprehensive enumeration of capabilities.	3 / 3
Completeness	Explicitly opens with 'Use when you need to design, review, or improve REST APIs with Micronaut' (clear when clause) and lists comprehensive what capabilities. Also includes a 'This should trigger for requests such as...' section providing explicit trigger examples.	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'REST APIs', 'Micronaut', '@Controller', 'validation', 'error handling', 'OpenAPI', 'pagination', 'HTTP status codes', 'DTOs'. Also includes example trigger phrases like 'Review or improve Micronaut @Controller REST APIs' and 'Add validation, error handling'.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — scoped specifically to Micronaut framework REST API design with very specific technology markers (@Controller, micronaut-openapi, OpenAPI Generator). Unlikely to conflict with generic REST API skills or other Java framework skills due to the Micronaut-specific terminology throughout.	3 / 3
	Total	12 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Commit: 0d8350f

Reviewed: 2 days 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.