jpa-patterns

JPA/Hibernate patterns for entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling in Spring Boot. Use when designing JPA entities or relationships, or when a Hibernate query, transaction, or N+1 problem needs fixing.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

68%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 concise, actionable patterns reference with strong code examples and clean sectioning. Its main weakness is the absence of explicit validation/verification feedback loops for batch and migration operations, which caps workflow clarity.

Suggestions

Add an explicit validate-then-proceed loop for migrations (e.g., run Flyway/Liquibase on a staging DB, verify schema, then apply) to lift workflow clarity above 3.

For batch writes, include a concrete checkpoint example showing batch_size setting plus a verification query or row-count assertion.

Either make cursor pagination actionable with a short JPQL example or move it to a brief note so the actionable sections stay copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Lean and code-heavy with minimal prose; it does not re-explain JPA/Hibernate concepts Claude already knows. A few introductory lines ('Use for data modeling, repositories, and performance tuning') slightly restate the description, keeping it just shy of a 5.	4 / 5
Actionability	Mostly executable, copy-paste-ready Java entities, repository interfaces, JPQL queries, and HikariCP properties cover common cases. Minor gaps (e.g., cursor pagination described in prose, batch_size without a full example) prevent a 5.	4 / 5
Workflow Clarity	The body is a topic-organized patterns catalog rather than a sequenced workflow, and sections touching batch writes and migrations ('avoid dropping columns without plan', 'saveAll') lack explicit validation/verification feedback loops, capping this dimension at 3.	3 / 5
Progressive Disclosure	A single self-contained SKILL.md with clear, well-organized section headers and no nested references; structure is good, though some detailed subsections (e.g., HikariCP config, caching) could optionally live in reference files.	4 / 5
	Total	15 / 20 Passed

Description

92%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 strong, specific description that clearly communicates capabilities and explicit activation triggers with low conflict risk. Only minor improvement possible in trigger-term synonym coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas — 'entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling' — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly states both what it does (JPA/Hibernate patterns across many concerns) and when to use it via a concrete 'Use when designing JPA entities or relationships, or when a Hibernate query, transaction, or N+1 problem needs fixing' clause.	5 / 5
Trigger Term Quality	Natural developer phrases like 'designing JPA entities or relationships' and 'Hibernate query, transaction, or N+1 problem' map well to what users say, though a few common synonyms (e.g., 'Spring Data', 'ORM') are absent.	4 / 5
Distinctiveness Conflict Risk	The JPA/Hibernate in Spring Boot niche is specific with distinct triggers, making conflict with unrelated skills minimal.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: skills/jpa-patterns/SKILL.md
Commit: d8409a4

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.