411-frameworks-quarkus-jdbc
Use when you need programmatic JDBC in Quarkus — Agroal DataSource, parameterized SQL, transactions, batching, and Dev Services. Part of the skills-for-java project
74
67%
Does it follow best practices?
Impact
Pending
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, well-crafted skill description that clearly identifies its niche (programmatic JDBC in Quarkus), lists specific capabilities, and includes an explicit 'Use when' trigger clause. The trigger terms are natural and comprehensive for the target audience. The only minor note is the trailing 'Part of the skills-for-java project' which is metadata rather than functional description, but it doesn't detract from quality.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions/capabilities: 'Agroal DataSource, parameterized SQL, transactions, batching, and Dev Services'. These are concrete, identifiable technical features rather than vague abstractions. | 3 / 3 |
Completeness | Explicitly answers both 'what' (programmatic JDBC in Quarkus — Agroal DataSource, parameterized SQL, transactions, batching, Dev Services) and 'when' ('Use when you need programmatic JDBC in Quarkus'). The 'Use when' clause is present and clear. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords a developer would use: 'JDBC', 'Quarkus', 'Agroal', 'DataSource', 'parameterized SQL', 'transactions', 'batching', 'Dev Services'. These cover the key terms a user working with Quarkus JDBC would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a specific niche (programmatic JDBC in Quarkus with Agroal) that is clearly distinguishable from other Java/Quarkus skills like ORM/Hibernate or reactive SQL. The combination of 'JDBC', 'Quarkus', and 'Agroal' creates a very narrow, well-defined scope. | 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 is essentially a table of contents and a link to a reference file, with no executable code examples or concrete patterns in the body itself. While the constraints section provides a reasonable compile/verify workflow, the complete absence of actionable code or specific guidance in the skill body means Claude would need to read the reference file before being able to do anything useful. The skill would benefit greatly from including at least a few key code examples inline.
Suggestions
Add at least 2-3 concrete, executable Java code examples inline (e.g., DataSource injection + PreparedStatement with bind parameters, ResultSet-to-record mapping, batch insert pattern) so the skill is actionable without requiring the reference file.
Remove or significantly condense the 'What is covered' bullet list — it reads like a table of contents and wastes tokens. Instead, use that space for actual code patterns.
Add a quick-start section showing the minimal working JDBC pattern (inject DataSource, try-with-resources, parameterized query) that Claude can immediately apply.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bullet list of covered topics is somewhat verbose and reads like a table of contents rather than actionable content. The 'What is covered' section explains scope but doesn't add much value since the actual content is deferred to the reference file. However, it's not egregiously padded. | 2 / 3 |
Actionability | There are no concrete code examples, no executable commands beyond generic mvnw compile, and no specific JDBC patterns shown. Everything actionable is deferred to the reference file. The skill body describes rather than instructs. | 1 / 3 |
Workflow Clarity | The constraints section provides a clear compile-before/verify-after sequence with a stop condition on failure, which is good. However, the actual JDBC workflow steps (how to apply improvements, what to check) are entirely absent — all deferred to the reference file. | 2 / 3 |
Progressive Disclosure | There is a single reference file linked at the bottom, which is one-level deep and clearly signaled. However, the SKILL.md itself is essentially just a pointer to the reference with very little standalone value — the balance between overview content and reference content is poor, with too little useful content in the skill itself. | 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
1847adc
- 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.