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:ysyecust/everything-claude-code --skill jpa-patterns74
Quality
61%
Does it follow best practices?
Impact
100%
1.14xAverage score across 3 eval scenarios
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/jpa-patterns/SKILL.mdDiscovery
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 trigger terms are adequate but could include more user-facing variations.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when working with JPA entities, Hibernate mappings, Spring Data repositories, or when the user mentions ORM, entity relationships, or database persistence in Spring Boot.'
Include common user-facing trigger terms like 'ORM', 'database mapping', '@Entity', 'repository', 'lazy loading', 'N+1 problem', or 'Spring Data JPA'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling. These are all concrete, actionable 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 say, but 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 provides some distinctiveness, but terms like 'query optimization', 'transactions', and 'indexing' could overlap with general database skills or other Spring-related skills. | 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 strong, actionable JPA/Hibernate reference with excellent code examples and efficient token usage. The content covers a broad range of patterns effectively but could improve by adding explicit validation workflows for database operations and better progressive disclosure for advanced topics that deserve deeper treatment.
Suggestions
Add explicit validation/verification steps for migration workflows (e.g., 'Run migration -> Validate schema -> Test queries -> Only then deploy')
Consider splitting advanced topics (caching, migrations, testing) into separate reference files with clear navigation links
Add a feedback loop for batch operations showing how to verify batch writes succeeded and handle partial failures
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only actionable patterns without explaining basic concepts Claude already knows. Every section delivers concrete value without padding or unnecessary context. | 3 / 3 |
Actionability | Provides fully executable Java code examples throughout, including entity design, repository patterns, transactions, and configuration properties. All examples are copy-paste ready with realistic patterns. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, the skill lacks explicit validation checkpoints for risky operations like migrations or batch writes. The migration section mentions best practices but doesn't provide a step-by-step workflow with verification steps. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but it's a monolithic file covering many topics. Complex areas like caching, migrations, and testing could benefit from references to separate detailed files rather than brief inline coverage. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Table of Contents
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.