412-frameworks-quarkus-panache

Use when you need data access with Quarkus Hibernate ORM Panache — including PanacheEntity / PanacheEntityBase, PanacheRepository, named queries, JPQL, native SQL, DTO projections (project(Class)), pagination (Page.of()), N+1 avoidance (JOIN FETCH), optimistic locking (@Version / OptimisticLockException), @NamedQuery for validated reusable queries, transactions, @TestTransaction for test isolation, and immutable-friendly patterns. This is the Quarkus analogue to Spring Data for relational persistence. This should trigger for requests such as Review Panache entities or repositories in Quarkus; Improve Hibernate ORM data access with Panache; Add DTO projections, JOIN FETCH, pagination, or optimistic locking to Panache queries; Fix N+1 query problems or add @Version concurrency control in Quarkus Panache; Improve Panache active record versus repository design. Part of Plinth Toolkit

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/412-frameworks-quarkus-panache/SKILL.md

Quality

Content

70%

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

A well-structured overview with clear validation-gated workflow and clean one-level progressive disclosure; it is held back by repetitive constraints and implementation guidance that is abstract rather than executable inline.

Suggestions

Collapse the redundant compile/stop constraints (MANDATORY, PREREQUISITE, SAFETY, BLOCKING CONDITION) into a single concise checkpoint to improve token efficiency.

Remove or compress the 'When to use this skill' section since it duplicates the description's trigger list.

Add at least one short executable Panache code snippet (e.g., a PanacheRepository query or JOIN FETCH example) inline so the body is actionable without opening the reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and does not tutor Claude on what Panache/Hibernate is, but the Constraints block restates 'compile first / stop on failure' four times (MANDATORY, PREREQUISITE, SAFETY, BLOCKING CONDITION) and 'When to use this skill' duplicates the description's triggers, so it could be tightened.	2 / 3
Actionability	It gives concrete commands (./mvnw compile, mvn clean verify) and a real reference path, but the core implementation guidance is deferred to the reference and workflow step 3 ('Implement or refactor configuration/code following the reference patterns') is abstract rather than executable.	2 / 3
Workflow Clarity	The four-step workflow has an explicit sequence with concrete validation checkpoints (MANDATORY compile before, VERIFY after, SAFETY stop on failure) forming a clear validate->stop->resolve->verify feedback loop.	3 / 3
Progressive Disclosure	The body is a concise overview pointing to a single one-level-deep reference (references/412-frameworks-quarkus-panache.md, which exists), clearly signaled in both the workflow and a dedicated Reference section.	3 / 3
	Total	10 / 12 Passed

Description

90%

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, specific description with explicit trigger guidance and a clear niche; its main weakness is the second-person 'you need' voice, which violates the third-person requirement and costs a specificity point.

Suggestions

Rewrite the opening in third person / imperative voice (e.g., 'Use when working with Quarkus Hibernate ORM Panache data access...') to avoid the second-person 'you need' phrasing.

Consider trimming the long capability enumeration slightly so the description stays scannable rather than padded.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities (PanacheEntity, PanacheRepository, JPQL, DTO projections via project(Class), Page.of(), JOIN FETCH, @Version/OptimisticLockException, @TestTransaction), which would merit a 3, but the second-person phrasing 'Use when you need data access' triggers the voice penalty reducing specificity by 1.	2 / 3
Completeness	It explicitly answers both 'what' (data access with Panache across the enumerated capabilities) and 'when' via an explicit 'Use when...' clause plus a concrete trigger-request list.	3 / 3
Trigger Term Quality	The 'should trigger for requests such as Review Panache entities..., Improve Hibernate ORM data access with Panache, Fix N+1 query problems or add @Version concurrency control' phrases are natural requests a user would actually say, giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	The 'Quarkus Hibernate ORM Panache' niche and the 'Quarkus analogue to Spring Data for relational persistence' framing give it a clear, distinct scope unlikely to trigger for the wrong skill.	3 / 3
	Total	11 / 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/412-frameworks-quarkus-panache/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.