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. Part of cursor-rules-java project
74
67%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/311-frameworks-spring-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, well-crafted skill description that excels across all dimensions. It provides comprehensive specificity with numerous concrete actions, includes natural trigger terms that developers would use, explicitly addresses both 'what' and 'when', and carves out a clear niche around Spring JDBC that distinguishes it from other Java or Spring skills. The only minor concern is verbosity — it could be slightly more concise — but the detail serves the purpose of disambiguation well.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists numerous specific concrete actions: JdbcClient as default API, JdbcTemplate for batch/streaming, NamedParameterJdbcTemplate for legacy code, parameterized SQL, RowMapper mapping to records, batch operations, transactions, generated keys handling, DataAccessException handling, read-only transactions, streaming large result sets, and @JdbcTest slice testing. | 3 / 3 |
Completeness | Clearly answers both 'what' (write/review programmatic JDBC with Spring, including a comprehensive list of capabilities) and 'when' (explicit 'Use when' clause at the start, plus a 'This should trigger for requests such as...' section with concrete example scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Spring JDBC', 'JdbcTemplate', 'JdbcClient', 'NamedParameterJdbcTemplate', 'SQL injection', 'transaction boundaries', 'exception handling', 'JDBC operations', 'batch operations', 'RowMapper', '@JdbcTest'. These are terms a developer would naturally use when seeking help with Spring JDBC. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — narrowly scoped to Spring JDBC specifically (JdbcClient, JdbcTemplate, NamedParameterJdbcTemplate). Unlikely to conflict with general Java skills, Spring Boot skills, or ORM-based skills like JPA/Hibernate due to the explicit JDBC focus and specific API names. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is structured as a thin wrapper that defers nearly all substantive guidance to a reference file, leaving the SKILL.md body with no executable code examples, no concrete patterns, and no domain-specific validation steps. The constraints section with compile/verify gates is a strength, but the core content lacks the actionability needed for Claude to act without reading the reference. The bullet-list summary of topics covered adds verbosity without adding actionable value.
Suggestions
Add at least 2-3 concrete, executable code examples directly in SKILL.md (e.g., JdbcClient query with RowMapper, parameterized update, batch operation) so Claude can act without reading the reference file.
Replace the 'What is covered' bullet list with a concise quick-start section showing the most common pattern (JdbcClient fluent query) — this saves tokens and adds actionability.
Add explicit validation checkpoints within the workflow for JDBC-specific concerns, e.g., 'After refactoring to JdbcClient, verify no raw string concatenation remains in SQL statements' or 'Check that @Transactional boundaries are at the service layer, not repository layer'.
Include a brief good/bad pattern comparison inline (e.g., SQL injection anti-pattern vs. bind parameter pattern) so the skill is self-contained for the most critical safety concern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The 'What is covered in this Skill?' bullet list is essentially a table of contents that restates the description and adds little actionable value — it's a verbose summary of what the reference file covers. However, the constraints and workflow sections are reasonably tight. | 2 / 3 |
Actionability | There are no concrete code examples, executable commands beyond build invocations, or copy-paste-ready patterns. All actual guidance is deferred to the reference file. The skill body describes rather than instructs for the core domain (Spring JDBC usage). | 1 / 3 |
Workflow Clarity | The workflow has a clear 4-step sequence with compilation checks before and verification after, which is good. However, the steps are generic ('apply framework-aligned changes', 'gather scope') and lack explicit validation checkpoints or error-recovery feedback loops within the JDBC-specific work itself. | 2 / 3 |
Progressive Disclosure | There is a clear reference to a single detailed file (references/311-frameworks-spring-jdbc.md), which is good one-level-deep disclosure. However, no bundle files were provided to verify the reference exists, and the SKILL.md itself contains almost no substantive quick-start content — it's nearly entirely a pointer, making the overview layer too thin to be useful on its own. | 2 / 3 |
Total | 7 / 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.