spring-data-jpa

Rules and guidelines for working with Spring Data JPA in the project. ALWAYS use this skill when adding, removing, or modifying JPA entities, repositories, or projections. Trigger on any request that involves changing entity structure, adding new entities, modifying field annotations, updating database mappings, creating or modifying Spring Data repositories, or defining query projections (interfaces, DTOs).

Quality

81%

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

71%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 well-structured, concise overview that routes the agent to convention-detection and rule files with clear workflows, but its progressive disclosure is undermined by empty and misspelled reference files and an unreferenced repository-conventions.md.

Suggestions

Fill or remove the empty reference files (repository-conventions.md, transaction-conventions.md, transaction-rules-impl.md) and fix the misspelled 'transaction-oregination.md' so every referenced path resolves to real content.

Add a 'Working with Repositories' section that references repository-conventions.md, since the description advertises repository changes as a trigger but the body never routes to it.

Add an explicit verification checkpoint in the 'Reviewing JPA Patterns' workflow (e.g., confirm detected conventions were re-checked against the rules file) to strengthen the feedback loop.

Dimension	Reasoning	Score
Conciseness	Lean body with no concept padding and no over-explanation of JPA/Spring basics, but the multi-paragraph MCP preflight block adds tokens that are not core JPA guidance and could be tightened.	4 / 5
Actionability	Gives concrete, executable steps — explicit reference paths, numbered procedures, and a defined review output template — but delegates most executable detail to the referenced files rather than including it inline.	4 / 5
Workflow Clarity	Clear numbered sequences with a preflight decision branch and a memory-before-read checkpoint; no explicit validate/verify loop, though the operations involved are non-destructive (reading and convention detection).	4 / 5
Progressive Disclosure	The body is an overview with clearly signaled one-level-deep references, but several referenced files (repository-conventions.md, transaction-conventions.md, transaction-rules-impl.md) are empty 0-byte files, a misspelled 'transaction-oregination.md' exists with no body reference, and repository-conventions.md is never referenced at all — so the navigation is partly broken and incompletely organized.	3 / 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 description that clearly states its purpose, enumerates concrete JPA-related actions, and gives explicit trigger guidance with broad keyword coverage. It is well-differentiated and concise without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across the JPA domain — 'adding, removing, or modifying JPA entities, repositories, or projections', 'modifying field annotations', 'updating database mappings', 'defining query projections (interfaces, DTOs)' — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both 'what' ('Rules and guidelines for working with Spring Data JPA') and 'when' ('ALWAYS use this skill when...', 'Trigger on any request that involves...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong keyword coverage ('JPA entities, repositories, or projections', 'field annotations', 'database mappings', 'query projections', 'DTOs'), but a few natural user-colloquial phrasings are missing, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Spring Data JPA entities/repositories/projections) with distinct, specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	19 / 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: Amplicode/spring-skills
Path: skills/spring-data-jpa/SKILL.md
Commit: bf19b3c

Reviewed: 5 days 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.