springboot-patterns
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.
Install with Tessl CLI
npx tessl i github:ysyecust/everything-claude-code --skill springboot-patterns85
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
85%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 around Spring Boot development with specific capabilities listed. It includes an explicit 'Use for' clause that provides clear trigger guidance. The main weakness is that trigger terms could be expanded to include more natural variations users might say.
Suggestions
Expand trigger terms to include common variations like 'Spring', '@RestController', 'JPA', 'microservices', or 'Spring MVC' that users might naturally mention
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'architecture patterns, REST API design, layered services, data access, caching, async processing, and logging' - these are distinct, concrete technical capabilities. | 3 / 3 |
Completeness | Clearly answers both what (architecture patterns, REST API design, layered services, etc.) AND when ('Use for Java Spring Boot backend work') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes good technical terms like 'Spring Boot', 'REST API', 'Java', but missing common variations users might say like 'Spring', 'backend API', 'microservices', 'JPA', 'repository pattern', or '@RestController'. | 2 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting specifically 'Java Spring Boot backend work' - unlikely to conflict with generic Java skills, frontend skills, or other backend frameworks like Node.js or Django. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable Spring Boot reference with excellent code examples that respect Claude's intelligence. The main weaknesses are the lack of explicit workflow sequences for complex multi-step setups and the monolithic structure that could benefit from progressive disclosure to separate files for advanced topics like observability configuration or testing patterns.
Suggestions
Add a workflow section showing the sequence for setting up a new Spring Boot service from scratch with validation checkpoints (e.g., verify each layer works before adding the next)
Split advanced topics like observability configuration, Kafka integration, and testing patterns into referenced files to reduce cognitive load and enable deeper coverage
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing executable code examples without explaining basic Spring concepts Claude already knows. Every section delivers actionable patterns without padding. | 3 / 3 |
Actionability | All code examples are complete, executable Java with proper annotations, imports implied by context, and realistic implementations. The patterns are copy-paste ready with clear structure. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, the skill lacks explicit workflow sequences for multi-step processes like setting up a new service or migrating existing code. No validation checkpoints are provided for operations like cache configuration or async setup. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but it's a monolithic file with no references to external documentation for advanced topics like Kafka integration, detailed observability setup, or testing patterns that could benefit from separate files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 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.