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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

70%

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

The body is well-structured with a clear workflow and good progressive disclosure to a single reference file, but it is held back by redundancy with the description and a lack of any inline executable code examples. Tightening the duplicated trigger list and including at least one small concrete JDBC code snippet would lift the weaker dimensions.

Suggestions

Remove or condense the 'When to use this skill' section, which repeats the description's triggers verbatim, to improve conciseness.

Consolidate the overlapping MANDATORY/PREREQUISITE/SAFETY/BLOCKING CONDITION constraint lines into a single clear compile-then-verify rule.

Add one short inline executable JDBC example (e.g., a try-with-resources PreparedStatement snippet) so the body is actionable without requiring the reference.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with a useful bulleted coverage list, but the 'When to use this skill' section verbatim repeats the trigger phrases already in the description, and the MANDATORY/PREREQUISITE/SAFETY/BLOCKING CONDITION constraints overlap heavily, which could be tightened.	2 / 3
Actionability	Concrete commands are present ('./mvnw compile', 'mvn clean verify') and specific APIs named (@Transactional, setFetchSize, addBatch), but no executable code examples appear in the body — all code is deferred to the reference, leaving the guidance instructive rather than copy-paste ready.	2 / 3
Workflow Clarity	A clear 4-step sequence with explicit validation checkpoints for database/batch work (compile before, stop immediately on failure, verify after), satisfying the feedback-loop requirement for batch operations.	3 / 3
Progressive Disclosure	A concise overview points to a single one-level-deep reference (references/511-frameworks-micronaut-jdbc.md), which exists on disk and is clearly signaled in both the Workflow and Reference sections.	3 / 3
	Total	10 / 12 Passed

Description

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.

A strong, specific description with concrete capabilities and natural trigger phrases that clearly answer both what the skill does and when to use it. The only minor weakness is that the 'When to use this skill' section duplicates the same trigger phrases already present in the description, but this does not detract from the description's own quality.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('pooled DataSource, parameterized SQL, io.micronaut.transaction.annotation.Transactional, batching, and domain exception translation') rather than vague language, matching the score-3 anchor.	3 / 3
Completeness	Explicitly answers both what (programmatic JDBC capabilities) and when ('This should trigger for requests such as...'), satisfying the score-3 anchor.	3 / 3
Trigger Term Quality	Includes natural phrases users would actually say ('Review JDBC or SQL data access in a Micronaut project', 'Improve transactions and parameter binding', 'Fix self-invocation bypassing @Transactional'), giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Scoped tightly to Micronaut JDBC with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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
Commit: aaee915

Reviewed: 1 day 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.