spring-data-jdbc

Rules and guidelines for working with Spring Data JDBC in the project. ALWAYS use this skill when adding, removing, or modifying Spring Data JDBC entities (@Table from org.springframework.data.relational.core.mapping), aggregates, AggregateReference links, embedded objects, @MappedCollection associations, or Spring Data JDBC repositories (CrudRepository / ListCrudRepository). Trigger on any request that touches @Table, @Column, @MappedCollection, @Embedded annotations from spring-data-relational, AggregateReference fields, @PersistenceCreator constructors, or @Query methods on JDBC repositories. Do NOT use for JPA (jakarta.persistence) entities — use the spring-data-jpa skill instead.

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

78%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, actionable skill body that routes to real one-level-deep reference files with clear numbered workflows and mandatory verification gates. The main improvements are tightening repeated parentheticals/MCP preflight prose and adding explicit error-recovery feedback loops for destructive entity modifications.

Suggestions

Consolidate the repeated 'check memory (or earlier conversation turns — see Harness compatibility)' reminder into a single stated-once note to reduce token repetition across the entity, repository, and aggregate sections.

Add an explicit validate→fix→retry feedback loop to the 'Working with JDBC Entities' and 'Working with Aggregates' workflows (e.g., re-check aggregate membership via get_jdbc_entity_details after the edit and roll back if a rule is violated), since these are destructive code changes.

Tighten the 'Preflight: Spring MCP' and 'MCP availability and fallbacks' sections — the install-handling narrative can be compressed without losing the fallback-grep guidance that is the operationally important part.

Dimension	Reasoning	Score
Conciseness	The body is efficient operational instruction without basic-concept padding, but the repeated 'check memory (or earlier conversation turns — see Harness compatibility)' parentheticals and the lengthy MCP preflight/fallback sections could be trimmed.	4 / 5
Actionability	It gives concrete executable guidance — a copy-paste grep regex '(extends\|:)\s*(ListCrudRepository\|CrudRepository\|...)', named MCP tools, and a review output template — but the core rule content itself is delegated to reference files rather than inlined.	4 / 5
Workflow Clarity	Multi-step workflows are clearly numbered with MANDATORY gates and verification ('Verify from get_jdbc_entity_details that both participants are aggregate roots'), though explicit validate→fix→retry recovery loops for destructive entity edits are limited.	4 / 5
Progressive Disclosure	The body is a clear overview that points to six well-signaled one-level-deep reference files (entity/aggregate/repository conventions and rules-impl), all of which exist on disk, with content appropriately split and easy to navigate.	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, highly specific description that clearly states what the skill covers and when to trigger it, with explicit boundary guidance against the closely related JPA stack. The only minor gap is trigger-term phrasing that leans on technical annotations rather than plain-language synonyms.

Dimension	Reasoning	Score
Specificity	The description lists multiple specific concrete actions — 'adding, removing, or modifying Spring Data JDBC entities', 'aggregates, AggregateReference links, embedded objects, @MappedCollection associations, or Spring Data JDBC repositories' — giving comprehensive coverage rather than just naming the domain.	5 / 5
Completeness	It explicitly answers both 'what' ('Rules and guidelines for working with Spring Data JDBC') and 'when' ('ALWAYS use this skill when...', 'Trigger on any request that touches...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage across @Table, @Column, @MappedCollection, @Embedded, AggregateReference, @PersistenceCreator, @Query, and CrudRepository/ListCrudRepository, but the terms lean technical-jargon with no plain-language synonyms or file extensions to reach comprehensive natural-term coverage.	4 / 5
Distinctiveness Conflict Risk	A clear niche (Spring Data JDBC) with explicit disambiguation against JPA ('Do NOT use for JPA (jakarta.persistence) entities — use the spring-data-jpa skill instead') minimizes conflict risk.	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: Amplicode/spring-skills
Path: skills/spring-data-jdbc/SKILL.md
Commit: bf19b3c

Reviewed: 5 days 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.