311-frameworks-spring-jdbc
Use when you need to write or review programmatic JDBC with Spring — including JdbcTemplate, NamedParameterJdbcTemplate, JdbcClient (Spring Framework 6.1+), 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. 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/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 an excellent skill description that clearly defines its scope (Spring JDBC programmatic access), provides comprehensive trigger terms that developers would naturally use, and explicitly states when to use it. The description is specific, complete, and highly distinctive from other potential database or Spring-related skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: JdbcTemplate, NamedParameterJdbcTemplate, JdbcClient, parameterized SQL, RowMapper mapping, batch operations, transactions, generated keys handling, DataAccessException handling, streaming large result sets, and @JdbcTest slice testing. | 3 / 3 |
Completeness | Explicitly answers both what (write or review programmatic JDBC with Spring, including comprehensive list of capabilities) AND when ('Use when you need to write or review programmatic JDBC with Spring') with clear trigger guidance at the start. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'JDBC', 'Spring', 'JdbcTemplate', 'NamedParameterJdbcTemplate', 'JdbcClient', 'RowMapper', 'batch operations', 'transactions', '@JdbcTest'. These are terms developers naturally use when working with Spring JDBC. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically targets Spring JDBC (not JPA, not Hibernate, not generic database access). The specific technologies mentioned (JdbcTemplate, JdbcClient, @JdbcTest) create a clear boundary that won't conflict with other database or Spring skills. | 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 functions primarily as a navigation document pointing to a reference file rather than providing standalone actionable guidance. While it has good structure and appropriate progressive disclosure, the complete absence of code examples or concrete patterns in the main skill body significantly limits its immediate utility. The constraints section provides useful guardrails but the skill relies entirely on the reference for actual implementation guidance.
Suggestions
Add at least one concrete, executable code example showing JdbcClient or JdbcTemplate usage with parameterized SQL directly in the skill body
Include a minimal good/bad pattern comparison for SQL injection prevention to make the safety guidance immediately actionable
Expand the 'stop immediately' constraint to include specific recovery steps (e.g., 'fix compilation errors before proceeding')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes a verbose 'What is covered' list that largely duplicates information Claude could infer from the title and reference. The constraints section is appropriately concise. | 2 / 3 |
Actionability | No concrete code examples, commands, or executable guidance provided in the skill body itself. All actionable content is deferred to the reference file, leaving this as a table of contents rather than actionable instructions. | 1 / 3 |
Workflow Clarity | The constraints section provides a clear sequence (compile -> apply -> verify) with validation checkpoints, but lacks error recovery guidance. The 'stop immediately' instruction is vague about what to do next. | 2 / 3 |
Progressive Disclosure | Clean structure with a single, clearly signaled reference file. The overview appropriately summarizes scope without embedding detailed content, and navigation to the reference is straightforward. | 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
7772a1b
- 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.