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
88
85%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 clearly defines its scope (Micronaut REST API design and review), lists comprehensive specific capabilities, includes explicit trigger guidance with example requests, and is highly distinctive due to its framework-specific focus. The only minor weakness is that it reads somewhat dense and list-heavy, but this doesn't detract from its functional quality as a skill selector.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists numerous specific concrete actions and concepts: @Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, contract-first OpenAPI, security annotations. This is highly specific and comprehensive. | 3 / 3 |
Completeness | Clearly answers both 'what' (design, review, improve REST APIs with Micronaut including a comprehensive list of capabilities) and 'when' ('Use when you need to design, review, or improve REST APIs with Micronaut' plus explicit trigger examples like 'Review or improve Micronaut @Controller REST APIs'). The 'Use when' clause is present and explicit. | 3 / 3 |
Trigger Term Quality | Includes many natural keywords a user would say: 'REST APIs', 'Micronaut', '@Controller', 'validation', 'error handling', 'OpenAPI', 'pagination', 'HTTP status codes', 'DTOs', 'caching headers', 'versioning'. Good coverage of terms developers would naturally use when working in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Micronaut framework REST API design with very specific triggers like '@Controller', 'micronaut-openapi', 'OpenAPI Generator', and 'Micronaut HTTP layer'. Unlikely to conflict with generic REST API or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has strong structural qualities — clear workflow with validation checkpoints, good progressive disclosure, and appropriate scoping. However, it lacks concrete code examples or executable patterns in the body itself, deferring nearly all substantive guidance to the reference file. The introductory bullet list enumerates topics without adding actionable value, consuming tokens that could be better used for a quick-start example.
Suggestions
Add at least one concrete, copy-paste-ready Micronaut code example (e.g., a @Controller with @Valid, HttpResponse, and an ExceptionHandler) to make the skill body actionable without requiring the reference file.
Trim or remove the 'What is covered' bullet list — it reads as a table of contents for the reference file rather than providing actionable guidance, and Claude doesn't need a preview of topics it can read in 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 introductory enumeration could be trimmed since it mostly restates what's in 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 Micronaut annotations in context, or copy-paste-ready patterns. All substantive guidance is deferred to the reference file. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced (read reference → gather scope → apply changes → verify), includes explicit validation checkpoints (compile before, verify after), has a stop condition on compilation failure, and handles edge cases (ambiguous scope, missing inputs). | 3 / 3 |
Progressive Disclosure | The skill provides a clear overview with a single, well-signaled reference to the detailed file (references/502-frameworks-micronaut-rest.md). Navigation is one level deep and clearly indicated. The content is appropriately split between overview and detailed reference. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%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
899d988
- Reviewed
Table of Contents
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.