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

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

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and highly actionable, with executable Java patterns and well-organized sections. It loses points for lacking explicit validation checkpoints in any workflow and for being a monolithic single file with no progressive disclosure to separate reference materials.

Suggestions

For the migration and batch-write sections, add an explicit validation/verification step (e.g. 'run the migration in a test environment and assert row counts') to introduce a feedback loop.

Consider splitting the detailed HikariCP configuration and Testcontainers testing setup into a separate reference file referenced from the body, improving progressive disclosure.

Add a short 'When to apply' intro per major section so the reference doubles as a decision guide for which pattern fits which situation.

DimensionReasoningScore

Conciseness

The body is lean and code-focused, jumping straight to executable patterns without explaining JPA/Hibernate basics Claude already knows; the only mild redundancy is the brief closing summary note.

3 / 3

Actionability

It provides concrete, copy-paste-ready Java snippets — entity annotations, @Query repositories, @Transactional service methods, PageRequest, and HikariCP properties — rather than pseudocode or abstract direction.

3 / 3

Workflow Clarity

The document is a thematic reference rather than a sequenced workflow, so steps are organized by topic but lack explicit validation checkpoints or a validate-fix-retry feedback loop for risky operations.

2 / 3

Progressive Disclosure

It is well-organized with clear section headings, but it is a monolithic ~141-line single file with no external references or navigation to progressively disclose deeper material.

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 specific and trigger-rich, naming a clear JPA/Hibernate Spring Boot niche with concrete capability areas. Its main weakness is the absence of an explicit 'Use when...' trigger clause, capping completeness at 2.

Suggestions

Append an explicit trigger clause, e.g. 'Use when designing JPA/Hibernate entities, modeling relationships, optimizing queries, or tuning transactions and pooling in Spring Boot.'

Clarify 'pooling' to 'connection pooling' so the natural trigger term matches what a user would say.

Consider adding 'N+1' or 'lazy loading' as explicit trigger terms since the body emphasizes N+1 prevention.

DimensionReasoningScore

Specificity

The description explicitly enumerates multiple concrete capability areas — 'entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling' — rather than relying on vague language.

3 / 3

Completeness

It clearly states what the skill covers but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

It uses natural terms a developer would actually say — 'JPA', 'Hibernate', 'Spring Boot', 'transactions', 'indexing', 'pagination' — giving good coverage of likely trigger vocabulary.

3 / 3

Distinctiveness Conflict Risk

The 'JPA/Hibernate ... in Spring Boot' framing carves out a clear, distinct niche that is unlikely to trigger for unrelated 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.

Validation16 / 16 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.