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

79%

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

63%Weight 40%Scale 1-5

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 that delegates detail to a single clearly-signaled reference and enforces compile/verify validation gates. Its weaknesses are duplicated trigger phrasing and over-labeled constraints, plus the absence of any executable Panache code examples in the body itself.

Suggestions

Remove the 'When to use this skill' section or replace it with a one-line pointer, since its bullets duplicate the description's trigger phrases and inflate the token budget.

Collapse the six tagged Constraint lines (MANDATORY/PREREQUISITE/SAFETY/BLOCKING CONDITION/VERIFY/BEFORE APPLYING) into two concrete rules: compile before, verify after.

Add 1-2 short inline code snippets (e.g., a PanacheRepository with @NamedQuery or a JOIN FETCH JPQL query) so the body is actionable without requiring a round-trip to the reference.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and free of basic-concept padding, but the 'When to use this skill' section duplicates triggers already in the description and the Constraints block over-labels (MANDATORY/PREREQUISITE/SAFETY/BLOCKING CONDITION/VERIFY/BEFORE APPLYING) for essentially two rules, so it could be tightened.	3 / 5
Actionability	Concrete build commands (./mvnw compile, mvn clean verify) and named APIs (Page.of(), project(Class), JOIN FETCH) are present, but the body contains no executable Panache code examples — all substantive implementation guidance is delegated to the reference, leaving key details missing here.	3 / 5
Workflow Clarity	A clear 4-step sequence with explicit validation checkpoints (compile before applying, stop on failure, verify after), but the fix-and-retry loop is only a gate ('stop immediately', 'resolved by the user') rather than an explicit re-validate loop, a minor gap.	4 / 5
Progressive Disclosure	The body is a well-organized overview with clearly signaled, one-level-deep navigation to a single real reference file (references/412-frameworks-quarkus-panache.md), with bulk detail appropriately split out and easy to navigate.	5 / 5
	Total	15 / 20 Passed

Description

95%Weight 40%Scale 1-5

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 comprehensive capability coverage and natural trigger phrases that clearly answer both what and when. Its only weakness is second-person voice ('Use when you need'), which the rubric penalizes on specificity.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities (PanacheEntity/PanacheEntityBase, PanacheRepository, project(Class), Page.of(), JOIN FETCH, @Version/OptimisticLockException, @NamedQuery, @TestTransaction) which is comprehensive, but the second-person phrasing 'Use when you need data access' triggers the rubric's -1 voice penalty from a 5.	4 / 5
Completeness	Explicitly answers both what (data access with Quarkus Hibernate ORM Panache, listing the concrete features) and when ('This should trigger for requests such as...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user phrasings are comprehensively enumerated — 'Review Panache entities or repositories in Quarkus', 'Fix N+1 query problems', 'Improve Panache active record versus repository design' — covering the synonyms a user would actually say.	5 / 5
Distinctiveness Conflict Risk	Scoped tightly to Quarkus Hibernate ORM Panache and framed as 'the Quarkus analogue to Spring Data', giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	19 / 20 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/plinth
Path: skills/412-frameworks-quarkus-panache/SKILL.md
Commit: 05bf9d1

Reviewed: 9 minutes 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.