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
—
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, which helps with targeting. However, it lacks concrete actions (verbs describing what the skill does), has no 'Use when...' clause to guide skill selection, and uses category-level terms rather than specific capabilities. The description reads more like a topic list than an actionable skill selector.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios, e.g., 'Use when the user asks about building REST APIs, optimizing database queries, structuring Express middleware, or setting up Next.js API routes.'
Replace abstract category names with concrete actions, e.g., 'Designs RESTful and GraphQL APIs, optimizes database queries and indexing, structures Express middleware pipelines, and implements authentication flows.'
Include additional natural trigger terms users might say, such as 'REST', 'GraphQL', 'middleware', 'SQL queries', 'MongoDB', '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 reads as a lengthy reference catalog of common backend patterns (repository, service layer, caching, auth, rate limiting, etc.) that Claude already understands well. It lacks workflow sequencing, validation steps, decision guidance, and progressive disclosure — it's essentially a monolithic dump of illustrative code snippets without actionable instructions on when or how to apply them in context.
Suggestions
Drastically reduce content to only project-specific conventions or non-obvious patterns that Claude wouldn't already know — remove standard patterns like repository, middleware, JWT auth, and rate limiting.
Add a clear workflow section that sequences when to apply which pattern (e.g., 'When adding a new API endpoint: 1. Define route → 2. Add validation → 3. Implement service → 4. Test with curl command → 5. Verify error handling').
Split detailed pattern references into separate files (e.g., AUTH.md, CACHING.md) and keep SKILL.md as a concise overview with links.
Add explicit validation/verification steps, especially for database operations and destructive endpoints (e.g., 'After adding a transaction, verify rollback behavior by...').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This is extremely verbose at ~400+ lines, covering many patterns (repository, service layer, middleware, caching, auth, rate limiting, queues, logging) that Claude already knows well. Most of these are standard software engineering patterns that don't need to be taught to Claude. The Chinese comments add minimal value over what the code already communicates. | 1 / 3 |
Actionability | The code examples are mostly concrete and executable TypeScript, which is good. However, they are more illustrative/reference patterns than actionable instructions — there's no clear guidance on *when* to apply which pattern, no decision framework, and the examples are somewhat generic (e.g., placeholder 'markets' domain) rather than copy-paste ready for a specific task. | 2 / 3 |
Workflow Clarity | There is no workflow or sequencing at all — it's a catalog of isolated patterns with no guidance on how they compose, what order to implement them, or validation/verification steps. For patterns involving database transactions and destructive operations (DELETE endpoints), there are no validation checkpoints or error recovery workflows. | 1 / 3 |
Progressive Disclosure | The entire content is a monolithic wall of code examples with no references to external files, no layered organization, and no separation of overview from detail. All patterns are dumped inline at the same level of detail, making it hard to navigate or discover specific sections. | 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
- affaan-m/everything-claude-code
- Commit
841beea
- 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.