backend-patterns

Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.

Quality

63%

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

The body is a well-structured, actionable catalog of backend patterns with concrete executable examples, but it lacks sequenced workflows with validation checkpoints and keeps all content in one large file rather than progressively disclosing deeper references.

Suggestions

Split the pattern categories (API design, database, caching, auth, rate limiting, queues, logging) into separate reference files under ./references/ and link to them from a concise SKILL.md overview.

Add explicit validation/verification checkpoints for the destructive and batch operations (e.g., 'verify cache invalidated after write', 'confirm transaction committed before returning').

Replace placeholder stubs like '// Vector search implementation' and '// Job execution logic' with complete executable code or move them to referenced files.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean TypeScript examples with minimal prose and terse PASS/FAIL annotations, though there is some redundancy (e.g., CachedMarketRepository and Cache-Aside overlap) and a few comment-only stubs that could be trimmed.	4 / 5
Actionability	Provides numerous concrete, mostly copy-paste-ready TypeScript/SQL examples covering common backend cases, with minor gaps where placeholders remain (e.g., '// Other methods...', '// Vector search implementation', '// Job execution logic').	4 / 5
Workflow Clarity	The skill is a patterns catalog with a 'When to Activate' list rather than a sequenced workflow, and the destructive/batch operations (transactions, caching invalidation, DB writes) lack explicit validation checkpoints, which caps this dimension at 3.	3 / 5
Progressive Disclosure	Content is well-organized under clear section headers, but at ~590 lines everything is inlined in a single SKILL.md with no bundle files or one-level-deep references to split the pattern categories out.	3 / 5
	Total	14 / 20 Passed

Description

61%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 identifies the domain and relevant technologies but is topic-oriented rather than action-oriented and omits an explicit 'Use when...' trigger clause, which limits completeness.

Suggestions

Reframe the description around concrete actions (e.g., 'Design and optimize REST/GraphQL APIs, structure repository/service layers, and prevent N+1 queries') instead of topic nouns.

Add an explicit 'Use when...' clause naming the trigger phrases (e.g., 'Use when designing API endpoints, optimizing database queries, or adding caching/middleware').

Include natural synonyms like 'REST endpoints', 'GraphQL', 'N+1 queries', or 'connection pooling' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the backend domain plus several concrete areas ('API design, database optimization, server-side best practices for Node.js, Express, and Next.js API routes'), but these are topic nouns rather than concrete verbs/actions, so coverage is not comprehensive.	3 / 5
Completeness	Has a clear 'what' (backend architecture patterns and best practices) but no explicit 'Use when...' trigger clause, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural keywords users would say ('API design', 'database optimization', 'Node.js', 'Express', 'Next.js API routes') with good coverage; a few natural synonyms or phrasings are missing but it is above the midpoint.	4 / 5
Distinctiveness Conflict Risk	Scoped to specific frameworks (Node.js, Express, Next.js API routes), making it mostly distinct from generic backend skills with only minor overlap risk.	4 / 5
	Total	14 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (601 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/skills/backend-patterns/SKILL.md
Commit: d8409a4

Reviewed: 1 day 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.