backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
38
23%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./docs/zh-TW/skills/backend-patterns/SKILL.mdQuality
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 (Node.js, Express, Next.js), which helps with selection. However, it reads more like a topic list than an actionable skill description—it lacks concrete verbs describing what the skill does and entirely omits a 'Use when...' clause, making it difficult for Claude to know when to select it over other backend-related skills.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about building APIs, optimizing database queries, structuring Express middleware, or designing Next.js API routes.'
Replace abstract category nouns with concrete action phrases, e.g., 'Designs RESTful and GraphQL APIs, optimizes database queries, structures Express middleware pipelines, and implements authentication flows.'
Include additional natural trigger terms users might say, such as 'REST', 'GraphQL', 'middleware', 'SQL optimization', 'server performance', or 'backend error handling'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (backend development) and some areas (API design, database optimization, architecture patterns), but these are still fairly broad categories rather than concrete actions like 'design RESTful endpoints' or 'optimize SQL queries'. No specific verbs describing what the skill does. | 2 / 3 |
Completeness | Describes 'what' at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also only loosely defined, warranting a score of 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', 'routing', 'MongoDB', 'PostgreSQL', 'server performance', or 'backend bugs'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of specific technologies (Node.js, Express, Next.js API routes) helps narrow the scope, but 'backend architecture patterns' and 'server-side best practices' are broad enough to overlap with general coding skills, DevOps skills, or database-specific 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 reads as an exhaustive backend patterns reference/cookbook rather than a focused, actionable skill. It is far too verbose, covering many well-known patterns with full implementations that Claude already knows, and lacks any workflow structure, decision guidance, or progressive disclosure. The content would benefit enormously from being condensed to a brief overview with references to separate pattern files.
Suggestions
Drastically reduce the main file to a concise overview (under 50 lines) listing available patterns with one-line descriptions, and move detailed implementations to separate referenced files (e.g., CACHING.md, AUTH.md, ERROR-HANDLING.md).
Remove implementations of well-known patterns Claude already knows (JWT verification, exponential backoff, N+1 prevention, RBAC) and instead focus on project-specific conventions, preferred libraries, and non-obvious decisions.
Add a workflow or decision framework — e.g., 'When building a new API endpoint, follow these steps: 1. Define route... 2. Add validation... 3. Implement service layer... 4. Add error handling... 5. Test endpoint' with validation checkpoints.
Add project-specific context: which ORM/database client to use, naming conventions, file structure expectations, and any non-standard patterns unique to this codebase.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This is extremely verbose at ~400+ lines, covering many patterns (repository, service layer, middleware, caching, auth, rate limiting, queues, logging) with full implementations. Much of this is standard knowledge Claude already possesses — repository pattern, JWT verification, exponential backoff, N+1 prevention, RBAC, etc. are well-known patterns that don't need full code examples in a skill file. | 1 / 3 |
Actionability | The code examples are mostly concrete and executable TypeScript, which is good. However, they are more like reference/cookbook patterns than actionable instructions — there's no guidance on when to apply which pattern, no decision framework, and some examples are incomplete (e.g., 'other methods...' comments, missing imports). It reads as a pattern catalog rather than executable guidance for a specific task. | 2 / 3 |
Workflow Clarity | There is no workflow or sequencing at all. The skill presents isolated patterns without any process for how to architect a backend, no validation checkpoints, no decision tree for choosing patterns, and no step-by-step guidance. For database operations and destructive changes shown (DELETE endpoints, transactions), there are no validation or verification steps. | 1 / 3 |
Progressive Disclosure | This is a monolithic wall of code examples with no references to external files and no layered structure. All patterns are inlined at full detail. Content covering 10+ distinct topics (API design, repository pattern, service layer, middleware, query optimization, transactions, caching, error handling, auth, RBAC, rate limiting, queues, logging) should be split across multiple files with a concise overview in the main skill. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%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
- ysyecust/everything-claude-code
- Commit
79cc4e3
- Reviewed
Table of Contents
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.