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).
86
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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 trigger term coverage and completeness. 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 outputs or transformations performed.
Suggestions
Add more specific concrete actions to the 'what' portion, e.g., 'Defines entity relationships, configures field annotations like @Column and @ManyToOne, sets up repository query methods' instead of the more general 'rules and guidelines for working with Spring Data JPA'.
| 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 specify things 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 changes in this domain. | 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 |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured routing skill that efficiently directs Claude through three distinct JPA-related workflows with clear sequencing and conditional logic. Its main weakness is that nearly all actionable content is delegated to reference files that cannot be verified, and the skill provides no inline fallback guidance or summary of key rules. The review output template is a strong concrete element, but the entity and transaction workflows lack any inline examples or key constraints.
Suggestions
Add a brief inline summary of the most critical entity/transaction rules (2-3 key constraints each) so Claude has actionable guidance even before reading reference files
Include a bundle file listing or navigation section that describes what each referenced file contains (e.g., 'entity-conventions.md: detection steps for ID strategy, naming, annotation style')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what JPA is, what entities are, or how Spring Data works. Every line serves a purpose — routing to the right reference file or defining a specific output format. No wasted tokens. | 3 / 3 |
Actionability | The skill provides clear routing logic (check memory → read conventions → read rules) and a concrete output format for reviews, but all actual implementation details are delegated to reference files. The skill itself contains no executable code, specific commands, or concrete examples of entity code. The review output template is actionable, but the core guidance is indirect. | 2 / 3 |
Workflow Clarity | Each workflow (entity creation/modification, review, transactions) has a clearly sequenced multi-step process with conditional logic (check memory first, then detect conventions, then apply rules). The review workflow includes an explicit output format. Steps are numbered and unambiguous. | 3 / 3 |
Progressive Disclosure | The skill references four external files (entity-conventions.md, entity-rules-impl.md, transaction-conventions.md, transaction-rules-impl.md) which is good progressive disclosure structure. However, no bundle files were provided to verify these references exist, and the references directory structure is not clearly signaled with a navigation overview. The skill also lacks any quick-start or inline summary of what those files contain. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
100%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
4d8e766
- 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.