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
74
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/412-frameworks-quarkus-panache/SKILL.mdQuality
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 about these topics. | 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 is essentially a thin wrapper around a reference file, providing almost no actionable content in the body itself. While it has reasonable structure and a clear compilation safety gate, it lacks any concrete code examples, specific patterns, or executable guidance — everything substantive is deferred to the reference. The bullet list of topics covered is informational but doesn't teach Claude anything actionable.
Suggestions
Add at least 2-3 concrete, executable code examples directly in the SKILL.md body — e.g., a PanacheEntity with @Version, a JOIN FETCH query, and a DTO projection with project(Class) — so Claude has actionable patterns without needing to read the reference file.
Replace the generic workflow steps ('Apply framework-aligned changes') with specific decision trees or checklists, e.g., 'If N+1 detected: add JOIN FETCH to the JPQL query; If exposing entity at REST boundary: create DTO and use project(DtoClass)'.
Consolidate the constraints section — the 6 bullets about compilation can be reduced to 2 lines: 'PREREQUISITE: Project must compile (`./mvnw compile`) before changes. VERIFY: Run `./mvnw clean verify` after changes. Stop if either fails.'
Include a minimal good/bad code comparison inline (e.g., unsafe string concatenation vs parameterized query) to make the skill immediately useful without requiring the reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list is somewhat verbose and reads like a table of contents for the reference file rather than actionable content. The constraints section repeats the same 'compile before/after' idea in 6 different bullet points. However, it avoids explaining what Panache or Hibernate is, which shows some respect for Claude's knowledge. | 2 / 3 |
Actionability | There are no concrete code examples, no executable commands beyond generic 'mvnw compile', no specific patterns shown. Everything is deferred to the reference file. The skill body describes what to do abstractly ('Apply framework-aligned changes') without showing how. | 1 / 3 |
Workflow Clarity | The workflow has a clear 4-step sequence with a compilation prerequisite and post-verification step, which is good. However, the steps are generic ('Gather scope', 'Apply framework-aligned changes') and lack specific validation checkpoints for the persistence-specific operations described (e.g., no guidance on verifying N+1 fixes, checking optimistic locking behavior). The constraints section does include a compile-before/verify-after pattern. | 2 / 3 |
Progressive Disclosure | The skill correctly references a single external file (references/412-frameworks-quarkus-panache.md) for detailed guidance, which is good one-level-deep disclosure. However, since no bundle files were provided, we can't verify the reference exists. The main issue is that the SKILL.md itself contains almost no substantive content — it's essentially just a pointer to the reference file with a generic workflow wrapper, making the skill body itself too thin to be useful as an overview. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
100%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
ef4eba3
- Reviewed
Table of Contents
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.