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, OpenAPI, and security annotations. Part of the skills-for-java project
77
71%
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 communicates its purpose, scope, and trigger conditions. It opens with an explicit 'Use when' clause, lists comprehensive specific capabilities, and includes framework-specific terminology (Micronaut) that makes it highly distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: '@Controller routes, HTTP status codes, DTOs, Bean Validation, exception handlers, pagination, idempotency, ETag/If-Match, caching headers, versioning, OpenAPI, and security annotations.' | 3 / 3 |
Completeness | Explicitly answers both what ('design, review, or improve REST APIs') and when ('Use when you need to...') with clear trigger conditions at the start of the description. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'REST APIs', 'Micronaut', '@Controller', 'HTTP status codes', 'DTOs', 'pagination', 'OpenAPI', 'security annotations' - these are terms developers naturally use when working with API design. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Micronaut' as a specific framework identifier, combined with REST API-specific terminology. Unlikely to conflict with generic Java skills or other framework-specific skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good structure and appropriate progressive disclosure, but critically lacks actionable content. It functions more as a table of contents pointing to a reference file rather than providing executable guidance. The compile/verify workflow is a strength, but the absence of any concrete code examples or specific implementation patterns significantly limits its utility.
Suggestions
Add at least 2-3 concrete, executable code examples showing key patterns (e.g., a @Controller with @Valid, an ExceptionHandler, pagination with Pageable)
Include a specific example of the problem JSON error response format mentioned
Add a brief workflow for the REST refactoring process itself (e.g., 1. Identify endpoints, 2. Add validation, 3. Add error handlers, 4. Add OpenAPI annotations)
Condense the 'What is covered' list into categories or remove items that are self-explanatory from the reference link
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but the 'What is covered' bullet list is somewhat verbose and could be condensed. The constraints section is appropriately lean. | 2 / 3 |
Actionability | No concrete code examples, commands beyond compile/verify, or executable guidance. The skill describes what it covers but delegates all actual implementation details to a reference file without providing any copy-paste ready examples. | 1 / 3 |
Workflow Clarity | The constraints section provides a clear compile-before/verify-after workflow with validation checkpoints, but the actual REST API improvement process lacks sequenced steps or feedback loops for the refactoring work itself. | 2 / 3 |
Progressive Disclosure | Clean structure with overview content in the main file and a single, clearly signaled reference link for detailed guidance. Appropriate separation of concerns with one-level-deep navigation. | 3 / 3 |
Total | 8 / 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.
a886986
Table of Contents
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.