CtrlK
BlogDocsLog inGet started
Tessl Logo

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

69

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured with a clear, validated workflow and clean progressive disclosure to a single reference file. Its main weaknesses are mild redundancy in the Constraints and When-to-use sections and a reliance on the reference for concrete, executable implementation guidance.

Suggestions

Collapse the repetitive Constraints bullets (MANDATORY/PREREQUISITE/SAFETY/BLOCKING CONDITION) into a single 'Compile before changes; stop and surface errors if compilation fails; run clean verify after' statement to tighten conciseness.

Drop the 'When to use this skill' list since it duplicates the description's triggers, or replace it with a one-line pointer back to the description.

Add at least one small executable code snippet (e.g., a PanacheRepository or PanacheEntity query example) in the body so the skill gives concrete guidance without forcing a reference read for common cases.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the Constraints block restates the compile-before idea across MANDATORY/PREREQUISITE/SAFETY/BLOCKING CONDITION bullets, and the 'When to use this skill' section duplicates triggers already in the description, so it could be tightened.

2 / 3

Actionability

It provides concrete commands ('./mvnw compile', './mvnw clean verify') but the workflow steps are abstract ('Implement or refactor configuration/code following the reference patterns') and defer real executable guidance to the reference file, leaving the body itself incomplete.

2 / 3

Workflow Clarity

The 4-step workflow is clearly sequenced with explicit validation checkpoints (compile before, verify after) and a stop-on-failure feedback loop ('If compilation fails, stop immediately'), matching the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

The body is an overview that points to a single one-level-deep reference (references/412-frameworks-quarkus-panache.md, verified present), signaled in both the Workflow and Reference sections, with content appropriately split.

3 / 3

Total

10

/

12

Passed

Description

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.

The description is comprehensive, specific, and well-triggered: it lists concrete Panache capabilities and pairs them with natural user-facing trigger phrases. It clearly answers both what the skill does and when to use it with low conflict risk.

DimensionReasoningScore

Specificity

The description enumerates concrete capabilities — 'PanacheEntity / PanacheEntityBase, PanacheRepository, named queries, JPQL, native SQL, DTO projections (project(Class)), pagination (Page.of()), N+1 avoidance (JOIN FETCH), optimistic locking (@Version / OptimisticLockException)' — matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It answers both 'what' (the enumerated Panache data-access capabilities) and 'when' via an explicit 'Use when you need...' clause and a 'This should trigger for requests such as...' list, clearing the explicit-trigger bar.

3 / 3

Trigger Term Quality

Phrases like 'Review Panache entities or repositories in Quarkus', 'Fix N+1 query problems', and 'Improve Panache active record versus repository design' are natural user requests, giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

It is sharply scoped to 'Quarkus Hibernate ORM Panache' and tagged 'Part of Plinth Toolkit', giving it a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jabrena/plinth
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.