411-frameworks-quarkus-jdbc
Programmatic JDBC in Quarkus with 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
50%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at listing specific technical capabilities and has a clear, distinct niche in the Quarkus/Agroal/JDBC space. However, it critically lacks any 'Use when...' guidance, making it difficult for Claude to know when to select this skill. The trailing project attribution adds no selection value.
Suggestions
Add a 'Use when...' clause with trigger scenarios like 'Use when the user needs direct database access in Quarkus, asks about connection pooling with Agroal, or wants to execute raw SQL queries'
Include common user-facing terms like 'database connection', 'raw SQL queries', 'connection pooling', or 'database operations' that developers might naturally use
Remove 'Part of the skills-for-java project' as it provides no value for skill selection and wastes description space
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Programmatic JDBC', 'Agroal DataSource', 'parameterized SQL', 'transactions', 'batching', and 'Dev Services'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance. The 'Part of the skills-for-java project' adds no value for skill selection. Per rubric, missing 'Use when' caps completeness at 2, and this is weaker than that anchor. | 1 / 3 |
Trigger Term Quality | Contains relevant technical keywords like 'JDBC', 'Quarkus', 'Agroal', 'DataSource', 'SQL', 'transactions' that developers would use, but missing common variations like 'database connection', 'query', 'database access', or 'connection pooling'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting Quarkus + Agroal + JDBC combination. The technology stack is distinct enough that it's unlikely to conflict with other database or Java skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill excels at conciseness, workflow clarity, and progressive disclosure - it's well-structured with clear validation checkpoints and appropriate delegation to a reference file. However, it lacks any concrete code examples in the main skill body, making it less immediately actionable; users must navigate to the reference for any executable guidance.
Suggestions
Add one minimal executable code example showing the core pattern (e.g., DataSource injection with try-with-resources and PreparedStatement with bind parameters)
Include a brief 'bad vs good' code snippet for the most critical anti-pattern (string concatenation vs bind parameters) to make the skill immediately actionable
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, using bullet points to list specific topics without explaining basic concepts Claude already knows. No padding or unnecessary context about what JDBC or Quarkus is. | 3 / 3 |
Actionability | The skill lists specific patterns and concepts but provides no executable code examples. It describes what to do (bind parameters, mapRow method, setFetchSize) but delegates all concrete implementation to the reference file. | 2 / 3 |
Workflow Clarity | Clear workflow with explicit validation checkpoints: compile before changes, stop if compilation fails, verify after changes. The MANDATORY/PREREQUISITE/SAFETY/BLOCKING labels make the sequence unambiguous. | 3 / 3 |
Progressive Disclosure | Excellent structure with a concise overview, clear 'When to use' section, and a single well-signaled reference link for detailed guidance. One level deep, easy navigation. | 3 / 3 |
Total | 11 / 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
16eb4bf
- 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.