springboot-patterns

Spring Boot 架构模式、REST API 设计、分层服务、数据访问、缓存、异步处理和日志记录。适用于 Java Spring Boot 后端工作。

Install with Tessl CLI

npx tessl i github:affaan-m/everything-claude-code --skill springboot-patterns

What are skills?

Review — 64%

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/skill

Learn more

Validation — 11 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

50%

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

The description adequately identifies the Spring Boot domain and lists relevant technical areas, but lacks concrete action verbs and explicit trigger phrases. The 'when to use' clause is present but too generic ('适用于 Java Spring Boot 后端工作') to effectively guide skill selection among similar backend or Java skills.

Suggestions

Add explicit trigger phrases with a 'Use when...' clause listing natural user terms like 'Spring Boot project', 'Java backend', 'REST endpoint', '@Service', '@Repository', 'Spring annotations'

Convert topic areas into concrete actions with verbs: 'Creates REST controllers', 'Implements service layers', 'Configures Redis caching', 'Sets up async methods with @Async'

Add file type triggers like '.java files', 'pom.xml', 'application.properties' to improve distinctiveness from generic backend skills

Dimension	Reasoning	Score
Specificity	Names the domain (Spring Boot) and lists several actions/concepts (REST API design, layered services, data access, caching, async processing, logging), but these are more like topic areas than concrete actions with verbs.	2 / 3
Completeness	Has a 'what' (architecture patterns, REST API design, etc.) and a brief 'when' clause ('适用于 Java Spring Boot 后端工作'), but the trigger guidance is generic rather than explicit about user phrases or scenarios.	2 / 3
Trigger Term Quality	Includes relevant keywords like 'Spring Boot', 'REST API', 'Java', but missing common variations users might say such as 'backend API', 'microservices', 'Spring framework', '@RestController', or file extensions like '.java'.	2 / 3
Distinctiveness Conflict Risk	Specifies Spring Boot and Java which provides some distinction, but could overlap with general Java skills, generic backend skills, or REST API skills that aren't Spring-specific.	2 / 3
	Total	8 / 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 skill with excellent code examples that are production-ready and concise. The main weaknesses are the lack of explicit workflow guidance for building services end-to-end and the monolithic structure that could benefit from progressive disclosure to separate reference files for advanced topics.

Suggestions

Add a brief workflow section at the top showing the recommended order for building a new feature (e.g., '1. Define DTO → 2. Create Entity → 3. Add Repository → 4. Implement Service → 5. Create Controller')

Split detailed topics like rate limiting security considerations and observability setup into separate reference files (e.g., SECURITY.md, OBSERVABILITY.md) with clear links from the main skill

Add validation checkpoints for common operations (e.g., 'After creating repository, verify with integration test before proceeding to service layer')

Dimension	Reasoning	Score
Conciseness	The skill is highly efficient with minimal explanatory text. It jumps directly into executable code examples without explaining what Spring Boot, REST APIs, or JPA are. Every section provides concrete patterns without padding.	3 / 3
Actionability	All code examples are complete, executable Java code with proper annotations, imports implied by context, and realistic implementations. The examples are copy-paste ready and cover real production patterns like pagination, caching, and exception handling.	3 / 3
Workflow Clarity	While individual patterns are clear, there's no explicit workflow for building a complete service or validation checkpoints. The skill presents isolated patterns without guidance on sequencing (e.g., 'first create entity, then repository, then service, then controller') or verification steps.	2 / 3
Progressive Disclosure	The content is well-organized with clear section headers, but it's a monolithic document (~200 lines) that could benefit from splitting detailed topics (like rate limiting security considerations or observability setup) into separate reference files. No external file references are provided.	2 / 3
	Total	10 / 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.

Reviewed: 8 days 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.