411-frameworks-quarkus-jdbc

Use when you need programmatic JDBC in Quarkus — Agroal DataSource, parameterized SQL, transactions, batching, and Dev Services. This should trigger for requests such as Review JDBC or SQL data access in a Quarkus project; Improve transactions and parameter binding for Quarkus JDBC; Translate SQLException to domain exceptions or stream large result sets; Fix CDI self-invocation bypassing @Transactional in Quarkus; Review Agroal DataSource usage in Quarkus JDBC. Part of Plinth Toolkit

Quality

83%

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

Quality

Content

71%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.

Well-structured body with strong progressive disclosure and a validation-backed workflow, but actionability is capped at 3 because executable JDBC code lives only in the reference rather than inline, and there is minor redundancy across sections.

Suggestions

Inline 1-2 short, copy-paste JDBC snippets (e.g., DataSource injection with try-with-resources PreparedStatement, and a parameterized query) so the body is actionable without forcing a reference read for the common cases.

De-duplicate: drop the standalone 'When to use this skill' section (it restates the frontmatter triggers) or merge it into the opening summary.

Fold the validation checkpoints into the numbered workflow steps (e.g., step 1: compile; step 4: verify-and-report) instead of keeping them only in the separate Constraints section.

Dimension	Reasoning	Score
Conciseness	Lean body that does not explain concepts Claude already knows (no 'what is JDBC/Quarkus' padding), but has minor redundancy: the 'When to use this skill' section repeats trigger phrases already in the frontmatter, and Constraints restates 'compile before applying' across MANDATORY/PREREQUISITE/BEFORE APPLYING bullets.	4 / 5
Actionability	Provides concrete commands for verification ('./mvnw compile', 'mvn clean verify') and names specific patterns (try-with-resources, setFetchSize, addBatch/executeBatch, TxType.REQUIRES_NEW), but the core JDBC guidance is only described, not shown as executable code in the body — all code examples are delegated to the reference file, leaving key details inline-incomplete.	3 / 5
Workflow Clarity	Clear 4-step sequence with explicit validation checkpoints (compile before, verify after, 'SAFETY: stop immediately' on failure, 'BLOCKING CONDITION' requiring user resolution); not a 5 because the workflow steps themselves are somewhat generic ('Gather scope', 'Apply framework-aligned changes') and the checkpoints live in a separate Constraints section rather than inline in the steps.	4 / 5
Progressive Disclosure	Clear overview in SKILL.md with a single well-signaled, one-level-deep reference link to references/411-frameworks-quarkus-jdbc.md (verified to exist, 31KB); content is appropriately split between overview and detailed reference with easy navigation.	5 / 5
	Total	16 / 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, comprehensive description with explicit what/when structure and natural trigger phrases scoped tightly to Quarkus JDBC. The only ding is second-person voice ('you need'), which costs one specificity point per the rubric.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Agroal DataSource, parameterized SQL, transactions, batching, and Dev Services') plus specific trigger tasks like 'Translate SQLException to domain exceptions' and 'Fix CDI self-invocation bypassing @Transactional', giving comprehensive coverage; reduced from 5 because the phrase 'Use when you need' uses second-person voice, which the rubric penalizes by one point on specificity.	4 / 5
Completeness	Explicitly answers both what ('programmatic JDBC in Quarkus — Agroal DataSource, parameterized SQL, transactions, batching, and Dev Services') and when ('Use when you need... This should trigger for requests such as...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases a user would say are comprehensively covered — 'Review JDBC or SQL data access in a Quarkus project', 'Improve transactions and parameter binding', 'stream large result sets', 'Review Agroal DataSource usage' — including synonyms and specific framework terms.	5 / 5
Distinctiveness Conflict Risk	Clear niche scoped to Quarkus JDBC with distinct triggers (Agroal, @Transactional, CDI self-invocation, Dev Services) and minimal overlap risk with 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/411-frameworks-quarkus-jdbc/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours 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.