backend-patterns

Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.

Quality

76%

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

A thorough, code-rich backend patterns reference with strong actionability but no progressive disclosure: everything lives in one long SKILL.md with placeholder stubs and some redundant examples. Splitting sections into reference files and tightening stubs would raise the score.

Suggestions

Move each major pattern category (API design, database, caching, auth/rate-limiting, background jobs, logging) into separate reference files and link to them from a concise SKILL.md overview.

Replace placeholder comments ('// Other methods...', '// Vector search implementation', '// Job execution logic') with either complete implementations or explicit 'see X' pointers.

Add validation/verification checkpoints for the destructive or batch-oriented patterns (e.g., transactions, queue processing) to introduce explicit feedback loops.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code-first content with little concept explanation, but contains placeholder stubs ('// Other methods...', '// Vector search implementation', '// Job execution logic') and some redundancy between the Redis Caching Layer and Cache-Aside examples.	4 / 5
Actionability	Provides concrete, mostly executable TypeScript examples across all pattern categories, with minor gaps where implementation bodies are left as placeholder comments.	4 / 5
Workflow Clarity	Organized as a pattern catalog rather than a sequenced workflow, with no explicit validation checkpoints or feedback loops; the 'When to Activate' list gives triggers but not a procedural sequence.	3 / 5
Progressive Disclosure	Well-sectioned structure, but ~590 lines of inlined pattern content (API design, database, caching, auth, rate limiting, jobs, logging) that would be better split into separate reference files, and no external references are signaled.	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, third-person description that clearly states capabilities and an explicit 'Use when' trigger scoped to specific frameworks. Minor gains possible from more granular action verbs and a few more synonyms.

Dimension	Reasoning	Score
Specificity	Names several concrete capability areas ('API design, database optimization, and server-side best practices') tied to specific frameworks, though these are domains rather than granular actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Backend architecture patterns, API design, database optimization...') and when ('Use when building or reviewing Node.js, Express, or Next.js API routes and their data access').	5 / 5
Trigger Term Quality	Includes natural terms users say ('building or reviewing Node.js, Express, or Next.js API routes', 'data access') with framework names, but misses a few common synonyms or file/extension variants.	4 / 5
Distinctiveness Conflict Risk	Carves a clear backend niche scoped to Node.js/Express/Next.js API routes and data access, with distinct triggers and minimal overlap with unrelated skills.	5 / 5
	Total	18 / 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
skill_md_line_count	SKILL.md is long (598 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: affaan-m/ECC
Path: .agents/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.