412-frameworks-quarkus-panache
Use when you need data access with Quarkus Hibernate ORM Panache — including PanacheEntity / PanacheEntityBase, PanacheRepository, named and HQL queries, 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
88
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
85%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 with excellent specificity and completeness. It clearly defines the technology niche (Quarkus Hibernate ORM Panache) and provides comprehensive coverage of capabilities. The main weakness is that trigger terms are heavily technical, which may miss users who describe their needs in more natural language like 'database access' or 'save data'.
Suggestions
Add natural language trigger terms that users might say, such as 'database queries', 'data persistence', 'CRUD operations', or 'save/retrieve data' alongside the technical terms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and patterns: PanacheEntity/PanacheEntityBase, PanacheRepository, named and HQL queries, DTO projections, pagination, N+1 avoidance with JOIN FETCH, optimistic locking, @NamedQuery, transactions, and @TestTransaction. | 3 / 3 |
Completeness | Explicitly starts with 'Use when you need data access with Quarkus Hibernate ORM Panache' providing clear trigger guidance, then comprehensively lists what it does. Both 'what' and 'when' are clearly addressed. | 3 / 3 |
Trigger Term Quality | Includes technical terms like 'Quarkus', 'Hibernate ORM', 'Panache', 'PanacheEntity', but these are developer jargon. Missing natural phrases users might say like 'database queries', 'save to database', 'CRUD operations', or 'data persistence'. | 2 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology stack (Quarkus + Hibernate ORM + Panache) and explicit comparison to Spring Data. Very unlikely to conflict with other skills due to the narrow, well-defined niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates excellent structure and progressive disclosure, with a clear workflow including validation checkpoints. The main weakness is the lack of concrete code examples in the skill body itself - all actionable code is deferred to the reference file, which reduces immediate actionability for common operations.
Suggestions
Add 1-2 minimal executable code examples for the most common patterns (e.g., PanacheEntity with a simple query, or a DTO projection example) to improve immediate actionability
Include a quick-start code snippet showing the basic Panache entity pattern before directing to the reference file
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using bullet points to list capabilities without explaining what Hibernate or Panache are. Every line serves a purpose - no padding or concepts Claude would already know. | 3 / 3 |
Actionability | The skill provides clear constraints and workflow steps (compile before, verify after), but lacks concrete code examples. All executable guidance is deferred to the reference file rather than providing copy-paste ready snippets. | 2 / 3 |
Workflow Clarity | Clear sequence with explicit validation checkpoints: compile before changes, stop if compilation fails, verify after applying improvements. Includes blocking conditions and safety gates for error recovery. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, clear 'When to use' section, and a single well-signaled reference to the detailed guidance file. One level deep, easy navigation. | 3 / 3 |
Total | 11 / 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
b36efb2
- 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.