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 rich natural trigger terms, and explicitly addresses both what the skill does and when it should be used. The description is comprehensive without being vague, listing concrete actions and technologies. The only minor concern is that the description is quite long, which could be slightly more concise, but the density of useful information justifies the length.

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 due to the specific Quarkus REST / Jakarta REST niche combined with very specific technical features like Idempotency-Key, ETag/If-Match, Sunset/Deprecation headers, and RFC 7807. Unlikely to conflict with generic API or Java skills due to the precise technology and feature scope.	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 acts primarily as a pointer to a reference file rather than providing standalone actionable guidance. It lacks any concrete code examples, specific patterns, or executable snippets — all substance is deferred to the reference. The workflow is reasonably structured but generic, and the content includes redundant topic listings that consume tokens without adding value.

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 guidance 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; run `./mvnw clean verify` after. Stop if either fails.'

Remove or significantly trim the 'What is covered' bullet list since it duplicates the reference file's content and the skill description; replace it with a brief one-liner like 'Covers REST resource design, validation, error handling, versioning, caching, and concurrency patterns.'

Add specific validation checkpoints within the workflow steps, such as 'After adding an ExceptionMapper, verify with `curl -v` that error responses return application/problem+json content type.'

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, it's not excessively verbose — it avoids explaining what REST or JAX-RS is.	2 / 3
Actionability	There are no concrete code examples, no executable commands beyond generic 'mvnw compile', no specific patterns, DTOs, or resource class snippets. Everything actionable is deferred to the reference file. The skill body describes rather than instructs.	1 / 3
Workflow Clarity	The workflow has a clear 4-step sequence with a verification step at the end and a pre-check compilation step. However, the steps are generic ('apply framework-aligned changes') with no specific validation checkpoints between steps, and the error recovery feedback loop is minimal ('stop immediately' if compilation fails, but no guidance on what to do next).	2 / 3
Progressive Disclosure	There is a clear reference to a single detailed file (references/402-frameworks-quarkus-rest.md), which is good one-level-deep disclosure. However, no bundle files were provided to verify the reference exists, and the SKILL.md itself contains a long bullet list of topics that could have been omitted since they're presumably covered in the reference. The overview doesn't provide enough standalone value.	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: 3fa5789

Reviewed: 3 days 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.