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; Review Hikari or pooled datasource usage in Micronaut JDBC. Part of Plinth Toolkit

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/511-frameworks-micronaut-jdbc/SKILL.md

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured overview with strong progressive disclosure and explicit compile/verify validation gates, but the body itself carries no inline JDBC code examples and contains redundant constraint and trigger bullets that could be tightened.

Suggestions

Inline 1-2 short executable JDBC snippets (e.g. a parameterized PreparedStatement with try-with-resources and a catch-translate-rethrow block) so the core patterns don't depend entirely on the reference.

Dedupe the Constraints section: the MANDATORY and PREREQUISITE bullets both say 'compile before applying' — collapse them into a single compile-before gate.

Drop or trim the 'When to use this skill' section since its bullets duplicate the trigger phrases already in the frontmatter description.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with no basic-concept over-explanation, but noticeably redundant: the MANDATORY and PREREQUISITE constraint bullets both say 'compile before', and the 'When to use this skill' section duplicates the frontmatter triggers.	3 / 5
Actionability	Concrete build commands ('./mvnw compile', 'mvn clean verify') and specific API names appear, but all JDBC pattern code is deferred to the reference with no inline executable examples for the core task.	3 / 5
Workflow Clarity	A clear 4-step workflow with explicit validation gates (compile-before, stop-on-failure, verify-after) and a blocking handoff; held below 5 because the steps themselves are generic and error recovery is a user handoff rather than a fix-and-revalidate loop.	4 / 5
Progressive Disclosure	The body is a concise overview pointing to a single real one-level-deep reference (references/511-frameworks-micronaut-jdbc.md, verified present), signaled in both the Workflow step and a dedicated Reference section.	5 / 5
	Total	15 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A highly specific, well-triggered description for a narrow Micronaut JDBC niche, clearly answering both what and when with concrete natural-language triggers. The only weakness is second-person voice ('you need'), which slightly undercuts specificity per the rubric.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (pooled DataSource, parameterized SQL, io.micronaut.transaction.annotation.Transactional, batching, domain exception translation) warranting a 5, but reduced by 1 because the description uses second-person voice ('Use when you need programmatic JDBC in Micronaut').	4 / 5
Completeness	Explicitly answers both 'what' (pooled DataSource, parameterized SQL, @Transactional, batching, exception translation) and 'when' via an explicit 'Use when...' clause plus 'This should trigger for requests such as...' with concrete triggers.	5 / 5
Trigger Term Quality	Comprehensive natural trigger phrasings a user would say ('Review JDBC or SQL data access in a Micronaut project', 'Fix self-invocation bypassing @Transactional in Micronaut', 'Review Hikari or pooled datasource usage') with synonyms (JDBC/SQL, Hikari/pooled datasource).	5 / 5
Distinctiveness Conflict Risk	A tight Micronaut-JDBC niche with framework-specific triggers (@Transactional, Hikari, self-invocation) makes overlap with other skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: jabrena/plinth
Path: skills/511-frameworks-micronaut-jdbc/SKILL.md
Commit: 77b8825

Reviewed: about 23 hours ago

Table of Contents

Discovery Implementation Validation

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.