spring-data-jpa
Implement persistence layers with Spring Data JPA. Use when creating repositories, configuring entity relationships, writing queries (derived and @Query), setting up pagination, database auditing, transactions, UUID primary keys, multiple databases, and database indexing. Covers repository interfaces, JPA entities, custom queries, relationships, and performance optimization patterns.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill spring-data-jpaOverall
score
84%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 an excellent skill description that follows best practices. It uses third person voice, provides comprehensive specific actions, includes an explicit 'Use when' clause with extensive trigger terms, and clearly defines its niche within the Spring Data JPA domain. The description would allow Claude to confidently select this skill when users need JPA-related persistence help.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'creating repositories, configuring entity relationships, writing queries (derived and @Query), setting up pagination, database auditing, transactions, UUID primary keys, multiple databases, and database indexing.' Also covers 'repository interfaces, JPA entities, custom queries, relationships, and performance optimization patterns.' | 3 / 3 |
Completeness | Clearly answers both what ('Implement persistence layers with Spring Data JPA') and when ('Use when creating repositories, configuring entity relationships, writing queries...'). The explicit 'Use when' clause provides comprehensive trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Spring Data JPA', 'repositories', 'entity relationships', 'queries', '@Query', 'pagination', 'database auditing', 'transactions', 'UUID primary keys', 'JPA entities', 'custom queries'. These are terms developers naturally use when working with this technology. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on Spring Data JPA persistence. The combination of 'Spring Data JPA', '@Query', 'JPA entities', and 'repository interfaces' creates distinct triggers unlikely to conflict with general database or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid Spring Data JPA skill with excellent actionability through complete, executable code examples covering repositories, entities, pagination, and auditing. The main weaknesses are moderate verbosity in introductory sections and missing validation/verification steps for database operations. The structure and progressive disclosure are well-executed.
Suggestions
Remove or significantly condense the 'When to Use' section - Claude can infer appropriate usage from the instructions themselves
Add validation checkpoints such as: verifying entity mappings with integration tests, checking query results, and validating schema migrations before proceeding
Condense the 'Overview' paragraph which largely repeats what the detailed instructions cover
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient but includes some unnecessary explanation like the 'When to Use' section that largely restates what Claude would infer from context. The 'Overview' section is also somewhat redundant given the detailed instructions that follow. | 2 / 3 |
Actionability | Provides fully executable Java code examples throughout - repository interfaces, entity configurations, pagination implementation, and auditing setup are all copy-paste ready with proper annotations and complete method signatures. | 3 / 3 |
Workflow Clarity | Steps are listed clearly for creating repositories and configuring entities, but lacks validation checkpoints. For database operations, there's no guidance on verifying entity mappings work correctly, testing queries, or handling migration issues before deployment. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections progressing from basic to advanced. References to external documentation (examples.md, reference.md) are clearly signaled at the end, maintaining one-level-deep navigation. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 12 / 16 Passed | |
- 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.