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; Improve Quarkus REST resources and exception mappers. Part of Plinth Toolkit

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, token-efficient overview with strong validation checkpoints and clean one-level progressive disclosure to a real reference file. Its main weakness is actionability: the body relies on concrete build commands but delegates all REST-specific implementation guidance to the reference without inline examples.

Suggestions

Add one short inline code snippet showing a canonical Quarkus REST resource pattern (e.g., a @Path class with @GET, Bean Validation, and an RFC 7807 ExceptionMapper) so the body is actionable without forcing a reference read for common cases.

Tighten the overlap between the 'What is covered in this Skill?' list and the description's capability list to avoid restating the same enumeration twice.

Make workflow step 3 ('Apply framework-aligned changes') more concrete by naming the specific reference subsections to consult per change type (e.g., 'see exception mappers section for error-handling changes').

Dimension	Reasoning	Score
Conciseness	The body is lean: a bulleted coverage summary, a constraints block with concrete commands, a short 4-step workflow, and a single reference link, with no padding explaining concepts Claude already knows. Minor redundancy between the coverage list and the description does not materially inflate it.	3 / 3
Actionability	It gives concrete build/verify commands ('./mvnw compile', 'mvn clean verify') but the core REST implementation guidance is abstract and deferred — 'Implement or refactor configuration/code following the reference patterns' — with no executable code or specific patterns in-body.	2 / 3
Workflow Clarity	The 4-step workflow is clearly sequenced and bracketed by explicit validation checkpoints: 'MANDATORY: Run mvn compile before applying any change', 'SAFETY: If compilation fails, stop immediately', and 'VERIFY: Run mvn clean verify after applying improvements'.	3 / 3
Progressive Disclosure	The SKILL.md is an overview that signals a single one-level-deep reference (references/402-frameworks-quarkus-rest.md, which exists) in both the workflow and a dedicated Reference section, keeping detail out of the main file with clear navigation.	3 / 3
	Total	11 / 12 Passed

Description

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.

A strong, third-person description that clearly states capabilities and explicit trigger conditions scoped to Quarkus REST. It is comprehensive without relying on vague fluff, though it is on the verbose side.

Dimension	Reasoning	Score
Specificity	The description lists many concrete actions and components — 'design, review, or improve REST APIs', 'resource classes, HTTP methods, status codes, request/response DTOs, Bean Validation, exception mappers', 'ETag / If-Match', 'RFC 7807 Problem Details' — going well beyond a vague domain label.	3 / 3
Completeness	It explicitly answers both what (design/review/improve Quarkus REST APIs with the enumerated capabilities) and when, opening with 'Use when you need to...' and reinforcing with 'This should trigger for requests such as...'.	3 / 3
Trigger Term Quality	It includes natural request phrasings a user would actually say — 'Review or improve JAX-RS resources in a Quarkus project', 'Add API versioning, idempotency, ETag concurrency, or deprecation headers', 'Implement pagination, sorting, or RFC 7807 Problem Details error responses' — with good coverage of common variations.	3 / 3
Distinctiveness Conflict Risk	The niche is sharply scoped to Quarkus REST (Jakarta REST) with Quarkus-specific triggers, making it unlikely to fire for non-Quarkus or non-REST skills.	3 / 3
	Total	12 / 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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Path: skills/402-frameworks-quarkus-rest/SKILL.md
Commit: fdaf68c

Reviewed: about 17 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.