CtrlK
BlogDocsLog inGet started
Tessl Logo

jpa-patterns

JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot.

91

1.28x
Quality

81%

Does it follow best practices?

Impact

98%

1.28x

Average score across 6 eval scenarios

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

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 solid JPA/Hibernate reference skill that provides concrete, executable patterns across entity design, relationships, repositories, transactions, and performance tuning. Its main strengths are conciseness and actionability with real Java code examples. Weaknesses include the lack of progressive disclosure to separate detailed topics and missing explicit validation/verification steps in areas like migration and testing workflows.

Suggestions

Consider splitting deeper topics (caching strategies, migration patterns, testing setup) into separate referenced files to improve progressive disclosure and keep the main skill focused on the most common patterns.

Add explicit validation steps to the migration section (e.g., 'Run flyway validate after applying migrations') and testing section (e.g., 'Assert query count to verify no N+1') to improve workflow clarity.

DimensionReasoningScore

Conciseness

The content is lean and efficient throughout. It assumes Claude knows what JPA, Hibernate, and Spring Boot are, and jumps straight into patterns with executable code. Brief bullet-point guidance accompanies code without over-explaining concepts.

3 / 3

Actionability

Nearly every section includes concrete, copy-paste-ready Java code or configuration properties. Entity design, repository patterns, transactions, pagination, and connection pooling all have executable examples with specific annotations and query syntax.

3 / 3

Workflow Clarity

This is a reference/patterns skill rather than a multi-step workflow, so sequential ordering is less critical. However, the migration and testing sections lack validation checkpoints (e.g., no explicit steps for verifying migration success or checking for N+1 queries in tests), and the overall structure reads as a collection of tips rather than a guided process.

2 / 3

Progressive Disclosure

The content is well-organized with clear section headers covering distinct topics, but it's a fairly long monolithic file with no references to external files for deeper topics like caching strategies, migration patterns, or advanced query optimization. Some sections (e.g., caching, migration) are thin and could either be expanded in separate files or removed.

2 / 3

Total

10

/

12

Passed

Description

82%

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 in specificity and trigger term coverage, listing numerous concrete JPA/Hibernate topics that align well with natural developer queries. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know precisely when to select this skill over others. The domain is well-scoped and distinctive.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks about JPA entities, Hibernate mappings, ORM queries, database relationships in Spring Boot, or mentions @Entity, @Repository, JPQL, or HQL.'

DimensionReasoningScore

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

Clearly answers 'what does this do' by listing JPA/Hibernate patterns and specific areas, 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', 'Spring Boot', 'entity', 'relationships', 'query optimization', 'transactions', 'auditing', 'pagination', 'pooling'. These are terms developers naturally use when seeking help in this domain.

3 / 3

Distinctiveness Conflict Risk

The combination of JPA/Hibernate with Spring Boot creates a clear, distinct niche. The specific mention of ORM-related concerns (entity design, relationships, query optimization) makes it unlikely to conflict with general Spring Boot or database skills.

3 / 3

Total

11

/

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.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
affaan-m/everything-claude-code
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.