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.

69

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

87%

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

A concise, highly actionable patterns catalog with clean section organization and copy-paste-ready examples. Its main gap is the absence of explicit validation/feedback checkpoints for destructive database operations such as migrations.

Suggestions

Add a validate-then-proceed feedback loop for migrations, e.g. run the migration against a Testcontainers database, assert results, and only then promote — fixing and re-running on failure.

Frame the testing section as an explicit sequence (write test → run with SQL logging on → inspect emitted queries → optimize fetch/index strategy) so the verification path is a clear workflow rather than scattered tips.

DimensionReasoningScore

Conciseness

Lean and code-driven with no explanations of concepts Claude already knows; every section adds pattern-specific guidance that earns its tokens.

3 / 3

Actionability

Provides multiple complete, copy-paste-ready Java examples — entity definitions, repository interfaces, JPQL queries, @Transactional methods, pagination, and HikariCP config — not pseudocode.

3 / 3

Workflow Clarity

Content is organized by topic rather than as a sequenced workflow, and destructive/batch database operations (migrations) lack an explicit validate→fix→retry feedback loop, capping this at 2 per the rubric.

2 / 3

Progressive Disclosure

With no bundle files present, the single SKILL.md is cleanly organized into well-labeled sections with no nested references and easy in-file navigation, which suits a self-contained patterns catalog.

3 / 3

Total

11

/

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.

A specific, well-scoped description with strong trigger terms and low conflict risk, but it omits an explicit 'when to use' trigger clause. Adding a 'Use when...' sentence would lift completeness to 3.

Suggestions

Append an explicit trigger clause, e.g. 'Use when designing JPA entities, optimizing queries, or configuring transactions, auditing, or pooling in Spring Boot.'

Include natural phrasings users often say (e.g. 'N+1 problems', 'lazy loading', 'HikariCP tuning') to strengthen trigger-term matching against conversational requests.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'entity design, relationships, query optimization, transactions, auditing, indexing, pagination, and pooling' — rather than naming only a domain.

3 / 3

Completeness

Comprehensively answers 'what' but lacks an explicit 'Use when...' trigger clause, so 'when' is only implied; per the rubric this caps completeness at 2.

2 / 3

Trigger Term Quality

Includes natural terms a developer would say — 'JPA', 'Hibernate', 'Spring Boot', 'entity', 'transactions', 'pagination', 'pooling' — giving good coverage rather than just a few keywords.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche (JPA/Hibernate in Spring Boot) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
ysyecust/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.