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. Part of cursor-rules-java project
88
85%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly defines its scope around Spring Data JDBC with Java records, lists specific capabilities, and includes explicit trigger guidance. The description covers both 'what' and 'when' effectively, and the domain is narrow enough to avoid conflicts with other skills. Minor improvement could be made by trimming the trailing project attribution which doesn't aid skill selection.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: entity design with records, repository pattern, immutable updates, aggregate relationships, custom queries, transaction management, and avoiding N+1 problems. | 3 / 3 |
Completeness | Clearly answers both 'what' (Spring Data JDBC with Java records, covering entity design, repositories, immutable updates, etc.) and 'when' (explicit 'Use when' clause and 'This should trigger for' clause with example requests like reviewing Java code for Spring Data JDBC). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Spring Data JDBC', 'Java records', 'repository pattern', 'N+1 problems', 'custom queries', 'transaction management', 'best practices'. These are terms developers naturally use when seeking help in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of 'Spring Data JDBC' with 'Java records' is a very specific niche. It's clearly distinguishable from general Java skills, Spring Boot skills, or Spring Data JPA skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill has strong workflow clarity with explicit validation checkpoints and good progressive disclosure via a single reference file. However, it lacks any inline code examples, which weakens actionability — Claude must read the reference before it can act. The topic enumeration in the 'What is covered' section adds moderate verbosity without adding actionable value.
Suggestions
Add at least one or two inline good/bad code snippets (e.g., a record entity definition and a repository example) so the skill is actionable without requiring the reference file for basic patterns.
Trim or remove the 'What is covered' bullet list — it largely duplicates what the reference file contains and what the workflow already implies; replace it with a single sentence pointing to the reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered' bullet list is somewhat redundant with the reference file and adds moderate verbosity. The constraints and workflow sections are reasonably tight but the introductory enumeration of topics Claude could discover from the reference file wastes tokens. | 2 / 3 |
Actionability | The skill provides concrete commands (./mvnw compile, mvn clean verify) and a clear workflow, but lacks any executable code examples — all actual patterns and good/bad examples are deferred entirely to the reference file. Without inline examples, Claude has no copy-paste-ready guidance in the skill itself. | 2 / 3 |
Workflow Clarity | The workflow is clearly sequenced (read reference → gather scope → apply changes → verify), with explicit pre-flight compilation checks, a stop-on-failure gate, and post-change verification. Edge-case handling (ambiguous scope, missing inputs) is also addressed. | 3 / 3 |
Progressive Disclosure | The skill serves as a concise overview and delegates detailed rules, patterns, and examples to a single clearly-referenced file (references/312-frameworks-spring-data-jdbc.md) — one level deep with a well-signaled link. Content is appropriately split for a skill of this nature. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jabrena/cursor-rules-java
- Commit
762cb86
- Reviewed
Table of Contents
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.