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
59
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 scope (programmatic JDBC in Micronaut), lists concrete capabilities, and provides explicit trigger scenarios. The inclusion of specific example requests makes it easy for Claude to match user queries. 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 usage, batching, domain exception translation, streaming large result sets, fixing 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 phrases like 'Use when you need programmatic JDBC in Micronaut' and specific example requests such as 'Review JDBC or SQL data access in a Micronaut project'. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'JDBC', 'SQL', 'Micronaut', 'DataSource', '@Transactional', 'parameter binding', 'SQLException', 'domain exceptions', 'self-invocation', 'result sets'. Good coverage of terms a developer working with Micronaut JDBC would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — scoped specifically to Micronaut JDBC (not generic Java JDBC, not Micronaut Data/ORM), with clear niche triggers like 'Micronaut JDBC', '@Transactional', 'self-invocation bypassing'. 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 pointer to an external reference file, with almost no actionable content in the body itself. The bullet list of covered topics is informational but not instructive, and the workflow steps are generic enough to apply to any framework skill. The constraints section is repetitive, and the complete absence of code examples or concrete patterns significantly limits the skill's standalone utility.
Suggestions
Add at least 2-3 concrete, executable code examples for the most common patterns (e.g., parameterized query with PreparedStatement, ResultSet-to-record mapping, SQLException translation) so the skill is actionable without reading the reference file.
Consolidate the constraints section into 2-3 concise bullet points instead of repeating the compile-before/verify-after concept five times with different labels (MANDATORY, PREREQUISITE, SAFETY, BLOCKING CONDITION, VERIFY).
Replace or supplement the generic 4-step workflow with a more specific sequence that includes concrete validation checkpoints, e.g., 'After adding @Transactional, verify the proxy is created by checking bean introspection' or 'After batch insert refactor, run the specific test class.'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list is essentially a table of contents for the reference file and adds moderate bloat. The constraints section repeats the same 'compile before/after' idea five different ways. However, it avoids explaining basic concepts Claude already knows (JDBC, PreparedStatement, etc.). | 2 / 3 |
Actionability | There are no concrete code examples, no executable commands beyond generic 'mvnw compile', and no specific patterns shown. Everything actionable is deferred to the reference file. The skill body describes rather than instructs — it tells Claude what topics exist but not how to implement them. | 1 / 3 |
Workflow Clarity | The four workflow steps provide a reasonable sequence (read reference → assess → apply → verify), and there is a compilation check before and after. However, the steps are generic and lack explicit validation checkpoints or feedback loops for error recovery beyond 'stop immediately 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 cannot verify the reference exists, and the SKILL.md itself contains a long bullet list that could be trimmed since it merely previews the reference content without adding standalone value. | 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
26e9744
- 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.