311-frameworks-spring-jdbc

Use when you need to write or review programmatic JDBC with Spring — including JdbcClient (Spring Framework 7+) as the default API, JdbcTemplate only where batch/streaming APIs require JdbcOperations, NamedParameterJdbcTemplate for legacy named-param code, parameterized SQL, RowMapper mapping to records, batch operations, transactions, safe handling of generated keys, DataAccessException handling, read-only transactions, streaming large result sets, and @JdbcTest slice testing. This should trigger for requests such as Review Java code for Spring JDBC (JdbcTemplate, JdbcClient, NamedParameterJdbcTemplate); Apply best practices for Spring JDBC data access in Java code; Detect and fix SQL injection risks in JDBC code; Improve transaction boundaries or exception handling for JDBC operations; Review JdbcClient usage in Spring Framework 7. Part of Plinth Toolkit

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

85%

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

A well-structured, lean overview with a clear validated workflow and clean one-level-deep reference navigation. Its main gap is actionability: the body holds build commands but no executable JDBC examples, leaving the actionable code in the reference.

Suggestions

Add one or two short executable JdbcClient/JdbcTemplate snippets (e.g. a parameterized query and a RowMapper-to-record example) inline so the body is actionable on its own, not only as a pointer.

Keep the SQL-injection constraint but pair it with a 1-line good/bad code contrast so the rule is immediately usable without opening the reference.

Dimension	Reasoning	Score
Conciseness	The body is a lean overview with organized lists (coverage, constraints, when-to-use, workflow) and no padding with concepts Claude already knows; every section earns its place.	3 / 3
Actionability	It provides some concrete executable guidance ('./mvnw compile', 'mvn clean verify', the never-concatenate-SQL rule), but the core JDBC patterns and code examples are deferred entirely to the reference, leaving the body's guidance on the actual data-access work abstract ('following the reference patterns').	2 / 3
Workflow Clarity	The 4-step workflow is paired with explicit validation checkpoints (MANDATORY compile before, SAFETY stop-if-failure, VERIFY clean verify after), giving a clear sequence with a feedback loop for error recovery.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview pointing one level deep to references/311-frameworks-spring-jdbc.md (verified to exist) via clearly signaled links, with content appropriately split between overview and detailed reference.	3 / 3
	Total	11 / 12 Passed

Description

90%

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, comprehensive description with explicit what/when triggers and natural request phrases. The only weakness is second-person voice ('you need'), which the rubric penalizes on specificity.

Suggestions

Rewrite the opening in third person to avoid the specificity penalty, e.g. 'Use when writing or reviewing programmatic JDBC with Spring' (drop 'you need').

Dimension	Reasoning	Score
Specificity	Lists many concrete actions (JdbcClient, parameterized SQL, RowMapper->records, batch ops, generated keys, @JdbcTest), which matches the anchor-3 example, but the second-person phrasing 'Use when you need to write or review programmatic JDBC' triggers the rubric's -1 specificity penalty, bringing it to 2.	2 / 3
Completeness	Explicitly answers both what (the enumerated JDBC capabilities) and when ('Use when you need to write or review programmatic JDBC with Spring' plus 'This should trigger for requests such as...'), matching the anchor-3 example.	3 / 3
Trigger Term Quality	Includes natural request phrases users would say, e.g. 'Review Java code for Spring JDBC (JdbcTemplate, JdbcClient, NamedParameterJdbcTemplate)', 'Detect and fix SQL injection risks', and 'Improve transaction boundaries or exception handling', giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche anchored to named APIs (JdbcClient, JdbcTemplate, NamedParameterJdbcTemplate, @JdbcTest) with distinct triggers, making it unlikely to fire for the wrong skill.	3 / 3
	Total	11 / 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.