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

79%

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 ./skills/backend-patterns/SKILL.md

Quality

Content

71%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 content is highly actionable with executable, copy-paste-ready patterns and clear section organization. Its weaknesses are token efficiency (some redundant boilerplate and obvious comments) and progressive disclosure (everything is inlined in one long file with no external references).

Suggestions

Trim obvious restating comments (e.g. '// Business logic separated from data access', '// Abstract data access logic') and consolidate repeated boilerplate to improve token efficiency.

Split large independent subtopics such as Authentication & Authorization, Caching Strategies, and Background Jobs into one-level-deep reference files (e.g. references/auth.md) linked from the overview, to improve progressive disclosure.

Add explicit validate/verify checkpoints or feedback loops for the transaction and queue patterns (e.g. confirm cache invalidation after writes) to strengthen workflow clarity for risky operations.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient TypeScript with brief comments, but includes redundant explanatory lines Claude already knows (e.g. '// Business logic separated from data access', '// Abstract data access logic') and repeats boilerplate across the ~562-line file, so it could be tightened.	3 / 5
Actionability	Provides concrete, copy-paste-ready executable TypeScript across all major patterns (repository, service, caching, auth, retry, logging) with realistic Supabase/Next.js examples covering common cases.	5 / 5
Workflow Clarity	A 'When to Activate' list sequences activation cues and sections are logically ordered; because this is a pattern reference rather than a destructive/batch workflow, the validation-cap does not apply, though it lacks explicit validate-then-retry feedback loops.	4 / 5
Progressive Disclosure	Content is well-sectioned with clear headers, but it is a monolithic ~562-line single file with no bundle files (references/scripts/assets absent) and large subtopics (auth, caching, jobs) inlined that could be split into one-level-deep reference files.	3 / 5
	Total	15 / 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.

The description is strong: it states concrete capabilities and provides an explicit 'Use when' trigger scoped to a distinct backend niche. It is comprehensive on completeness and distinctiveness, with only minor gaps in specificity and trigger-term synonym coverage.

Dimension	Reasoning	Score
Specificity	Lists several specific capability areas ('API design, database optimization, ... caching ... background jobs') rather than vague language, though it names domains/patterns more than discrete user-facing actions, leaving minor gaps in coverage.	4 / 5
Completeness	Explicitly answers both 'what' (backend patterns, API design, database optimization) and 'when' with a concrete 'Use when building or reviewing Node.js, Express, or Next.js API routes and their data access' trigger phrase.	5 / 5
Trigger Term Quality	Includes natural trigger terms users say ('Node.js', 'Express', 'Next.js API routes', 'API routes', 'data access') with good coverage; a few common synonyms or variants are missing, so it does not reach comprehensive level 5.	4 / 5
Distinctiveness Conflict Risk	A clear niche scoped to server-side patterns for Node.js/Express/Next.js API routes with distinct triggers, minimizing overlap risk with unrelated skills.	5 / 5
	Total	18 / 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 (563 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: skills/backend-patterns/SKILL.md
Commit: 5eddf1a

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.