CtrlK
BlogDocsLog inGet started
Tessl Logo

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. Use when building or reviewing a Spring Boot backend — REST layer, services, data access, caching, or async work.

63

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, code-first pattern catalog with concrete, mostly executable examples and clear section structure. The main costs are token efficiency (the forwarded-header security material is explained three times, and standard Spring boilerplate is restated) and a monolithic single-file layout that has outgrown its SKILL.md overview role.

Suggestions

State the forwarded-header security guidance once — keep the prose checklist and trim the ~20-line block comment and inline comment in RateLimitFilter to a one-line pointer ("see security note above").

Split deep-dive topics (rate limiting/proxy trust, observability, retry/resilience) into references/ files (e.g. references/rate-limiting.md) linked one level deep from SKILL.md, keeping only quick patterns inline.

Complete or trim stub examples: give the retry and async snippets realistic bodies or drop them in favor of the fully executable controller/service/repository examples, and note required dependencies (Bucket4j, Micrometer).

DimensionReasoningScore

Conciseness

The body is mostly lean code snippets, but the X-Forwarded-For / forwarded-headers security guidance is repeated three times (prose numbered list, a ~20-line block comment, and an inline comment), and several snippets re-teach standard Spring idioms Claude already knows. Mostly efficient, but noticeably tighten-able — anchor 3 rather than 4.

3 / 5

Actionability

Concrete, mostly executable Java for controllers, repositories, services, DTOs, caching, filters, and rate limiting, with prerequisites flagged ("Requires `@EnableCaching` on a configuration class"). Minor gaps keep it from 5: stub bodies ("// send email/SMS", "// logic"), undefined helpers (MarketEntity.from, ApiError), and no stated Bucket4j dependency.

4 / 5

Workflow Clarity

This is a pattern catalog rather than a multi-step process; sections are unambiguous, activation conditions and prerequisites are explicit, and the security section sequences its checklist conditions clearly. No destructive or batch operations exist that would demand validation checkpoints, so it sits at 'clear guidance with minor gaps' rather than 5 (there is no explicit sequence/checkpoint structure to reward) or 3 (nothing is unclear).

4 / 5

Progressive Disclosure

The skill is a single ~310-line file with no references/, scripts/, or assets/ directories. Headers make it navigable, but at this length heterogeneous deep dives (the rate-limiting security discussion, observability, retry logic) would be better split into one-level-deep reference files; the under-50-lines exception for scoring 5 on sections alone does not apply.

3 / 5

Total

14

/

20

Passed

Description

87%Weight 40%Scale 1-5

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

A strong description that clearly and explicitly states both capabilities and activation triggers with a well-defined Spring Boot niche. Its only weaknesses are that capabilities are phrased as topic areas rather than actions and a few natural synonyms are absent.

DimensionReasoningScore

Specificity

Lists several concrete capability areas — "REST API design, layered services, data access, caching, async processing, and logging" — but names domains rather than actions and omits topics the body covers (validation, exception handling, pagination), so it matches 'several specific actions; minor gaps' rather than the comprehensive anchor.

4 / 5

Completeness

Explicitly answers both what ("Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging") and when ("Use when building or reviewing a Spring Boot backend — REST layer, services, data access, caching, or async work") with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Good natural keyword coverage ("Spring Boot", "Java Spring Boot backend", "REST", "caching", "async work", "building or reviewing") but missing common synonyms and variations such as "Spring", "Java backend", or "REST API", so it stops short of the comprehensive-synonyms anchor.

4 / 5

Distinctiveness Conflict Risk

"Java Spring Boot backend" is a clear niche with distinct triggers (framework name plus concrete layer keywords); overlap risk with generic Java or non-Java skills is minimal.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

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.