backend-patterns

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

Quality

23%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./docs/zh-TW/skills/backend-patterns/SKILL.md

Quality

Discovery

32%

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 identifies a reasonable domain and names specific technologies, which helps with targeting. However, it lacks concrete actions (uses category labels instead of verbs), has no 'Use when...' clause to guide skill selection, and some terms are broad enough to risk overlap with other skills.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about building APIs, optimizing database queries, structuring Express middleware, or setting up Next.js API routes.'

Replace abstract category labels with concrete actions, e.g., 'Designs RESTful and GraphQL APIs, optimizes database queries and indexing, structures Express middleware pipelines, and implements authentication patterns.'

Include additional natural trigger terms users might say, such as 'REST', 'GraphQL', 'middleware', 'SQL optimization', 'server performance', or 'endpoint design'.

Dimension	Reasoning	Score
Specificity	Names the domain (backend development) and lists several areas like 'API design', 'database optimization', and 'server-side best practices', but these are still fairly high-level categories rather than concrete actions. It doesn't specify what actions are performed (e.g., 'designs RESTful endpoints', 'optimizes SQL queries').	2 / 3
Completeness	Describes 'what' at a high level but completely lacks any 'when' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also somewhat vague, this scores a 1.	1 / 3
Trigger Term Quality	Includes some relevant keywords users might say like 'API design', 'Node.js', 'Express', 'Next.js API routes', and 'database optimization'. However, it misses common variations like 'REST', 'GraphQL', 'middleware', 'SQL', 'MongoDB', 'backend performance', or 'server setup'.	2 / 3
Distinctiveness Conflict Risk	The mention of specific technologies (Node.js, Express, Next.js API routes) helps narrow the scope, but terms like 'backend architecture patterns' and 'best practices' are broad enough to overlap with general coding, architecture, or full-stack skills.	2 / 3
	Total	7 / 12 Passed

Implementation

14%

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

This skill is an extensive catalog of backend patterns presented as a monolithic document with no workflow guidance, no progressive disclosure, and significant verbosity. While the code examples are mostly concrete TypeScript, the skill explains many patterns Claude already knows well and fails to provide actionable sequencing or validation steps. It would benefit greatly from being restructured into a concise overview with references to detailed pattern files.

Suggestions

Drastically reduce the main SKILL.md to a concise overview (under 80 lines) listing each pattern with a one-liner description and a reference link to a dedicated file (e.g., 'See [CACHING.md](CACHING.md) for Redis cache-aside pattern').

Add a workflow section that sequences when and how to apply these patterns (e.g., 'Start with repository pattern → add service layer → add caching → add error handling') with validation checkpoints.

Remove explanations of patterns Claude already knows (repository, middleware, RBAC, retry with exponential backoff) and focus only on project-specific conventions, configurations, or non-obvious implementation details.

For database operations and transactions, add explicit validation steps (e.g., 'Verify transaction success before proceeding', 'Test rollback behavior') to improve workflow safety.

Dimension	Reasoning	Score
Conciseness	This is extremely verbose at ~400+ lines, covering 10+ distinct backend patterns (API design, repository, service layer, middleware, caching, error handling, auth, RBAC, rate limiting, job queues, logging). Most of these are well-known patterns that Claude already understands. The Chinese comments add minimal value over what the code itself communicates. This reads like a textbook chapter, not a targeted skill.	1 / 3
Actionability	The code examples are mostly concrete and executable TypeScript, which is good. However, many are incomplete (e.g., 'other methods...' comments, missing imports, vectorSearch left unimplemented), and the skill lacks specific guidance on when to apply which pattern or how to compose them. It's more of a reference catalog than actionable instructions.	2 / 3
Workflow Clarity	There is no sequenced workflow or multi-step process described. The skill presents isolated patterns without explaining how to combine them, in what order to implement them, or any validation/verification steps. For database operations and destructive changes (DELETE endpoints, transactions), there are no validation checkpoints.	1 / 3
Progressive Disclosure	This is a monolithic wall of code examples with no references to external files and no layered organization. All 10+ patterns are dumped inline at the same level of detail. Content like the SQL function, Redis caching, job queues, and logging could easily be split into separate reference files with a concise overview in the main skill.	1 / 3
	Total	5 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (588 lines); consider splitting into references/ and linking	Warning

	Total	10 / 11 Passed

Repository: affaan-m/everything-claude-code
Commit: 928076c

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.