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. Part of cursor-rules-java project

Quality

67%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/411-frameworks-quarkus-jdbc/SKILL.md

Quality

Discovery

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.

This is a strong skill description that clearly defines its scope (programmatic JDBC in Quarkus), lists concrete capabilities, and provides explicit trigger guidance with realistic example requests. The description is well-targeted to its niche and uses natural developer terminology that would facilitate accurate skill selection.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: Agroal DataSource usage, parameterized SQL, transactions, batching, Dev Services, translating SQLException to domain exceptions, streaming large result sets, fixing CDI self-invocation bypassing @Transactional.	3 / 3
Completeness	Clearly answers both 'what' (programmatic JDBC in Quarkus with Agroal DataSource, parameterized SQL, transactions, batching, Dev Services) and 'when' (explicit 'Use when' clause at the start, plus 'This should trigger for requests such as...' with concrete example scenarios).	3 / 3
Trigger Term Quality	Excellent coverage of natural terms a user would say: 'JDBC', 'SQL', 'Quarkus', 'transactions', 'parameter binding', 'SQLException', 'DataSource', '@Transactional', 'CDI', 'result sets', 'batching'. These are all terms a developer would naturally use when seeking help with JDBC in Quarkus.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive niche: specifically Quarkus JDBC with Agroal, not generic database access or ORM. The combination of Quarkus + JDBC + Agroal + specific patterns like CDI self-invocation makes it very unlikely to conflict with other skills (e.g., a Hibernate/Panache skill or a generic SQL skill).	3 / 3
	Total	12 / 12 Passed

Implementation

35%

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

This skill functions primarily as a thin wrapper around a reference file, providing almost no standalone actionable content. The bullet list of topics covered is informative but not executable, and the workflow steps are generic enough to apply to any Quarkus skill. The constraints section appropriately emphasizes compilation safety but is repetitively stated.

Suggestions

Add at least 2-3 concrete, executable code examples inline (e.g., DataSource injection with try-with-resources, PreparedStatement with bind parameters, and the CDI self-invocation fix) so the skill is actionable without reading the reference file.

Replace the generic workflow steps ('Apply framework-aligned changes') with JDBC-specific actions, e.g., 'Check for string-concatenated SQL and replace with PreparedStatement bind parameters' with before/after code snippets.

Consolidate the five redundant constraint bullets about compilation into a single clear statement, e.g., '**Pre/post check**: Run `./mvnw compile` before changes and `./mvnw clean verify` after. Stop if compilation fails.'

Dimension	Reasoning	Score
Conciseness	The 'What is covered' bullet list is somewhat verbose and reads like a table of contents for the reference file rather than actionable content. The constraints section repeats the same 'compile before/after' idea in five different bullet points. However, it doesn't over-explain concepts Claude already knows.	2 / 3
Actionability	The skill contains no executable code, no concrete commands beyond generic './mvnw compile', no code examples, and no specific patterns. All actual guidance is deferred to the reference file. The body describes what to do abstractly ('Apply framework-aligned changes') without showing how.	1 / 3
Workflow Clarity	The workflow has four numbered steps with a clear sequence, and the constraints section includes validation checkpoints (compile before, verify after). However, the steps are generic ('Gather scope', 'Apply framework-aligned changes') rather than specific to JDBC operations, and there's no feedback loop for handling verification failures beyond 'stop immediately'.	2 / 3
Progressive Disclosure	The skill correctly references a single external file (references/411-frameworks-quarkus-jdbc.md) for detailed content, which is good one-level-deep disclosure. However, no bundle files were provided to verify the reference exists, and the SKILL.md itself contains almost no actionable content — it's essentially just a pointer to the reference file with a generic wrapper, making the split feel like it went too far.	2 / 3
	Total	7 / 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/cursor-rules-java
Commit: 3fa5789

Reviewed: 3 days 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.