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. Part of the skills-for-java project
83
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/502-frameworks-micronaut-rest/SKILL.mdQuality
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), provides an explicit 'Use when' trigger clause, and lists an extensive set of specific capabilities and technologies. The description is comprehensive, uses natural developer terminology, and occupies a clear niche that minimizes conflict with other skills. The only minor note is that the trailing 'Part of the skills-for-java project' adds no selection value, but it doesn't detract significantly.
| 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, runtime OpenAPI via micronaut-openapi, and security annotations. | 3 / 3 |
Completeness | The description explicitly answers both 'what' (design, review, or improve REST APIs with Micronaut including a comprehensive list of features) and 'when' ('Use when you need to design, review, or improve REST APIs with Micronaut') with a clear trigger clause at the beginning. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would say: 'REST API', 'Micronaut', '@Controller', 'HTTP status codes', 'DTOs', 'Bean Validation', 'pagination', 'OpenAPI', 'caching headers', 'versioning', 'security annotations'. These are terms developers naturally use when working in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — it targets specifically Micronaut REST API design with very specific framework-level concepts like @Controller, micronaut-openapi, and OpenAPI Generator. This is unlikely to conflict with generic API skills or other Java framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions primarily as a pointer to a reference file, providing good structure and clear build/verify constraints but lacking any concrete code examples or actionable REST patterns in the skill body itself. The progressive disclosure is well done, but the skill's value is almost entirely dependent on the referenced file, leaving the SKILL.md itself with limited standalone actionability.
Suggestions
Add at least 2-3 concrete, executable code examples directly in the SKILL.md (e.g., a minimal @Controller with @Valid, an ExceptionHandler pattern, or a pagination example) so Claude has immediately actionable guidance without needing to read the reference.
Convert the 'What is covered' bullet list into a more actionable quick-reference format, such as a table mapping common tasks to specific Micronaut annotations/patterns (e.g., 'Optimistic concurrency → ETag + @Header("If-Match")').
Add a brief sequenced workflow for reviewing/improving a REST controller (e.g., 1. Check status codes, 2. Validate DTOs, 3. Check error handling, 4. Verify OpenAPI alignment) to improve workflow clarity beyond just the compile/verify steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bullet list of covered topics is somewhat verbose and reads like a table of contents rather than actionable content. The 'What is covered in this Skill?' section could be trimmed since it mostly just lists topics without adding instructional value. However, it's not egregiously padded. | 2 / 3 |
Actionability | The constraints section provides concrete commands (`./mvnw compile`, `./mvnw clean verify`) which is good, but the skill itself contains zero code examples, no concrete patterns, and delegates all actual guidance to the reference file. Claude would need to read the reference to do anything useful. | 2 / 3 |
Workflow Clarity | There is a clear compile-before/verify-after workflow with a stop-on-failure checkpoint, which is good. However, the actual REST API improvement workflow (what to check, in what order, how to validate REST design decisions) is entirely absent and deferred to the reference file. | 2 / 3 |
Progressive Disclosure | The skill is well-structured as a concise overview with a clear, one-level-deep reference to the detailed guidance file. The sections (constraints, when to use, reference) are well-signaled and appropriately scoped for a SKILL.md that delegates detail to a reference document. | 3 / 3 |
Total | 9 / 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
1847adc
- 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.