CtrlK
BlogDocsLog inGet started
Tessl Logo

springboot-patterns

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

86

1.53x
Quality

66%

Does it follow best practices?

Impact

100%

1.53x

Average score across 6 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./docs/zh-CN/skills/springboot-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

64%Scale 1-3

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 reference skill with excellent actionability—nearly every section has production-quality, executable Java code covering the full Spring Boot stack. Its main weaknesses are the monolithic structure (all patterns inline rather than using progressive disclosure) and the lack of workflow sequencing that would guide Claude through building a complete service. The rate limiting section's security commentary, while valuable, is disproportionately verbose compared to other sections.

Suggestions

Extract detailed sections (rate limiting, caching, async, observability) into separate referenced files and keep SKILL.md as a concise overview with links

Add a brief workflow section at the top showing the recommended order for building a Spring Boot service (e.g., 1. Define DTOs → 2. Create Repository → 3. Build Service → 4. Add Controller → 5. Add exception handling → 6. Verify with tests)

Condense the rate limiting security notes into 2-3 bullet points instead of the current lengthy explanation plus code comments

DimensionReasoningScore

Conciseness

The skill is mostly efficient with executable code examples, but includes some unnecessary explanations Claude would already know (e.g., the lengthy security notes about X-Forwarded-For, explaining what constructor injection is, basic SLF4J logging patterns). The rate limiting section alone has an extensive comment block and preceding explanation that could be significantly condensed.

2 / 3

Actionability

Nearly every section provides fully executable, copy-paste ready Java code with proper annotations, imports implied by context, and realistic patterns. The code examples are complete class/method definitions rather than pseudocode, covering controllers, services, repositories, DTOs, exception handlers, filters, caching, and retry logic.

3 / 3

Workflow Clarity

The skill presents individual patterns clearly but lacks an explicit workflow sequence showing how the layers connect end-to-end. There are no validation checkpoints (e.g., 'verify your API responds correctly', 'run tests after adding exception handler'). The 'When to activate' section lists triggers but doesn't guide through a sequenced process of building a Spring Boot service.

2 / 3

Progressive Disclosure

The content is well-sectioned with clear headers, but it's a monolithic file with ~250 lines of inline code that could benefit from splitting advanced topics (rate limiting, observability, caching) into separate reference files. There are no external file references, and some sections like observability are too brief to be actionable while others like rate limiting are overly detailed for an overview.

2 / 3

Total

9

/

12

Passed

Description

67%Scale 1-3

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 is functional and covers the domain adequately with an explicit 'use when' clause. Its main weaknesses are that the listed capabilities read more as topic areas than concrete actions, and some terms are generic enough to potentially overlap with other backend development skills. Adding more specific trigger terms and concrete actions would strengthen it.

Suggestions

Reframe topic areas as concrete actions, e.g., 'Creates Spring Boot REST controllers, configures JPA repositories, implements caching with @Cacheable, sets up async processing with @Async'.

Add more natural trigger term variations such as 'Spring Framework', 'JPA', 'Hibernate', 'microservices', 'Maven', 'Gradle', '.java files' to improve keyword coverage.

DimensionReasoningScore

Specificity

The description names the domain (Spring Boot) and lists several areas like REST API design, layered services, data access, caching, async processing, and logging. However, these are more like topic areas than concrete actions (e.g., 'designs REST APIs' vs 'REST API设计').

2 / 3

Completeness

The description answers both 'what' (architecture patterns, REST API design, layered services, data access, caching, async processing, logging) and 'when' ('用于Java Spring Boot后端工作' = Use for Java Spring Boot backend work), providing an explicit trigger clause.

3 / 3

Trigger Term Quality

Includes relevant keywords like 'Spring Boot', 'REST API', 'Java', 'caching', and 'logging' which users might naturally mention. However, it misses common variations like 'Spring Framework', 'JPA', 'Hibernate', 'microservices', '@RestController', '.java files', or 'Maven/Gradle'.

2 / 3

Distinctiveness Conflict Risk

While 'Spring Boot' and 'Java' provide some distinctiveness, terms like 'REST API设计', 'caching', 'async processing', and 'logging' are generic enough to overlap with other backend or general programming skills. It could conflict with a general Java skill or a generic REST API skill.

2 / 3

Total

9

/

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

10

/

11

Passed

Repository
affaan-m/ECC
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.