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, optional runtime OpenAPI exposure (SmallRye), contract-first generation from OpenAPI, 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
74
67%
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/402-frameworks-quarkus-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 excels across all dimensions. It provides an explicit 'Use when' trigger clause, lists an extensive and specific set of capabilities, and uses natural developer terminology that would match real user queries. The only minor concern is that the description is quite long and dense, bordering on a feature list rather than a concise summary, but the content quality is high.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists numerous specific concrete actions and capabilities: resource classes, HTTP methods, status codes, DTOs, Bean Validation, exception mappers, OpenAPI exposure, contract-first generation, content negotiation, pagination, sorting, filtering, API versioning, idempotency, optimistic concurrency, HTTP caching, API deprecation, RFC 7807 Problem Details, and more. | 3 / 3 |
Completeness | The description opens with an explicit 'Use when' clause ('Use when you need to design, review, or improve REST APIs with Quarkus REST') that clearly answers both what the skill does and when Claude should select it. The trigger guidance is explicit and upfront. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a user would mention: 'REST API', 'Quarkus', 'Jakarta REST', 'OpenAPI', 'pagination', 'sorting', 'filtering', 'API versioning', 'ETag', 'Cache-Control', 'Bean Validation', 'exception mappers', 'content negotiation', 'HTTP methods', 'status codes'. These are terms developers naturally use when working in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to Quarkus REST / Jakarta REST API design with a clear niche. The combination of Quarkus-specific terminology and detailed REST API concerns (idempotency keys, ETag/If-Match, Sunset headers, RFC 7807) makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill body functions primarily as a table of contents and a pointer to a reference file, with almost no actionable content of its own. It lists many topics but provides zero code examples, concrete patterns, or executable guidance for any of them. The constraints section has the right idea (compile before, verify after) but is repetitively stated rather than cleanly structured.
Suggestions
Add at least 2-3 concrete, executable code examples directly in the skill body — e.g., a minimal JAX-RS resource class, a Bean Validation DTO, and an ExceptionMapper for RFC 7807 — so the skill is actionable without requiring the reference file.
Consolidate the constraints into a clear numbered workflow: 1. Compile → 2. Apply changes → 3. Verify → 4. If verify fails, fix and re-verify.
Remove the redundant 'What is covered' bullet list or merge it with 'When to use this skill' to reduce duplication and improve conciseness.
Add a brief 'Quick start' section with a copy-paste-ready example of a well-structured Quarkus REST resource so the skill provides immediate value before deferring to the reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is relatively brief but includes a verbose 'What is covered' bullet list that essentially duplicates the description and the 'When to use this skill' section. The constraints section repeats the same compilation check idea five different ways. Some tightening would help. | 2 / 3 |
Actionability | There is no concrete code, no executable commands beyond generic 'mvnw compile', no examples of resource classes, DTOs, exception mappers, or any of the topics listed. All actual guidance is deferred entirely to the reference file, leaving the skill body as a table of contents with no actionable content. | 1 / 3 |
Workflow Clarity | There is a compile-before/verify-after workflow with a stop condition on failure, which is good. However, the steps are not clearly sequenced as a numbered workflow, validation is mentioned redundantly rather than structured, and there's no feedback loop for what to do if verification fails after changes. | 2 / 3 |
Progressive Disclosure | The skill correctly points to a single reference file for detailed rules and examples (one level deep), which is good. However, the SKILL.md itself contains almost no substantive quick-start content — it's essentially just a pointer with a long bullet list, so there's no useful overview content before the reference link. | 2 / 3 |
Total | 7 / 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.