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.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

A strong, actionable catalog of Spring Boot patterns with executable code throughout, though it reads as a monolithic reference rather than a progressively disclosed skill. The main weaknesses are duplicated prose in the rate-limiting section and the absence of any external reference structure.

Suggestions

De-duplicate the forwarded-headers guidance in the Rate Limiting section — keep it in either the prose "Security Note" or the inline comment, not both, to tighten the token budget.

Move the detailed rate-limiting/security configuration and the retry/resilience patterns into a separate reference file (e.g., references/production-hardening.md) and link to it from SKILL.md to improve progressive disclosure.

Add a brief validation/checklist element (e.g., confirm @EnableCaching/@EnableAsync are present, verify forwarded-headers strategy before relying on getRemoteAddr) so the production-oriented sections have explicit checkpoints.

DimensionReasoningScore

Conciseness

The body is mostly lean, executable code that assumes Claude's competence, but the rate-limiting section duplicates the forwarded-header guidance in both a prose "Security Note" block and a large inline /* SECURITY */ comment.

2 / 3

Actionability

Provides complete, executable Java examples (controllers, repositories, services, filters, caching, async) that are copy-paste ready with concrete annotations and imports.

3 / 3

Workflow Clarity

Sections are well-organized and "When to Activate" gives clear triggers, but this is a reference catalog of patterns rather than a sequenced multi-step workflow, with no explicit validation checkpoints or feedback loops.

2 / 3

Progressive Disclosure

The file is well-structured by section but is a ~320-line monolith with no bundle files or one-level-deep references; content like the detailed rate-limiting/security guidance that could be split out is kept inline.

2 / 3

Total

9

/

12

Passed

Description

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.

A concise, third-person description that names concrete capabilities and pairs them with an explicit use-trigger, covering both what and when clearly. It is distinctively scoped to Spring Boot backend work with natural trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "REST API design, layered services, data access, caching, async processing, and logging" — rather than vague abstractions.

3 / 3

Completeness

Explicitly answers both what it does (architecture patterns and the listed capabilities) and when to use it via the "Use for Java Spring Boot backend work" trigger.

3 / 3

Trigger Term Quality

Uses natural terms a user would say ("Spring Boot", "REST API", "Java Spring Boot backend") with good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

Scoped to Java Spring Boot backend work — a clear niche unlikely to trigger for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

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.