spring-boot-crud-patterns
Provide repeatable CRUD workflows for Spring Boot 3 services with Spring Data JPA and feature-focused architecture; apply when modeling aggregates, repositories, controllers, and DTOs for REST APIs.
Install with Tessl CLI
npx tessl i github:giuseppe-trisciuoglio/developer-kit --skill spring-boot-crud-patternsOverall
score
82%
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 a strong skill description that clearly defines its scope (Spring Boot 3 CRUD workflows with JPA) and provides explicit trigger conditions. It uses appropriate technical terminology that developers would naturally use, and the specificity of the technology stack (Spring Boot 3, Spring Data JPA, feature-focused architecture) makes it highly distinctive. The description follows third-person voice correctly.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'CRUD workflows', 'modeling aggregates, repositories, controllers, and DTOs for REST APIs'. These are concrete, actionable capabilities in the Spring Boot domain. | 3 / 3 |
Completeness | Clearly answers both what ('repeatable CRUD workflows for Spring Boot 3 services with Spring Data JPA and feature-focused architecture') and when ('apply when modeling aggregates, repositories, controllers, and DTOs for REST APIs'). Has explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes natural keywords developers would use: 'Spring Boot 3', 'Spring Data JPA', 'CRUD', 'aggregates', 'repositories', 'controllers', 'DTOs', 'REST APIs'. Good coverage of terms a developer would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: Spring Boot 3 + Spring Data JPA + feature-focused architecture. The combination of technology stack and architectural pattern makes it clearly distinguishable from generic coding or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
70%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill demonstrates strong organizational structure and progressive disclosure, with a clear workflow and well-organized references to supporting materials. However, it sacrifices actionability by deferring all concrete code examples to reference files, leaving the main skill as architectural guidance rather than executable instruction. The content could be more concise by trimming explanations of concepts Claude already understands.
Suggestions
Add at least one concrete, executable code snippet in the main skill (e.g., a minimal aggregate class or controller method) to improve actionability without requiring reference file lookup.
Trim the 'When to Use' section - the trigger phrases and detailed scenarios add tokens without proportional value for Claude's task execution.
Remove explanatory phrases like 'to centralize invariants' or 'to enforce type safety' that explain why patterns exist rather than how to implement them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation that Claude would already know (e.g., explaining what constructor injection is, basic Spring concepts). The 'When to Use' section with trigger phrases adds bulk without proportional value. | 2 / 3 |
Actionability | The skill provides structured guidance and workflow steps but lacks executable code examples. It describes patterns abstractly ('Define immutable aggregates with factory methods') rather than showing concrete, copy-paste ready implementations, deferring all code to reference files. | 2 / 3 |
Workflow Clarity | The 7-step quickstart workflow is clearly sequenced with logical progression from structure to testing. Each step has a clear purpose and the final validation step provides a checkpoint. The workflow is appropriate for the complexity of CRUD implementation. | 3 / 3 |
Progressive Disclosure | Excellent structure with clear overview sections and well-signaled one-level-deep references to detailed materials (examples, official docs, generator scripts). The References section provides clear navigation to supporting files with context about what each contains. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
69%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 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
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 | 11 / 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.