312-frameworks-spring-data-jdbc

Use when you need to use Spring Data JDBC with Java records — including entity design with records, repository pattern, immutable updates, aggregate relationships, custom queries, transaction management, and avoiding N+1 problems. This should trigger for requests such as Review Java code for Spring Data JDBC; Apply best practices for Spring Data JDBC in Java code; Model Spring Data JDBC aggregates with Java records; Review Spring Data JDBC repositories and aggregate boundaries; Improve optimistic locking or domain events in Spring Data JDBC. Part of Plinth Toolkit

Quality

85%

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.

The body is well-structured as an overview with strong workflow validation and clean progressive disclosure to one reference file. Its main weakness is actionability: the actual technical patterns live entirely in the reference rather than inline.

Suggestions

Add 1-2 short inline code snippets (e.g., a record entity with @Table/@Id, or a repository interface with @Query) so the body gives executable guidance without forcing a reference read for common cases.

Remove or condense the 'When to use this skill' section since it duplicates the trigger phrases already in the frontmatter description.

Tighten workflow step 3 ('Apply framework-aligned changes') with a concrete pointer to the specific reference subsections to consult per change type.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not explain concepts Claude already knows, but the 'When to use this skill' section duplicates trigger phrases already present in the frontmatter description, a minor instance of padding that could be trimmed.	4 / 5
Actionability	Concrete verification commands ('./mvnw compile', 'mvn clean verify') are present, but the core technical guidance is delegated to the reference and the workflow step 'Implement or refactor configuration/code following the reference patterns' is high-level with no inline code examples.	3 / 5
Workflow Clarity	A clear 4-step sequence is paired with explicit validation checkpoints (MANDATORY compile before, SAFETY stop-on-failure, VERIFY after), providing the feedback loop the top anchor requires.	5 / 5
Progressive Disclosure	SKILL.md is a concise overview pointing to a single one-level-deep reference (references/312-frameworks-spring-data-jdbc.md) via a clearly signaled markdown link, with well-organized sections and easy navigation.	5 / 5
	Total	17 / 20 Passed

Description

92%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, specific description that clearly states both capabilities and explicit trigger conditions for a well-scoped niche. The only minor gap is the absence of synonym/extension variants in the trigger terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'entity design with records, repository pattern, immutable updates, aggregate relationships, custom queries, transaction management, and avoiding N+1 problems' — giving comprehensive coverage rather than vague abstraction.	5 / 5
Completeness	It explicitly answers 'what' (the enumerated capabilities) and 'when' via 'This should trigger for requests such as ...' with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'Review Java code for Spring Data JDBC' and 'Model Spring Data JDBC aggregates with Java records' read like real user requests, but synonyms and file/extension variants are absent so it falls short of the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	The narrow niche of 'Spring Data JDBC with Java records' with distinct trigger phrases and explicit routing to sibling skills (311/313) yields minimal overlap with other skills.	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/312-frameworks-spring-data-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.