backend-patterns

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

Quality

59%

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

57%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 a well-organized, actionable catalog of backend patterns with concrete TypeScript examples, but it spends tokens re-teaching well-known patterns, lacks sequenced workflows with validation checkpoints, and keeps everything monolithically inline.

Suggestions

Trim explanations of concepts Claude already knows (e.g., 'Abstract data access logic', 'Business logic separated from data access') and drop redundant PASS/GOOD vs FAIL/BAD labels in favor of concise comments.

Move detailed implementations of individual patterns into separate reference files (e.g., references/api-design.md, references/caching.md, references/auth.md) and keep SKILL.md as a concise overview with one-level-deep links.

For destructive or batch operations (transactions, N+1 fixes, cache invalidation), add explicit validation/verification checkpoints and feedback loops (validate -> fix -> retry).

Dimension	Reasoning	Score
Conciseness	The body is code-focused and organized, but it restates many patterns Claude already knows (repository, service layer, middleware, JWT, RBAC, rate limiting, structured logging) and includes redundant labels like 'PASS: GOOD'/'FAIL: BAD', so it could be tightened.	3 / 5
Actionability	Provides concrete, mostly copy-paste-ready TypeScript across many patterns with specific examples; only minor placeholders (vectorSearch, job execute) keep it from a 5.	4 / 5
Workflow Clarity	This is a pattern catalog rather than a sequenced workflow, and operations involving batch/destructive changes (transactions, N+1 batch fetch) lack explicit validation checkpoints, capping workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist and all content is inlined in a single ~600-line file; section headers give structure, but full implementations of standard patterns that could live in separate reference files are inlined with no references signaled.	3 / 5
	Total	13 / 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 a backend/server-side niche with natural trigger terms and a clear 'what', but it lacks any 'when to use' guidance and relies on abstract topic labels rather than concrete actions.

Suggestions

Add an explicit 'Use when...' clause with concrete trigger phrases (e.g., 'Use when designing REST/GraphQL endpoints, optimizing database queries, or adding caching/middleware to Node.js, Express, or Next.js API routes').

Replace abstract noun phrases ('patterns', 'design', 'optimization') with concrete verbs where possible (e.g., 'Design APIs, optimize database queries, add caching layers, structure error handling').

Include common synonyms or file/concept extensions users say (e.g., 'REST', 'GraphQL', 'N+1 queries', 'Redis caching') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the backend domain plus several topic areas ('API design', 'database optimization', 'server-side best practices'), but these are abstract noun phrases rather than concrete actions like 'Extract' or 'Fill', matching the anchor for listing a domain with limited concrete actions.	3 / 5
Completeness	The 'what' is clearly stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural terms users would say ('API design', 'database optimization', 'Node.js', 'Express', 'Next.js API routes') with good stack-specific coverage, missing only a few common variations.	4 / 5
Distinctiveness Conflict Risk	Clearly scoped to server-side backend work for Node.js/Express/Next.js, a distinct niche with only minor overlap risk against general full-stack or frontend skills.	4 / 5
	Total	14 / 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: ysyecust/everything-claude-code
Path: .agents/skills/backend-patterns/SKILL.md
Commit: a9cbecb

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