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

85%

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

71%Weight 40%Scale 1-5

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

The body is a well-structured overview that cleanly delegates detail to one real reference file and includes solid compile/verify validation checkpoints. It is held back by padded constraint labels, redundant when-to-use text, and a lack of any in-body executable REST examples.

Suggestions

Collapse the Constraints section's six synonymic labels (MANDATORY/PREREQUISITE/SAFETY/BLOCKING CONDITION/VERIFY/BEFORE APPLYING) into two or three crisp rules to remove padding.

Add one small inline code example (e.g. a minimal @Path resource with @GET and an ExceptionMapper returning RFC 7807) so the body is actionable without forcing a reference round-trip.

Either drop the 'When to use this skill' list (it duplicates the frontmatter description) or replace it with a pointer, to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with no over-explanation of concepts Claude already knows, but the Constraints section pads one idea across six synonymic labels (MANDATORY, PREREQUISITE, SAFETY, BLOCKING CONDITION, VERIFY, BEFORE APPLYING) and the 'When to use' list duplicates the description's trigger phrases.	4 / 5
Actionability	Concrete build/verify commands are present, but the actual REST guidance is high-level delegation ('Implement or refactor configuration/code following the reference patterns') with no executable REST code examples in the body itself — details live only in the reference file.	3 / 5
Workflow Clarity	A clear four-step sequence with explicit validation checkpoints (compile before changes, verify after) is present, but the error path is a stop-and-hand-off ('stop immediately', 'resolved by the user') rather than a fix-and-revalidate feedback loop.	4 / 5
Progressive Disclosure	A concise overview body points to a single one-level-deep, well-signaled reference (references/402-frameworks-quarkus-rest.md, verified present) via both a dedicated Reference section and Workflow step 1; content is appropriately split.	5 / 5
	Total	16 / 20 Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is highly specific, comprehensive, and explicitly pairs a clear 'what' with concrete 'when' trigger phrases, all scoped to a distinct Quarkus REST niche. Its only weakness is verbosity — it is one long padded sentence — but no dimension in this rubric penalizes length.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions (design, review, improve REST APIs) plus a comprehensive feature inventory (resource classes, HTTP methods, DTOs, Bean Validation, exception mappers, ETag/If-Match, RFC 7807, Sunset/Deprecation, etc.), matching the 'comprehensive coverage' anchor.	5 / 5
Completeness	Explicitly answers both what (the feature/action inventory) and when ('Use when you need to...', 'This should trigger for requests such as...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases users would actually say ('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...') with synonyms (Quarkus REST / Jakarta REST / JAX-RS).	5 / 5
Distinctiveness Conflict Risk	Scoped tightly to Quarkus REST / Jakarta REST with framework-specific triggers (SmallRye, @RunOnVirtualThread, Idempotency-Key), giving a clear niche with minimal conflict risk against generic API skills.	5 / 5
	Total	20 / 20 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/plinth
Path: skills/402-frameworks-quarkus-rest/SKILL.md
Commit: 77b8825

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