CtrlK
BlogDocsLog inGet started
Tessl Logo

jpa-patterns

Patrones JPA/Hibernate para diseño de entidades, relaciones, optimización de consultas, transacciones, auditoría, indexación, paginación y pooling en Spring Boot.

63

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./docs/es/skills/jpa-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

The content is highly actionable with executable code throughout and is concisely written assuming Claude's expertise. Its weaknesses are the lack of validation checkpoints for destructive/batch operations and a topic-catalog structure rather than an explicit workflow.

Suggestions

Add an explicit validate→fix→retry loop for migrations (e.g. run Flyway validate, fix, re-run) and for batch writes to lift workflow clarity above the cap.

Trim the closing 'Recuerda' recap or fold its unique points into the relevant sections to remove mild redundancy.

Consider extracting the HikariCP/migration reference tables into a separate reference file to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — no explanations of what JPA/Hibernate or an entity is — with the only mild redundancy being the closing 'Recuerda' recap that restates N+1, indexing, and short-transaction points already covered.

4 / 5

Actionability

It provides copy-paste-ready executable code across common cases — full @Entity definitions, repository interfaces with @Query, @Transactional service methods, PageRequest usage, and concrete HikariCP properties — matching the anchor for fully executable, specific examples.

5 / 5

Workflow Clarity

Content is organized as a topic catalog with a rough progression (entities → relationships → repositories → transactions → paging → indexing → pooling → cache → migrations → testing), but destructive/batch operations like migrations and saveAll lack validation checkpoints, so per the guideline workflow clarity is capped at 3.

3 / 5

Progressive Disclosure

No bundle files exist and the skill is a single self-contained file with clear ## section headers and no nested references; it is well-organized, though at >50 lines some sections (e.g. HikariCP config, migration guidance) could optionally be split into references.

4 / 5

Total

16

/

20

Passed

Description

75%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.

The description is specific and distinctive, naming a clear JPA/Hibernate niche with comprehensive capability coverage and natural trigger terms. Its main weakness is the absence of an explicit 'when to use' clause, which caps completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Úsalo para modelado de datos, repositorios y ajuste de rendimiento al trabajar con JPA/Hibernate en Spring Boot.'

Add a few natural synonyms users might say ('ORM', 'repositorios', 'mapeo objeto-relacional', 'N+1') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

The description enumerates eight concrete capability areas — 'diseño de entidades, relaciones, optimización de consultas, transacciones, auditoría, indexación, paginación y pooling' — matching the anchor for multiple specific concrete actions with comprehensive coverage.

5 / 5

Completeness

A clear 'what' is present (the listed JPA/Hibernate pattern areas) but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3.

3 / 5

Trigger Term Quality

It includes strong natural terms a developer would say ('JPA', 'Hibernate', 'Spring Boot', 'transacciones', 'paginación', 'pooling'), but omits common synonyms/variations such as 'ORM', 'repositorios', 'mapeo', or 'N+1' that appear in the body.

4 / 5

Distinctiveness Conflict Risk

'Patrones JPA/Hibernate ... en Spring Boot' names a clear niche with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

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.

Validation — 15 / 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/ECC
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.