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. 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/412-frameworks-quarkus-panache/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, includes abundant natural trigger terms, explicitly addresses both what and when, and occupies a clearly distinct niche. The description is comprehensive and well-structured, though it is quite dense and could benefit from slightly more concise formatting. It follows third-person voice conventions appropriately.

Dimension	Reasoning	Score
Specificity	The description lists numerous specific concrete actions and patterns: PanacheEntity/PanacheEntityBase, PanacheRepository, named queries, JPQL, native SQL, DTO projections with project(Class), pagination with Page.of(), N+1 avoidance with JOIN FETCH, optimistic locking with @Version, @NamedQuery, transactions, @TestTransaction, and immutable-friendly patterns.	3 / 3
Completeness	The description clearly answers both 'what' (data access with Quarkus Hibernate ORM Panache including a comprehensive list of capabilities) and 'when' (explicit 'Use when' clause at the start, plus a 'This should trigger for requests such as...' section with concrete example requests).	3 / 3
Trigger Term Quality	Excellent coverage of natural terms a user would say: 'Panache', 'Hibernate ORM', 'Quarkus', 'DTO projections', 'JOIN FETCH', 'pagination', 'optimistic locking', 'N+1', '@Version', 'PanacheEntity', 'PanacheRepository', 'native SQL', 'JPQL'. These are exactly the terms a developer would use when asking for help with Quarkus data access.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — it targets a very specific niche (Quarkus Hibernate ORM Panache for relational persistence) with domain-specific triggers like 'Panache', 'PanacheEntity', 'PanacheRepository', and Quarkus-specific annotations. The comparison to Spring Data further clarifies its scope. 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 table of contents and pointer to an external reference file, with almost no actionable content in the body itself. While the structure is reasonable and constraints are clearly stated, the complete absence of code examples for any of the listed patterns (PanacheEntity, projections, pagination, JOIN FETCH, optimistic locking) makes it difficult for Claude to act on without reading the external reference. The workflow steps are too generic to provide meaningful guidance.

Suggestions

Add at least 2-3 concrete, executable code examples inline for the most common patterns (e.g., PanacheEntity definition, DTO projection with project(Class), JOIN FETCH query) so the skill is actionable without requiring the external reference.

Consolidate the redundant constraint entries (MANDATORY, PREREQUISITE, SAFETY, BLOCKING CONDITION all say 'must compile first') into a single clear pre/post check instruction.

Make workflow step 3 specific: instead of 'Apply framework-aligned changes', list the concrete patterns to check/apply (e.g., 'Replace string-concatenated queries with parameterized JPQL', 'Add @Version to entities lacking optimistic locking').

Add a brief good/bad code comparison for at least one anti-pattern (e.g., unsafe query concatenation vs parameterized query) to make the skill self-contained for common cases.

Dimension	Reasoning	Score
Conciseness	The 'What is covered' bullet list is somewhat verbose and partially redundant with the 'When to use this skill' section. The constraints section repeats the compilation check idea multiple times with different bold labels (MANDATORY, PREREQUISITE, SAFETY, BLOCKING CONDITION) which is redundant. However, it doesn't over-explain concepts Claude already knows.	2 / 3
Actionability	The skill contains no concrete code examples, no executable commands beyond generic mvnw compile/verify, and delegates all actual guidance to an external reference file. There is no copy-paste ready code for any of the listed patterns (PanacheEntity, projections, pagination, JOIN FETCH, etc.).	1 / 3
Workflow Clarity	The workflow has a clear 4-step sequence with a verification step at the end and compilation checks before starting. However, the steps are generic ('apply framework-aligned changes') rather than specific, and there's no explicit feedback loop for what to do if verification fails beyond the pre-check compilation constraint.	2 / 3
Progressive Disclosure	The skill references a single external file (references/412-frameworks-quarkus-panache.md) which is one level deep and clearly signaled. However, since no bundle files were provided, we can't verify the reference exists, and the SKILL.md itself contains almost no actionable content — it's essentially just a pointer to the reference file with a table of contents, which means too little is inline.	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: 2 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.