jpa-patterns
JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.
90
77%
Does it follow best practices?
Impact
98%
1.28xAverage score across 6 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/ja-JP/skills/jpa-patterns/SKILL.mdQuality
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description is strong on specificity and trigger terms, listing a comprehensive set of JPA/Hibernate topics that developers would naturally search for. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill over related ones like general Spring Boot or database skills. Adding trigger guidance would elevate this from good to excellent.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about JPA entities, Hibernate mappings, database relationships, or persistence-layer optimization in Spring Boot.'
Consider adding boundary language to distinguish from general Spring Boot or SQL skills, e.g., 'Not for raw SQL queries or Spring MVC/web layer concerns.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions/topics: entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling. These are concrete, well-defined technical capabilities. | 3 / 3 |
Completeness | Clearly answers 'what does this do' by listing specific JPA/Hibernate patterns and topics, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'JPA', 'Hibernate', 'entity design', 'relationships', 'query optimization', 'transactions', 'auditing', 'indexing', 'pagination', 'pooling', 'Spring Boot'. These cover the main terms developers naturally use when seeking help in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | The JPA/Hibernate + Spring Boot focus is fairly specific, but could overlap with a general Spring Boot skill, a database/SQL skill, or a broader Java patterns skill. The combination of terms helps but the lack of explicit boundary-setting leaves some conflict risk. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong reference skill that covers JPA/Hibernate patterns comprehensively with concrete, executable code examples and minimal verbosity. Its main weaknesses are the lack of explicit validation/verification steps for potentially destructive operations (migrations, batch writes) and the monolithic structure that could benefit from splitting deeper topics into referenced files. Overall it serves well as a quick-reference guide for Spring Boot data access patterns.
Suggestions
Add explicit validation steps for the migration section (e.g., dry-run migration, verify schema state, rollback procedure) to improve workflow clarity for destructive operations.
Consider splitting deeper topics (caching strategies, migration workflows, advanced query optimization) into separate referenced files to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude knows what JPA, Hibernate, and Spring Boot are, jumping straight into patterns with executable code. No unnecessary explanations of basic concepts. Every section delivers actionable content without padding. | 3 / 3 |
Actionability | Nearly every section includes concrete, executable Java code or configuration properties. Entity design, repository patterns, transactions, pagination, and connection pooling all have copy-paste ready examples. The few bullet-point sections (caching, migration) provide specific, actionable guidance even without code. | 3 / 3 |
Workflow Clarity | This is primarily a reference/patterns skill rather than a multi-step workflow, so strict sequencing is less critical. However, the sections on batch writes mention `saveAll` and `hibernate.jdbc.batch_size` without validation steps, and the migration section lacks a concrete workflow with verification checkpoints for what could be a destructive operation. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers covering distinct topics, making it easy to scan. However, it's a fairly long monolithic file (~100+ lines of dense content) with no references to external files for deeper topics like caching strategies, migration patterns, or advanced query optimization that could benefit from separate documents. | 2 / 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
- affaan-m/everything-claude-code
- Commit
5df943e
- 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.