402-frameworks-quarkus-rest
Use when you need to design, review, or improve REST APIs with Quarkus REST (Jakarta REST) — including resource classes, HTTP methods, status codes, request/response DTOs, Bean Validation, exception mappers, OpenAPI with SmallRye, content negotiation, pagination, sorting and filtering, API versioning, idempotency (Idempotency-Key), optimistic concurrency (ETag / If-Match), HTTP caching (Cache-Control), API deprecation (Sunset / Deprecation headers), RFC 7807 Problem Details, ISO-8601 for time in contracts, and security-aware boundaries. Part of the skills-for-java project
94
92%
Does it follow best practices?
Impact
Pending
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 an excellent skill description that comprehensively covers REST API design with Quarkus. It excels in all dimensions: explicit 'Use when' trigger, extensive specific capabilities, natural developer terminology, and a clearly defined niche. The description uses proper third-person voice and provides enough detail for accurate skill selection among many alternatives.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists extensive specific concrete actions: 'design, review, or improve REST APIs' with detailed capabilities including 'resource classes, HTTP methods, status codes, request/response DTOs, Bean Validation, exception mappers, OpenAPI with SmallRye, content negotiation, pagination, sorting and filtering, API versioning, idempotency, optimistic concurrency, HTTP caching, API deprecation, RFC 7807 Problem Details, ISO-8601 for time in contracts, and security-aware boundaries.' | 3 / 3 |
Completeness | Clearly answers both what ('design, review, or improve REST APIs' with comprehensive feature list) AND when ('Use when you need to...'). The explicit 'Use when' clause at the beginning provides clear trigger guidance for skill selection. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'REST APIs', 'Quarkus REST', 'Jakarta REST', 'HTTP methods', 'status codes', 'DTOs', 'Bean Validation', 'OpenAPI', 'pagination', 'sorting', 'filtering', 'API versioning', 'ETag', 'Cache-Control', 'Sunset headers'. These are terms developers naturally use when working with REST API design. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Quarkus REST/Jakarta REST APIs with very specific technical features. The combination of 'Quarkus REST', 'Jakarta REST', and detailed REST-specific patterns like 'Idempotency-Key', 'RFC 7807 Problem Details' makes it unlikely to conflict with general Java or generic API skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates strong organization with clear constraints, validation checkpoints, and appropriate progressive disclosure to a reference file. The main weakness is the lack of any concrete code examples in the skill body itself - all actionable code is deferred to the reference, which may require Claude to always consult the external file for basic operations.
Suggestions
Add 1-2 minimal executable code examples directly in the skill body (e.g., a basic resource class with @Path and a simple ExceptionMapper) to provide immediate actionability without requiring reference lookup
Include a quick-start snippet showing the most common pattern (e.g., a POST endpoint returning 201 with Location header) that can be copy-pasted
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing a clear table of contents without explaining concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context. | 3 / 3 |
Actionability | The skill provides clear constraints and verification commands (mvnw compile, mvn clean verify), but lacks concrete code examples directly in the skill body. All executable guidance is deferred to the reference file. | 2 / 3 |
Workflow Clarity | Clear workflow with explicit validation checkpoints: compile before changes, verify after changes, stop on compilation failure. The sequence is unambiguous with explicit blocking conditions and safety gates. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, clear scope definition, and a single well-signaled reference to detailed documentation. One-level-deep reference pattern is properly implemented. | 3 / 3 |
Total | 11 / 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
b36efb2
- 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.