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.

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/springboot-patterns/SKILL.md

Quality

Content

65%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, actionable Spring Boot pattern reference with broad executable code coverage. It is held back by duplicated security guidance, no multi-step workflow with validation checkpoints, and a monolithic single-file structure with no progressive disclosure.

Suggestions

De-duplicate the X-Forwarded-For / ForwardedHeaderFilter security guidance: keep it in one place (the blockquote) and trim the long in-code comment to a one-line pointer.

Split the larger sections (rate limiting, retry/resilience, exception handling) into reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

For stateful or destructive patterns (caching evict, retry, scheduled jobs), add explicit validation/verification checkpoints so the workflow-clarity dimension can rise above 3.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code with brief section headers and assumes Claude's Spring Boot competence, but the rate-limiting section duplicates the forwarded-header security guidance in both a blockquote and a large in-code comment, which is trimmable redundancy.	4 / 5
Actionability	Provides concrete, mostly-executable Java code across controllers, repositories, services, DTOs, exception handling, caching, async, logging, filters, retry, and rate limiting, but examples reference undefined helper types (Market, MarketEntity, ApiError) and contain a couple of placeholder comments, leaving minor gaps from fully copy-paste-ready.	4 / 5
Workflow Clarity	The skill is a topical pattern catalog with clear section organization rather than a sequenced multi-step workflow; no end-to-end process with validation checkpoints is present, though the retry example does include a feedback loop.	3 / 5
Progressive Disclosure	Content is well-organized under clear headers but is a monolithic ~310-line single file with no bundle files or one-level-deep references, and material such as the detailed rate-limiting and retry sections could plausibly be split into reference files.	3 / 5
	Total	14 / 20 Passed

Description

73%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 solid, third-person description that names a distinct niche and includes an explicit 'Use for' trigger. Its main limitation is that capabilities are stated as topic categories rather than concrete actions, and the trigger clause is terse rather than richly varied.

Suggestions

Lead with concrete action verbs (e.g., 'Design REST APIs, structure controller→service→service→repository layers, configure JPA and caching') instead of noun-phrase topic lists.

Expand the trigger clause with concrete situations, e.g. 'Use when building or reviewing Java Spring Boot backends, REST APIs, or layered service architectures.'

Dimension	Reasoning	Score
Specificity	Names the Spring Boot domain plus several capability areas ('REST API design, layered services, data access, caching, async processing, and logging'), but these are topic categories rather than concrete action verbs like 'extract' or 'fill', so it stops short of the score-4 anchor.	3 / 5
Completeness	Clearly states what the skill covers (the capability list) and provides an explicit trigger ('Use for Java Spring Boot backend work'), but the 'when' clause is a single terse phrase rather than the concrete, varied trigger phrases the score-5 anchor calls for.	4 / 5
Trigger Term Quality	Includes natural terms a user would actually say — 'Spring Boot', 'REST API', 'Java', 'backend' — giving good keyword coverage, though it misses common synonyms like 'Spring framework' or 'microservices' that the score-5 anchor expects.	4 / 5
Distinctiveness Conflict Risk	'Java Spring Boot backend' carves out a clear, distinct niche with minimal overlap risk, matching the score-5 anchor's 'clear niche with distinct triggers'.	5 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: affaan-m/everything-claude-code
Path: .kiro/skills/springboot-patterns/SKILL.md
Commit: 06c5e11

Reviewed: 2 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.