backend-patterns

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-organized patterns catalog that loses points for being a monolithic ~600-line file with some redundancy and no validation checkpoints on its destructive/batch operations.

Suggestions

Split large sections (caching, auth, rate limiting) into separate reference files linked one level deep from SKILL.md to improve progressive disclosure.

Add explicit validation/verification checkpoints (e.g. verify token before destructive actions, confirm job completion) for batch and destructive operations.

Collapse the duplicate cache-aside examples (CachedMarketRepository vs getMarketWithCache) into a single canonical pattern to tighten token use.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code catalog with little concept re-teaching, but ~600 lines include redundant coverage (e.g. CachedMarketRepository followed by a near-duplicate getMarketWithCache) that could be tightened.	2 / 3
Actionability	Abundant concrete, copy-paste-ready TypeScript examples with explicit PASS/FAIL annotations across API design, caching, auth, rate limiting, and logging, fully matching the executable-code anchor.	3 / 3
Workflow Clarity	This is a pattern catalog rather than a sequenced workflow, and destructive/batch operations (DELETE handler, background jobs, N+1 batch fetch) lack explicit validation checkpoints, capping clarity at 2.	2 / 3
Progressive Disclosure	Well-organized into labeled sections but monolithic — all ~600 lines are inline with no bundle files or one-level-deep references to split out sub-topics like caching or auth.	2 / 3
	Total	9 / 12 Passed

Description

82%

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 specific, well-scoped backend description with strong natural trigger terms, weakened only by the absence of an explicit 'Use when...' trigger clause which caps completeness at 2.

Suggestions

Append an explicit trigger clause such as 'Use when designing or optimizing Node.js/Express/Next.js APIs, repositories, caching, or auth middleware.'

Replace the vague 'server-side best practices' phrasing with one or two concrete capabilities to avoid mild fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capability areas — 'Backend architecture patterns, API design, database optimization, and server-side best practices' — tied to a specific stack ('Node.js, Express, and Next.js API routes'), matching the anchor for multiple specific concrete areas.	3 / 3
Completeness	Clearly states what the skill covers but lacks any explicit 'Use when...' or equivalent trigger clause, so per the judging guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Uses natural developer terms a user would actually say — 'API design', 'database optimization', 'Node.js', 'Express', 'Next.js API routes', 'server-side best practices' — giving good coverage of likely trigger phrasing.	3 / 3
Distinctiveness Conflict Risk	Scoped to backend/server-side work for a named Node/Express/Next.js stack, a clear niche unlikely to conflict with frontend or other-domain skills.	3 / 3
	Total	11 / 12 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
Commit: 4130457

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.