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

88%

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

Quality

Content

77%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 an explicit validate/stop/verify workflow, though the body's own actionability is limited because the concrete JDBC patterns live entirely in the reference file.

Suggestions

Add one or two short inline good/bad JDBC snippets (e.g., a JdbcClient query-to-record example vs a concatenated-SQL anti-pattern) so the body is actionable without forcing a reference read for common cases.

Trim the 'When to use this skill' section since its trigger phrases duplicate the description's 'This should trigger for requests such as' list, or replace it with a pointer to the description.

Make the feedback loop explicit inside the Workflow steps (e.g., add a 'if compile fails, stop and fix before proceeding' checkpoint between steps 1 and 3) rather than relying solely on the separate Constraints section.

Dimension	Reasoning	Score
Conciseness	The body is lean with no padding about concepts Claude already knows, but 'What is covered in this Skill?' and 'When to use this skill' partly restate capabilities and triggers already present in the description, which could be trimmed.	4 / 5
Actionability	It gives concrete, executable build commands ('./mvnw compile', 'mvn clean verify') but delegates the substantive JDBC code guidance to the reference, so the body alone offers only partial executable guidance for the core task.	3 / 5
Workflow Clarity	The four-step Workflow is a clear sequence and the Constraints section provides an explicit validation feedback loop — MANDATORY compile before, SAFETY stop-on-failure, VERIFY clean after — acting as a checklist for risky code changes.	5 / 5
Progressive Disclosure	SKILL.md is a concise overview with a single well-signaled, one-level-deep reference link to references/311-frameworks-spring-jdbc.md (a real 43KB file), keeping detail appropriately split and easy to navigate.	5 / 5
	Total	17 / 20 Passed

Description

100%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 strong, third-person description that explicitly states both what the skill does and when to use it, with concrete capabilities and natural trigger phrases. It is comprehensive without relying on buzzwords or padding.

Dimension	Reasoning	Score
Specificity	Lists many concrete capabilities — 'parameterized SQL', 'RowMapper mapping to records', 'batch operations', 'safe handling of generated keys', 'read-only transactions', 'streaming large result sets', '@JdbcTest slice testing' — giving comprehensive coverage rather than vague abstractions.	5 / 5
Completeness	It opens with 'Use when you need to write or review programmatic JDBC with Spring' (clear what) and follows with a concrete 'This should trigger for requests such as' list (explicit when), satisfying both halves.	5 / 5
Trigger Term Quality	The explicit 'This should trigger for requests such as' block supplies natural user phrases ('Review Java code for Spring JDBC', 'Detect and fix SQL injection risks in JDBC code', 'Improve transaction boundaries') plus synonyms across JdbcClient/JdbcTemplate/NamedParameterJdbcTemplate.	5 / 5
Distinctiveness Conflict Risk	The niche is tightly scoped to Spring Framework 7+ JdbcClient and specific JDBC concerns, with distinct triggers (JdbcClient, Spring JDBC, @JdbcTest) that minimally overlap with other skills.	5 / 5
	Total	20 / 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/311-frameworks-spring-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.