Name: spring-data-jpa
Rating: 60.8 (1 reviews)
Author: Amplicode

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

70%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/spring-data-jpa/SKILL.md

Quality

Content

50%

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

This skill functions primarily as a routing document that delegates nearly all substantive guidance to reference files. The preflight MCP detection section is well-structured but verbose, and the core workflows are clear in sequence but lack validation checkpoints for entity/transaction modifications. The skill would benefit from including at least minimal inline actionable content (e.g., a quick example of a properly annotated entity) rather than deferring everything to external references.

Suggestions

Add at least one concrete inline example (e.g., a minimal JPA entity with correct annotations) so the skill provides immediate actionable value without requiring reference file reads.

Include validation/verification steps in the entity creation and transaction modification workflows (e.g., 'compile and check for mapping errors' or 'run entity validation tool after changes').

Tighten the preflight section — the three-tier fallback (MCP available → amplicode-install skill → manual instructions) could be condensed into a compact decision table rather than prose paragraphs.

Consider adding a brief summary of what each referenced file contains so Claude can decide whether to read it, rather than always reading the full file.

Dimension	Reasoning	Score
Conciseness	The preflight section is somewhat verbose with detailed fallback instructions and installation steps that could be more compact. The main workflow sections are reasonably lean, but the MCP detection block includes redundant explanation. The review output template is useful but adds some bulk.	2 / 3
Actionability	The skill delegates all concrete implementation details to reference files (entity-conventions.md, entity-rules-impl.md, transaction-conventions.md, transaction-rules-impl.md) rather than providing executable code or specific commands directly. The review output format template is concrete, but the core workflows are essentially 'read this other file and follow it' — making the skill itself a routing document rather than actionable guidance.	2 / 3
Workflow Clarity	The workflows are sequenced (check memory → read conventions → apply rules) and the preflight has a clear decision tree. However, there are no validation checkpoints or feedback loops for entity creation/modification, which are potentially destructive operations. The review workflow is clearer with its explicit output format, but entity/transaction workflows lack verification steps.	2 / 3
Progressive Disclosure	The skill references four separate reference files (entity-conventions.md, entity-rules-impl.md, transaction-conventions.md, transaction-rules-impl.md) which is good progressive disclosure structure. However, since no bundle files were provided, we cannot verify these references exist or are well-structured. The references are one level deep and clearly signaled, but the skill itself is thin — almost too much is delegated, making it hard to assess whether the overall content is appropriately split or just incomplete.	2 / 3
	Total	8 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description with excellent completeness and trigger term coverage. It clearly defines both what the skill does and when to use it, with explicit trigger conditions. The main weakness is that the 'what' portion could be more specific about the concrete actions or guidelines it provides, as 'rules and guidelines' is somewhat vague about the actual content.

Dimension	Reasoning	Score
Specificity	The description names the domain (Spring Data JPA) and mentions several actions like adding/removing/modifying entities, repositories, and projections, but these are described at a category level rather than listing multiple concrete specific actions (e.g., it doesn't mention specific operations like 'define entity relationships', 'configure lazy loading', 'write JPQL queries').	2 / 3
Completeness	Clearly answers both 'what' (rules and guidelines for working with Spring Data JPA) and 'when' (explicit trigger clause: 'ALWAYS use this skill when adding, removing, or modifying JPA entities, repositories, or projections. Trigger on any request that involves...'). The 'when' guidance is detailed and explicit.	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: 'JPA entities', 'repositories', 'projections', 'entity structure', 'field annotations', 'database mappings', 'Spring Data repositories', 'query projections', 'interfaces', 'DTOs'. These are terms a developer would naturally use when requesting JPA-related changes.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche around Spring Data JPA specifically. The trigger terms like 'JPA entities', 'field annotations', 'database mappings', 'Spring Data repositories', and 'query projections' are specific enough to avoid conflicts with general coding or database skills.	3 / 3
	Total	11 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: Amplicode/spring-skills
Commit: 50fc5d2

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