backend-patterns

后端架构模式、API设计、数据库优化以及针对Node.js、Express和Next.js API路由的服务器端最佳实践。

Install with Tessl CLI

npx tessl i github:affaan-m/everything-claude-code --skill backend-patterns

What are skills?

Overall
score

61%

Review — 49%

Does it follow best practices?

If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:

npx tessl skill review --optimize ./path/to/skill

Learn more

Validation — 10 / 11 Passed

Validation for skill structure

SKILL.md

Review

Evals

Discovery

33%

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 clear technical domain and specific technologies but lacks concrete action verbs and explicit trigger guidance. It reads more like a topic list than an actionable skill description, and the absence of a 'Use when...' clause significantly limits Claude's ability to know when to select this skill over others.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'backend code', 'API endpoint', 'server-side', 'database query', 'Express route', or 'Next.js API'.

Replace abstract terms like 'best practices' with concrete actions such as 'design RESTful endpoints', 'optimize database queries', 'implement middleware', or 'structure API routes'.

Include common user phrases and variations like 'REST API', 'server code', 'backend logic', 'database performance', '.js server files' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (backend architecture, API design, database optimization) and mentions specific technologies (Node.js, Express, Next.js API routes), but actions are described at a high level ('best practices') rather than listing concrete specific actions like 'design RESTful endpoints' or 'implement connection pooling'.	2 / 3
Completeness	Describes what the skill covers (backend patterns, API design, database optimization, server-side best practices) but completely lacks any 'Use when...' clause or explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant technology keywords (Node.js, Express, Next.js) that users might mention, but lacks common variations and natural phrases users would say like 'backend', 'server code', 'REST API', 'database queries', or 'API endpoints'.	2 / 3
Distinctiveness Conflict Risk	The combination of backend + specific frameworks (Node.js, Express, Next.js) provides some distinctiveness, but 'API design' and 'database optimization' are broad enough to potentially overlap with other database or API-focused skills.	2 / 3
	Total	7 / 12 Passed

Implementation

65%

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

This is a solid reference document with high-quality, executable TypeScript examples covering essential backend patterns. The main weaknesses are its length (could benefit from splitting into focused sub-documents) and lack of guidance on pattern selection and composition. The code quality is excellent but the document tries to cover too much ground in a single file.

Suggestions

Split into focused sub-documents (e.g., CACHING.md, AUTH.md, ERROR-HANDLING.md) with SKILL.md as a concise overview pointing to each

Add a decision guide or flowchart for when to use each pattern (e.g., 'Use repository pattern when: ...')

Remove basic patterns Claude knows well (simple rate limiter, basic job queue) or move to an 'examples' reference file

Add validation checkpoints for implementing these patterns (e.g., 'After adding caching: verify cache invalidation works by...')

Dimension	Reasoning	Score
Conciseness	The skill is comprehensive but includes some patterns Claude already knows well (basic repository pattern, simple rate limiting). Some sections like the job queue could be trimmed, and the explanatory comments are occasionally redundant.	2 / 3
Actionability	Excellent executable TypeScript code throughout with complete, copy-paste ready examples. Each pattern includes full implementation details with proper typing, error handling, and usage examples.	3 / 3
Workflow Clarity	Individual patterns are clear, but there's no guidance on when to use which pattern, how patterns compose together, or validation steps when implementing these in a real project. Missing feedback loops for database migrations or deployment.	2 / 3
Progressive Disclosure	Content is well-organized with clear section headers, but it's a monolithic 400+ line file. Advanced topics like Redis caching, job queues, and RBAC could be split into separate reference files with the main skill providing an overview.	2 / 3
	Total	9 / 12 Passed

Validation

91%

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

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.