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. This should trigger for requests such as Review or improve JAX-RS resources in a Quarkus project; Design HTTP APIs with validation and error handling on Quarkus; Add API versioning, idempotency, ETag concurrency, or deprecation headers; Implement pagination, sorting, or RFC 7807 Problem Details error responses. Part of cursor-rules-java project

Quality

67%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/402-frameworks-quarkus-rest/SKILL.md

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 thoroughly covers specific capabilities, provides explicit trigger guidance with example requests, and occupies a clearly distinct niche. The description is comprehensive and uses natural developer terminology. The only minor concern is that it is quite long and dense, which could be slightly more concise, but the verbosity is justified by the breadth of specific features covered.

Dimension	Reasoning	Score
Specificity	The description lists numerous specific concrete actions: designing 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	Clearly answers both 'what' (design, review, improve REST APIs with extensive list of capabilities) and 'when' with an explicit 'Use when...' clause at the start and a 'This should trigger for requests such as...' section providing concrete example triggers.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'REST API', 'Quarkus', 'JAX-RS', 'pagination', 'sorting', 'ETag', 'idempotency', 'API versioning', 'error handling', 'validation', 'OpenAPI', 'HTTP caching', 'deprecation headers', 'RFC 7807'. These are terms developers would naturally use when requesting help with these topics.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: Quarkus REST/Jakarta REST API design with very specific technical features. The combination of Quarkus-specific context plus detailed API design patterns (ETag, Idempotency-Key, 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 functions primarily as a thin wrapper around an external reference file, providing almost no actionable content in the body itself. The workflow is structured but vague, and the complete absence of code examples, concrete patterns, or copy-paste-ready snippets means Claude would need to read the entire reference file before doing anything useful. The constraints section has good safety intent but is redundantly stated.

Suggestions

Add at least 2-3 concrete, executable code examples inline (e.g., a minimal JAX-RS resource class, an ExceptionMapper for RFC 7807, a pagination DTO) so the skill provides immediate actionable value without requiring the reference file.

Consolidate the constraints section — the five bullets about compilation can be reduced to one clear rule: 'Run `./mvnw compile` before changes; if it fails, stop. Run `./mvnw clean verify` after changes.'

Replace the 'What is covered' bullet list with a quick-start example showing a complete minimal REST resource with validation and error handling, which would be far more useful than a topic listing.

Make workflow steps more specific — e.g., step 3 should mention specific files to create/modify (resource classes, exception mappers, DTOs) rather than the generic 'implement or refactor following reference patterns.'

Dimension	Reasoning	Score
Conciseness	The 'What is covered' bullet list is essentially a table of contents that restates the description and doesn't add actionable value. The constraints section is repetitive (multiple bullets saying 'compile first'). However, the overall structure is reasonably tight and doesn't over-explain concepts Claude already knows.	2 / 3
Actionability	The skill contains no concrete code examples, no executable commands beyond generic mvnw invocations, and no specific patterns or snippets. All actual guidance is deferred to the reference file. The body describes rather than instructs — it tells Claude to 'follow the reference patterns' without showing any.	1 / 3
Workflow Clarity	The workflow has a clear 4-step sequence with a pre-compilation check and post-verification step, which is good. However, the steps are vague ('apply framework-aligned changes', 'gather scope') and lack explicit validation checkpoints or error recovery loops between steps. The constraints section mentions stopping on compilation failure, which partially compensates.	2 / 3
Progressive Disclosure	The skill correctly references a single external file (references/402-frameworks-quarkus-rest.md) for detailed content, which is good one-level-deep disclosure. However, since no bundle files were provided, we cannot verify the reference exists or is well-structured. The SKILL.md itself provides almost no standalone value — it's essentially just a pointer to the reference file with no quick-start content.	2 / 3
	Total	7 / 12 Passed

Validation

100%

Warnings & errors only

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: ef4eba3

Reviewed: about 5 hours ago

Table of Contents

Discovery Implementation Validation

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.