jpa-patterns
JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.
Install with Tessl CLI
npx tessl i github:affaan-m/everything-claude-code --skill jpa-patterns72
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
42%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 within the JPA/Hibernate domain, demonstrating good specificity. However, it critically lacks any 'Use when...' guidance, which is essential for Claude to know when to select this skill over others. The technical terminology is appropriate but could benefit from more user-facing trigger terms.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about JPA entities, Hibernate mappings, database relationships in Spring Boot, or mentions @Entity, @Repository, or ORM patterns.'
Include common user-facing terms and variations such as 'ORM', 'database mapping', 'lazy loading', 'N+1 problem', 'entity relationships', or 'JPA repository queries'.
Add file extension triggers if applicable, such as 'when working with @Entity classes or Spring Data JPA repositories'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling. These are all distinct, concrete capabilities within the JPA/Hibernate domain. | 3 / 3 |
Completeness | Describes what the skill does (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. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'JPA', 'Hibernate', 'Spring Boot', 'entity', 'transactions' that users would naturally mention. However, missing common variations like 'ORM', 'database mapping', 'lazy loading', 'N+1 queries', or '@Entity'. | 2 / 3 |
Distinctiveness Conflict Risk | The JPA/Hibernate + Spring Boot combination creates a reasonably specific niche, but could overlap with general Spring Boot skills, database skills, or Java persistence skills without explicit trigger boundaries. | 2 / 3 |
Total | 8 / 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 high-quality, concise reference skill that provides excellent actionable patterns for JPA/Hibernate in Spring Boot. The code examples are complete and executable, covering entity design through connection pooling. Minor improvements could include explicit validation steps for migrations/batch operations and better progressive disclosure for advanced topics.
Suggestions
Add explicit validation steps for migrations (e.g., 'Run flyway:validate before flyway:migrate, verify with SELECT count(*) queries')
Include a feedback loop for batch operations showing how to verify batch_size is working (check SQL logs for batched inserts)
Consider linking to separate files for advanced topics like second-level caching configuration or complex migration strategies
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient - every section provides concrete patterns without explaining what JPA/Hibernate is or how Spring Boot works. Assumes Claude's competence with Java/Spring ecosystem. | 3 / 3 |
Actionability | Fully executable code examples throughout - entity definitions, repository interfaces, JPQL queries, configuration properties are all copy-paste ready. Specific annotations and property values provided. | 3 / 3 |
Workflow Clarity | Sections are well-organized by concern (entities, relationships, transactions, etc.) but lacks explicit validation checkpoints. For database operations, missing feedback loops for verifying query performance or migration success. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear section headers, but everything is inline in one file. Topics like caching, migrations, and testing could benefit from references to separate detailed guides for complex scenarios. | 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.
- 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.