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
74
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/411-frameworks-quarkus-jdbc/SKILL.mdQuality
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 uses appropriate third-person voice and includes both domain-specific and natural trigger terms that developers would use. Minor improvement could be made by slightly tightening the prose, but overall it's well-crafted for 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 and @Transactional makes it very unlikely to conflict with other skills. | 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, with almost all actionable content deferred elsewhere. The body lacks any concrete code examples, specific patterns, or executable guidance for JDBC in Quarkus. While the structure is reasonable and constraints mention compilation verification, the skill would benefit enormously from at least one or two concrete code snippets demonstrating key patterns inline.
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 requiring the reference file.
Consolidate the five redundant compilation constraint bullets into a single clear pre/post verification step within the workflow itself.
Make workflow steps specific to JDBC tasks rather than generic (e.g., step 3 could say 'Replace string-concatenated SQL with PreparedStatement bind parameters' with a before/after example).
Include a minimal good/bad code comparison inline for the most critical pattern (e.g., SQL injection prevention or CDI self-invocation pitfall) to make the skill immediately useful.
| 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 avoids explaining basic concepts Claude already knows. | 2 / 3 |
Actionability | The skill contains zero 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 a clear 4-step sequence with a verification step at the end and compilation checks mentioned in constraints. However, the steps are generic ('Gather scope', 'Apply framework-aligned changes') and lack specific validation checkpoints or feedback loops for error recovery within the JDBC-specific domain. | 2 / 3 |
Progressive Disclosure | There is a clear reference to a single external file for detailed guidance, which is appropriate one-level-deep disclosure. However, the SKILL.md body itself contains almost no substantive content — it's essentially just a pointer to the reference file with a generic workflow wrapper, making the skill body feel hollow rather than being a useful overview. | 2 / 3 |
Total | 7 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
ef4eba3
- 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.