jpa-patterns

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

1.28x

Quality

75%

Does it follow best practices?

Impact

98%

1.28x

Average score across 6 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/ja-JP/skills/jpa-patterns/SKILL.md

Quality

Content

90%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 dense, highly actionable reference: every section pairs a concrete, executable example with terse directive guidance, and nothing pads or over-explains. Its only structural weaknesses are the absence of explicit validation checkpoints for risky operations and the monolithic single-file layout, where a few sections could be externalized as one-level-deep references.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive: short Japanese bullets plus executable code/properties snippets with no explanation of concepts Claude already knows (e.g. no 'JPA is a specification that...' padding). Every section earns its tokens, matching the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	Guidance is copy-paste ready: a complete audited entity, @EnableJpaAuditing config, JOIN FETCH repository query, projection interface, @Transactional service method, PageRequest usage, and concrete HikariCP/logging properties. Common cases are covered with concrete snippets (e.g. 'JPQLに id > :lastId を含める'), matching the fully-executable anchor.	5 / 5
Workflow Clarity	This is a patterns reference rather than a multi-step procedure, and its sections are clearly organized with concrete sequencing advice (enable auditing before using @CreatedDate, prefer Testcontainers, avoid auto-DDL in production). It sits below 5 because there are no explicit validation checkpoints or feedback loops for the riskier operations it touches (migrations, batch writes), matching 'clear sequence with most checkpoints present; minor validation gaps'.	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent), so all content is inline and consistently structured with clear section headers, matching 'good structure; most content is appropriately placed'. It is not a 5 because at ~135 lines with no external references, material like the HikariCP property blocks or the testing/logging details could be split into one-level-deep reference files per the rubric's structure expectations.	4 / 5
	Total	18 / 20 Passed

Description

61%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 domain-specific, information-dense description that clearly scopes what the skill covers, but it lacks any 'Use when...' trigger clause and states topics rather than actions. Adding explicit trigger conditions and natural synonyms (N+1, Spring Data JPA, HikariCP) would raise both completeness and trigger quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when designing entities, modeling relationships, fixing N+1 queries, or tuning persistence in a Spring Boot/JPA project.'

Convert topic nouns into concrete actions where possible (e.g. 'Design entities, prevent N+1 with JOIN FETCH and DTO projections, configure HikariCP pooling').

Include high-traffic synonyms users naturally say: 'N+1', 'Spring Data JPA', 'repository', 'HikariCP', 'Flyway'.

Dimension	Reasoning	Score
Specificity	The description names the domain and enumerates eight specific topic areas ('entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling'), but frames them as topics via 'patterns for' rather than listing concrete actions, which matches the anchor 'names domain and 1-2 concrete actions, but not comprehensive' rather than the action-listing anchors above.	3 / 5
Completeness	It has a clear 'what' (JPA/Hibernate patterns across listed areas) but no 'Use when...' clause or equivalent explicit trigger guidance, which the judging guidelines state should cap completeness at 3.	3 / 5
Trigger Term Quality	Good keyword coverage with natural terms users would say ('JPA/Hibernate', 'Spring Boot', 'transactions', 'pagination', 'pooling'), but common variations like 'N+1', 'Spring Data JPA', 'repository', or 'HikariCP' are missing, matching the 'good coverage; a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	The 'JPA/Hibernate ... in Spring Boot' framing carves out a clear, mostly distinct niche with minimal conflict risk, though it could overlap slightly with generic database or Spring skills, matching 'mostly distinct; minor overlap risk'.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: affaan-m/ECC
Path: docs/ja-JP/skills/jpa-patterns/SKILL.md
Commit: c70874f

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.