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. Part of the skills-for-java project
74
67%
Does it follow best practices?
Impact
Pending
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 a strong skill description that excels across all dimensions. It opens with an explicit 'Use when' trigger clause, enumerates a comprehensive list of specific capabilities with concrete API references, and occupies a clearly distinct niche (Quarkus Panache ORM). The inclusion of both high-level concepts (transactions, pagination) and specific API details (Page.of(), project(Class), @TestTransaction) makes it highly effective for skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | 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, transactions, @TestTransaction, and immutable-friendly patterns. | 3 / 3 |
Completeness | Starts with an explicit 'Use when' clause that clearly defines when Claude should select this skill, and the extensive list of capabilities thoroughly answers 'what does this do'. Both dimensions are well covered. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a developer would use: 'Hibernate ORM', 'Panache', 'PanacheEntity', 'PanacheRepository', 'JPQL', 'native SQL', 'DTO projections', 'pagination', 'N+1', 'JOIN FETCH', 'optimistic locking', '@Version', 'transactions', '@TestTransaction', 'Quarkus', 'relational persistence', and the Spring Data comparison helps with discoverability. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific niche (Quarkus Hibernate ORM Panache for relational persistence) with domain-specific triggers like PanacheEntity, PanacheRepository, and Panache-specific APIs. The comparison to Spring Data further clarifies its scope and distinguishes it from a potential Spring Data skill. | 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 table of contents with a compilation safety checklist that delegates all substantive content to a reference file. It lacks any concrete code examples, executable commands beyond generic Maven invocations, or actionable patterns that Claude could immediately apply. The structure is reasonable but the body provides almost no standalone value without the reference file.
Suggestions
Add at least 2-3 concrete, executable code examples inline (e.g., a PanacheEntity with @Version, a DTO projection with project(Class), a JOIN FETCH query) so the skill has standalone value without requiring the reference file.
Convert the constraints section into a numbered workflow sequence: 1. Compile → 2. Apply changes → 3. Validate → 4. If errors, fix and re-validate, to improve workflow clarity.
Remove the 'What is covered' bullet list or condense it to 2-3 lines — it reads like a syllabus rather than actionable guidance, and the topics are better demonstrated through examples.
Add a 'Quick start' section with a minimal but complete Panache entity + repository example showing the most common pattern, so Claude can act immediately.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bullet list of covered topics is somewhat verbose and reads like a table of contents rather than actionable content. The constraints section repeats similar ideas (compile before, stop if fails) in multiple bullet points. However, it doesn't over-explain concepts Claude already knows. | 2 / 3 |
Actionability | There is no executable code, no concrete examples, no specific commands beyond generic mvnw compile/verify. The entire skill delegates to a reference file for 'detailed rules and examples,' leaving the SKILL.md itself as a vague pointer with no copy-paste-ready guidance. | 1 / 3 |
Workflow Clarity | There is a compile-before/verify-after workflow with a stop condition on failure, which is good. However, the validation steps are listed as unordered bullet points rather than a clear numbered sequence, and there's no feedback loop for fixing issues — it just says 'stop immediately' and 'resolved by the user.' | 2 / 3 |
Progressive Disclosure | There is a single reference file linked at the bottom, which is good one-level-deep disclosure. However, the SKILL.md itself contains almost no substantive content — it's essentially just a topic list and a pointer, meaning the split is too aggressive. The overview should contain at least a quick-start example or key pattern. | 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
1847adc
- 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.