CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

59

Quality

74%

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 ./.kiro/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.

The body is a well-organized catalog of executable Spring Boot patterns with concrete code for each concern. Main weaknesses are the duplicated security prose in the rate-limiting section and the absence of any progressive-disclosure structure for the deeper configuration material.

Suggestions

Remove the duplication between the prose 'Security Note' and the block comment in the Rate Limiting section, keeping one authoritative explanation.

Move the detailed forwarded-header/proxy configuration guidance (and possibly the full pattern catalog) into a references/ file linked from a short inline summary.

Define or reference the supporting types (ApiError, Market/MarketEntity) or note them as project-specific to make examples fully copy-paste ready.

DimensionReasoningScore

Conciseness

Mostly lean, code-forward content with no basic-concept padding, but the Rate Limiting section states the X-Forwarded-For/proxy guidance twice (a prose security note plus a near-identical block comment), which is unnecessary explanation that could be tightened.

3 / 5

Actionability

Provides concrete, near-copy-paste Java for controllers, repositories, services, DTOs, exception handling, caching, retries, and rate limiting, with minor gaps such as undefined ApiError, Market/MarketEntity, and omitted imports.

4 / 5

Workflow Clarity

A 'When to Activate' list scopes the skill and each section states prerequisites ('Requires @EnableCaching on a configuration class'), giving a clear structure; no validation checkpoints are present but the skill involves no destructive or batch operations, so the cap does not apply.

4 / 5

Progressive Disclosure

All ~320 lines are inline with no bundle files or external references; sections are well-organized, but deep-dive content like the proxy/forwarded-header configuration belongs in a one-level-deep reference file, matching the 'content that should be separate is inline' anchor.

3 / 5

Total

14

/

20

Passed

Description

75%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.

The description clearly states what the skill covers and when to use it, with distinctive Spring Boot trigger terms. It could be improved by using action verbs, adding trigger synonyms (Spring MVC, JPA, endpoints), and slightly narrowing the broad caching/logging claims.

Suggestions

Reframe capability areas with action verbs, e.g. 'Design REST APIs, structure controller-service-repository layers, configure JPA and caching'.

Add trigger synonyms users naturally say, such as 'Spring', 'Spring MVC', 'JPA', or 'Spring endpoints', to the 'Use for' clause.

Make the 'when' clause more concrete, e.g. 'Use when building or modifying Java Spring Boot services, REST controllers, or repository layers'.

DimensionReasoningScore

Specificity

Lists seven specific capability areas ('REST API design, layered services, data access, caching, async processing, and logging') but as noun phrases without action verbs, so it is above the 1-2-concrete-actions anchor yet below the comprehensive concrete-actions anchor.

4 / 5

Completeness

Has both a clear 'what' (the enumerated capability areas) and an explicit trigger ('Use for Java Spring Boot backend work'), but the single terse 'when' clause lacks the multiple concrete trigger phrases of the top anchor.

4 / 5

Trigger Term Quality

Includes natural terms users would say ('Spring Boot', 'REST API', 'Java', 'backend') but misses common variations like 'Spring', 'Spring MVC', 'JPA', or 'endpoint', matching the good-coverage-with-a-few-missing anchor.

4 / 5

Distinctiveness Conflict Risk

'Java Spring Boot backend' carves a clear niche, but generic terms like 'caching' and 'logging' create minor overlap risk with broader Java/backend skills, fitting the mostly-distinct anchor rather than minimal-conflict.

4 / 5

Total

16

/

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

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

.kiro/skills/springboot-patterns/SKILL.md

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.