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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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 with a clear, validated workflow and clean one-level-deep progressive disclosure; it loses points on conciseness (redundant constraints and duplicated triggers) and actionability (no executable JDBC code in the body itself, only in the reference).

Suggestions

Collapse the four overlapping compile-first constraint bullets into a single 'Compile before changes; stop if it fails' rule plus the post-change verify step to remove redundancy.

Drop or shorten the 'When to use this skill' section since it restates the description's triggers verbatim, or cross-reference it instead of repeating.

Add one small executable JDBC snippet (e.g. a try-with-resources PreparedStatement with bind parameters) inline so the body is actionable without forcing a reference read for the core pattern.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations, but the Constraints section restates 'compile before changes' four ways (MANDATORY/PREREQUISITE/SAFETY/BLOCKING CONDITION) and the 'When to use this skill' section duplicates the description's triggers verbatim, so not every token earns its place.	2 / 3
Actionability	Concrete build commands are present ('./mvnw compile', 'mvn clean verify'), but the JDBC code patterns are only named (e.g. 'PreparedStatement with bind parameters', 'addBatch / executeBatch') with all executable code deferred to the reference, and 'Implement… following the reference patterns' is vague direction.	2 / 3
Workflow Clarity	The four-step workflow is clearly sequenced with explicit validation checkpoints — 'Run ./mvnw compile before applying any change', 'If compilation fails, stop immediately', and 'Run ./mvnw clean verify' after — forming a compile/verify feedback loop, so the batch/destructive cap does not apply.	3 / 3
Progressive Disclosure	The body is a concise overview pointing to a single one-level-deep reference (references/411-frameworks-quarkus-jdbc.md, verified to exist), clearly signaled in both the '## Reference' section and workflow step 1, with well-organized sections.	3 / 3
	Total	10 / 12 Passed

Description

90%

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, well-scoped description with explicit what/when triggers and good natural trigger terms; its only real weakness is the second-person voice ('you need'), which costs it a specificity point.

Suggestions

Rewrite the description in third person (e.g. 'Provides programmatic JDBC in Quarkus…') to avoid the second-person voice penalty on specificity.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Agroal DataSource, parameterized SQL, transactions, batching, and Dev Services' plus SQLException translation, streaming, CDI self-invocation) which would be a 3, but the second-person voice ('Use when you need…') triggers the −1 specificity penalty per the guidelines.	2 / 3
Completeness	It states both what the skill does ('programmatic JDBC in Quarkus — Agroal DataSource, parameterized SQL, transactions, batching, and Dev Services') and explicit when-to-use triggers ('Use when…', 'This should trigger for requests such as…').	3 / 3
Trigger Term Quality	Phrases like 'Review JDBC or SQL data access in a Quarkus project', 'Improve transactions and parameter binding', 'Translate SQLException… or stream large result sets', and 'Review Agroal DataSource usage' are natural terms a Quarkus developer would actually say.	3 / 3
Distinctiveness Conflict Risk	A clear Quarkus-JDBC niche with distinct triggers, and it even disambiguates from the Panache skill ('When to prefer Panache (@412) vs raw JDBC'), making wrong-skill triggering unlikely.	3 / 3
	Total	11 / 12 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
Commit: aaee915

Reviewed: 1 day 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.