jpa-patterns
JPA/Hibernate patterns and common pitfalls (N+1, lazy loading, transactions, queries). Use when user has JPA performance issues, LazyInitializationException, or asks about entity relationships and fetching strategies.
82
77%
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 ./.claude/skills/jpa-patterns/SKILL.mdQuality
Discovery
89%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 a strong skill description with excellent trigger terms and completeness. It clearly identifies its niche in JPA/Hibernate troubleshooting and includes an explicit 'Use when' clause with natural developer language. The main weakness is that the 'what' portion describes topics rather than concrete actions Claude will perform.
Suggestions
Rephrase the capabilities as concrete actions, e.g., 'Diagnoses and resolves JPA/Hibernate issues including N+1 query problems, lazy loading exceptions, transaction management, and query optimization' instead of listing topics.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (JPA/Hibernate) and mentions specific concepts (N+1, lazy loading, transactions, queries), but these are more like topic areas than concrete actions. It doesn't list specific actions like 'diagnose N+1 queries', 'configure fetch strategies', or 'resolve LazyInitializationException'. | 2 / 3 |
Completeness | Clearly answers both 'what' (JPA/Hibernate patterns and common pitfalls including N+1, lazy loading, transactions, queries) and 'when' (explicit 'Use when' clause with specific triggers like JPA performance issues, LazyInitializationException, entity relationships, and fetching strategies). | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms that users would actually say: 'JPA performance issues', 'LazyInitializationException', 'entity relationships', 'fetching strategies', 'N+1', 'lazy loading', 'Hibernate'. These cover common variations of how developers describe these problems. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche in JPA/Hibernate-specific concerns. The mention of specific exceptions (LazyInitializationException), patterns (N+1), and the JPA/Hibernate technology stack makes it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, actionable JPA skill with excellent concrete code examples covering the most common pitfalls. Its main weaknesses are the truncated ending (the LazyInitializationException solution 2 is cut off mid-code), lack of explicit validation/verification workflows for performance fixes, and the monolithic structure that could benefit from splitting advanced topics into referenced files.
Suggestions
Complete the truncated content — the LazyInitializationException Solution 2 code block is cut off mid-method, leaving an incomplete skill.
Add an explicit verification workflow: e.g., 'Enable SQL logging → reproduce issue → count queries → apply fix → verify query count reduced → disable verbose logging.'
Split detailed sections (entity relationships, query optimization, transaction management) into separate referenced files to improve progressive disclosure and reduce the main file's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with good use of tables and code examples, but includes some unnecessary commentary (e.g., '> The #1 JPA performance killer') and explanatory comments that Claude would already know. The inline comments explaining what N+1 means ('if 100 authors = 101 queries') add some value for context but border on over-explanation. | 2 / 3 |
Actionability | Provides fully executable Java code examples with repository interfaces, entity annotations, JPQL queries, and configuration YAML. Each solution is copy-paste ready with clear anti-patterns (❌) and correct patterns (✅), plus multiple alternative solutions for each problem. | 3 / 3 |
Workflow Clarity | The quick reference table provides good problem-to-solution mapping, and the N+1 section has a clear detect-then-fix flow with SQL logging configuration. However, there's no explicit validation workflow (e.g., 'enable logging → identify N+1 → apply fix → verify query count reduced'), and the content appears truncated mid-code-block in the LazyInitializationException section, leaving an incomplete workflow. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear headers and a useful quick reference table at the top. However, it's becoming a long monolithic document with no references to separate files for advanced topics (e.g., optimistic locking, projections, pagination). The content also appears truncated, suggesting it may be incomplete. | 2 / 3 |
Total | 9 / 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
- piomin/claude-ai-spring-boot
- Commit
301ea7a
- 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.