511-frameworks-micronaut-jdbc
Use when you need programmatic JDBC in Micronaut — pooled DataSource, parameterized SQL, io.micronaut.transaction.annotation.Transactional, batching, and domain exception translation. This should trigger for requests such as Review JDBC or SQL data access in a Micronaut project; Improve transactions and parameter binding for Micronaut JDBC; Translate SQLException to domain exceptions or stream large result sets; Fix self-invocation bypassing @Transactional in Micronaut. 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/511-frameworks-micronaut-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 niche (programmatic JDBC in Micronaut), lists specific concrete capabilities, and provides explicit trigger scenarios. The inclusion of detailed example requests ('Fix self-invocation bypassing @Transactional') makes it highly actionable for skill selection. Minor note: it uses second person 'you' in the opening clause, but the rest is appropriately structured.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: pooled DataSource, parameterized SQL, Transactional annotation, batching, domain exception translation, stream large result sets, fix self-invocation bypassing @Transactional. | 3 / 3 |
Completeness | Clearly answers both 'what' (pooled DataSource, parameterized SQL, transactional management, batching, exception translation) and 'when' with explicit trigger scenarios ('Use when you need programmatic JDBC in Micronaut', 'This should trigger for requests such as...' with multiple concrete examples). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'JDBC', 'SQL', 'Micronaut', 'DataSource', 'Transactional', 'parameter binding', 'SQLException', 'domain exceptions', 'result sets', 'batching'. Good coverage of terms a developer working with Micronaut JDBC would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — narrowly scoped to Micronaut JDBC specifically, with domain-specific triggers like '@Transactional', 'self-invocation bypassing', 'SQLException to domain exceptions'. Unlikely to conflict with general SQL, ORM, or other framework 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 more as an index/table of contents than actionable guidance. It lists many topics covered but provides zero code examples, no concrete patterns, and defers all substance to a reference file. The workflow is structured but generic, and the constraints section is repetitive. The skill would benefit significantly from at least one or two inline executable examples demonstrating key patterns.
Suggestions
Add at least 2-3 concrete, executable code examples inline (e.g., PreparedStatement with bind parameters, ResultSet-to-record mapping, SQLException translation pattern) so the skill provides standalone value without requiring the reference file.
Consolidate the constraints section — the five bullet points about compilation can be reduced to two: 'Run ./mvnw compile before changes; run ./mvnw clean verify after. Stop if compilation fails.'
Remove or drastically shorten the 'What is covered' bullet list — it explains concepts Claude already knows and adds no actionable value. Replace with a quick-start example showing the most common pattern.
Add a concrete error-recovery step in the workflow (e.g., 'If verify fails, check test output for SQLException patterns and apply domain exception translation from the reference').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list is essentially a table of contents that restates concepts Claude already understands. The constraints section is repetitive (multiple bullets saying 'compile before/after'). However, it's not egregiously verbose — it stays reasonably focused on the domain. | 2 / 3 |
Actionability | There are no concrete code examples, no executable commands beyond generic mvnw invocations, and no specific patterns shown. Everything is deferred to the reference file. The skill body describes what to do rather than showing how to do it — it reads as an index rather than actionable guidance. | 1 / 3 |
Workflow Clarity | The workflow has a clear 4-step sequence with a compilation prerequisite and post-change verification step, which is good. However, the steps are generic ('apply framework-aligned changes') with no validation checkpoints between substeps, and there's no error recovery/feedback loop beyond 'stop if compilation fails.' | 2 / 3 |
Progressive Disclosure | The skill correctly references a single external file (references/511-frameworks-micronaut-jdbc.md) for detailed content, which is good one-level-deep disclosure. However, since no bundle files were provided, we can't verify the reference exists, and the SKILL.md itself provides almost no standalone value — it's essentially just a pointer with no quick-start content or inline examples. | 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
762cb86
- 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.