jpa-patterns
JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.
86
68%
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
57%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 excels at listing specific technical capabilities and includes strong domain-specific trigger terms that developers would naturally use. However, it critically lacks any 'Use when...' guidance, making it incomplete for Claude's skill selection process. Adding explicit trigger conditions would significantly improve its effectiveness.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about JPA entities, Hibernate mappings, database relationships in Spring Boot, or ORM-related query performance issues.'
Include boundary conditions to distinguish from general Spring Boot or database skills, e.g., 'Not for raw SQL queries, NoSQL databases, or non-JPA data access patterns.'
| 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 areas. | 3 / 3 |
Completeness | Describes 'what' (JPA/Hibernate patterns for various concerns) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause should cap completeness at 2, and since the 'when' is entirely absent, this scores a 1. | 1 / 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 terms developers naturally use when seeking help in this domain. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of JPA/Hibernate with Spring Boot is fairly specific, but it could overlap with general Spring Boot skills, database skills, or ORM-related skills. The lack of explicit trigger boundaries increases conflict risk. | 2 / 3 |
Total | 9 / 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 provides concrete, executable JPA/Hibernate patterns with excellent conciseness and actionability. Its main weaknesses are the lack of explicit validation/feedback loops for destructive operations (migrations, batch writes) and the monolithic structure that could benefit from splitting advanced topics into separate files. The content effectively covers a broad range of JPA concerns while respecting Claude's existing knowledge.
Suggestions
Add explicit validation steps for migrations (e.g., 'Run flyway validate before applying; if errors, fix and re-validate') and batch operations to improve workflow clarity.
Consider splitting caching, migrations, and testing guidance into separate referenced files to improve progressive disclosure for this breadth of content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient throughout. It assumes Claude knows Java, Spring Boot, and JPA concepts, providing only the specific patterns and configurations needed without explaining what JPA or Hibernate is. Every section delivers actionable code or concise guidance without padding. | 3 / 3 |
Actionability | Nearly every section includes executable, copy-paste-ready Java code or configuration properties. Entity design, repository patterns, JOIN FETCH queries, transaction usage, pagination, HikariCP config, and test logging are all concrete and specific. | 3 / 3 |
Workflow Clarity | This is a reference/patterns skill rather than a multi-step workflow, so strict sequencing is less critical. However, sections like migration and batch operations lack explicit validation checkpoints or feedback loops (e.g., no 'validate migration before applying' step), and the overall structure is more of a catalog than a guided workflow. | 2 / 3 |
Progressive Disclosure | The content is well-organized with clear section headers covering distinct topics, making it easy to scan. However, at ~100+ lines with multiple distinct concerns (entity design, caching, migrations, testing, pooling), some sections like caching, migrations, and testing could be split into separate reference files. No bundle files exist to offload detail. | 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
841beea
- 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.