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. 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/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 identifies its niche (programmatic JDBC in Micronaut), lists specific concrete capabilities, and opens with an explicit 'Use when' trigger clause. The trigger terms are natural and technically precise, making it easy for Claude to select this skill when a user asks about JDBC, DataSource configuration, or transactional SQL in a Micronaut context. The only minor note is the use of second person 'you' in 'Use when you need', but this is a common convention in trigger clauses and doesn't significantly detract.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: pooled DataSource, parameterized SQL, Transactional annotation usage, batching, and domain exception translation. These are clearly defined technical capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (pooled DataSource, parameterized SQL, transactional management, batching, exception translation) and 'when' with an explicit 'Use when you need programmatic JDBC in Micronaut' trigger clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords a developer would use: 'JDBC', 'Micronaut', 'DataSource', 'parameterized SQL', 'Transactional', 'batching', and the fully qualified annotation path 'io.micronaut.transaction.annotation.Transactional'. These are terms developers naturally search for. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets the specific niche of programmatic JDBC in Micronaut, which is clearly distinguishable from ORM-based approaches (like Micronaut Data), other frameworks, or non-JDBC database access patterns. | 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 table of contents pointing to a reference file, rather than providing actionable guidance itself. It lists many topics but includes zero code examples, no concrete patterns, and no executable instructions. The constraints section provides reasonable build verification steps, but the core content is entirely deferred to the reference document.
Suggestions
Add at least 2-3 concrete, executable code examples inline (e.g., DataSource injection, PreparedStatement with bind parameters, ResultSet-to-record mapping) so the skill is actionable without requiring the reference file.
Remove or significantly condense the 'What is covered' bullet list — it reads like a syllabus rather than instructions. Replace with a brief summary and move topic details to the reference.
Add a 'Quick start' or 'Common patterns' section with copy-paste-ready code snippets for the most frequent use cases (e.g., parameterized query, batch insert, @Transactional usage).
Include a specific example of the SQLException-to-domain-exception translation pattern and the self-invocation pitfall fix, as these are the most error-prone areas where concrete guidance adds the most value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bullet list under 'What is covered' is somewhat verbose and reads more like a table of contents than actionable content. Some items explain concepts Claude already knows (e.g., 'never string concatenation', 'never assume rs.next() succeeds'). However, it's not egregiously padded. | 2 / 3 |
Actionability | The skill body contains no executable code, no concrete commands beyond generic 'mvnw compile', and no specific examples. It describes what topics are covered but doesn't actually instruct Claude how to do anything — all real content is deferred to the reference file. | 1 / 3 |
Workflow Clarity | The Constraints section provides a clear sequence (compile before, apply changes, verify after) with a stop condition on failure, which is good. However, the validation steps are generic ('compile', 'verify') without specific feedback loops for JDBC-specific issues, and the actual workflow of applying improvements is entirely absent — it just says 'see the reference.' | 2 / 3 |
Progressive Disclosure | There is a clear reference to a single external file, which is good one-level-deep disclosure. However, the SKILL.md itself is essentially just a pointer to the reference with a long bullet list that doesn't provide any quick-start actionable content — the overview doesn't stand on its own as useful guidance. | 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
9ec21dd
- 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.