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.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

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

A tight, highly actionable reference with executable examples and excellent token efficiency; its only gap is the absence of explicit validation/verification checkpoints for destructive and batch operations.

Suggestions

Add explicit validation steps for destructive/batch paths (e.g., 'After saveAll, verify row counts'; 'Test migrations on a copy before applying to production').

For migrations, include a feedback loop (apply -> verify -> rollback if errors) to lift workflow clarity into the top band.

DimensionReasoningScore

Conciseness

Lean and efficient throughout—short directive bullets and code with no padding, no explanation of concepts Claude already knows; every token earns its place.

5 / 5

Actionability

Fully executable Java/Spring code and concrete property examples cover the common cases (entities, JOIN FETCH, projections, @Transactional, PageRequest, HikariCP).

5 / 5

Workflow Clarity

Clear sectioned guidance, but batch/destructive operations (migrations, saveAll batching, status updates) lack explicit validation checkpoints or feedback loops, which the rubric penalizes for such contexts.

4 / 5

Progressive Disclosure

A single, well-organized SKILL.md with clear section headers and no external references needed; the simple-skill exception applies, so well-organized sections earn the top score.

5 / 5

Total

19

/

20

Passed

Description

71%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-scoped description that clearly names its JPA/Hibernate capabilities, but it omits an explicit 'Use when...' trigger clause, which limits completeness and keeps it from the top band.

Suggestions

Add an explicit 'Use when...' clause listing concrete user-side triggers (e.g., 'Use when designing JPA entities, fixing N+1 queries, or tuning Spring Boot data access').

Include a few more natural trigger terms and synonyms users actually say (e.g., 'N+1', 'lazy loading', 'Spring Data repositories').

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities—'entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling'—giving comprehensive coverage of the JPA domain.

5 / 5

Completeness

The 'what' is clearly stated but there is no explicit 'Use when...' trigger clause; per the rubric a missing trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Good natural keyword coverage ('entities', 'relationships', 'N+1' implied via query optimization, 'transactions', 'pagination', 'pooling') but a few common synonyms and file/annotation triggers are missing.

4 / 5

Distinctiveness Conflict Risk

The JPA/Hibernate + Spring Boot niche is clearly distinct with specific triggers, with only minor overlap risk against broader Spring skills.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

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.