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. Part of the skills-for-java project
77
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/312-frameworks-spring-data-jdbc/SKILL.mdQuality
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 identifies its niche (Spring Data JDBC with Java records), lists comprehensive specific capabilities, and includes an explicit 'Use when' trigger clause. The description uses third person voice appropriately and contains natural keywords that developers would use when seeking help in this area. Minor note: 'Part of the skills-for-java project' is organizational metadata that doesn't aid skill selection but doesn't significantly detract.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: entity design with records, repository pattern, immutable updates, aggregate relationships, custom queries, transaction management, and avoiding N+1 problems. These are all concrete, actionable topics. | 3 / 3 |
Completeness | Explicitly answers both 'what' (entity design, repository pattern, immutable updates, aggregate relationships, custom queries, transaction management, N+1 avoidance) and 'when' ('Use when you need to use Spring Data JDBC with Java records'). The 'Use when...' clause is present and clear. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Spring Data JDBC', 'Java records', 'repository pattern', 'N+1 problems', 'aggregate relationships', 'custom queries', 'transaction management', 'immutable updates'. These cover the terms a developer would naturally use when seeking help in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — the combination of 'Spring Data JDBC' specifically with 'Java records' carves out a very clear niche. This would not conflict with general Java skills, Spring Boot skills, or Spring Data JPA skills due to the specific JDBC + records focus. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-structured as a navigation document with clear constraints and a single reference link, but it critically lacks any concrete code examples or actionable patterns in the body itself. It essentially serves as a pointer to the reference file without providing any quick-start value or executable guidance that Claude could immediately apply. The workflow around compilation checks is reasonable but could be more explicit about error recovery.
Suggestions
Add at least 2-3 concrete code examples showing key patterns (e.g., a record entity definition, a repository interface, an immutable update with wither) so the skill body is actionable without requiring the reference file for basic tasks.
Convert the constraints section into a numbered workflow with an explicit feedback loop: 1. Compile → 2. Apply changes → 3. Verify → 4. If verify fails, review errors and return to step 2.
Remove or significantly condense the 'What is covered' bullet list — it describes topics rather than instructing, and the reference file already contains the detailed content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bullet-point list of covered topics is somewhat verbose and reads like a table of contents rather than actionable content. The 'What is covered' section explains scope but doesn't add much value since the reference file contains the actual guidance. However, it's not egregiously padded. | 2 / 3 |
Actionability | The skill contains no concrete code examples, no executable commands beyond compile/verify, and no specific patterns to follow. It entirely delegates to a reference file for 'detailed rules and good/bad patterns,' making the skill body itself vague and non-actionable. | 1 / 3 |
Workflow Clarity | The constraints section provides a clear sequence (compile → apply → verify) with a stop condition on failure, which is good. However, the validation steps are listed as bullet points rather than a numbered workflow, and there's no explicit feedback loop for what to do if verification fails after changes. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with a well-signaled one-level-deep reference to the detailed guidance file. The structure is clean with distinct sections for scope, constraints, usage triggers, and the reference link. | 3 / 3 |
Total | 8 / 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
9ec21dd
- 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.