backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
Install with Tessl CLI
npx tessl i github:haniakrim21/everything-claude-code --skill backend-patternsOverall
score
61%
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/skillValidation for skill structure
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 relies heavily on abstract concepts ('patterns', 'best practices') rather than concrete actions. The complete absence of a 'Use when...' clause significantly weakens its utility for skill selection, and the trigger terms could be expanded to capture more natural user language.
Suggestions
Add an explicit 'Use when...' clause with trigger scenarios like 'Use when building REST APIs, designing backend services, optimizing database queries, or working with Express/Next.js server code'
Replace abstract terms with concrete actions: instead of 'backend architecture patterns', specify 'design REST endpoints, structure Express middleware, configure API routes'
Expand trigger terms to include common variations: 'REST', 'endpoints', 'server-side', 'middleware', 'SQL queries', 'MongoDB', 'authentication'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (backend/API/database) and mentions specific technologies (Node.js, Express, Next.js), but uses abstract terms like 'patterns', 'best practices', and 'optimization' rather than concrete actions like 'design REST endpoints' or 'write database queries'. | 2 / 3 |
Completeness | Describes what the skill covers (backend patterns, API design, etc.) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes some relevant keywords users might say ('API design', 'Node.js', 'Express', 'Next.js', 'database'), but missing common variations like 'REST', 'endpoints', 'server', 'backend code', 'SQL', 'MongoDB', or 'routes'. | 2 / 3 |
Distinctiveness Conflict Risk | The technology stack (Node.js, Express, Next.js API routes) provides some distinction, but 'backend architecture' and 'database optimization' are broad enough to potentially overlap with general coding skills or database-specific 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 excellent, executable code examples covering a wide range of backend patterns. However, it reads more like a comprehensive cookbook than a focused skill guide - it could be more concise by removing patterns Claude already knows and would benefit from clearer guidance on when to apply each pattern and how they work together in a real application.
Suggestions
Split into multiple focused files (e.g., DATABASE.md, AUTH.md, CACHING.md) and make this file a concise overview with links to detailed implementations
Add a decision tree or guidance section at the top explaining when to use each pattern (e.g., 'Use Repository pattern when: you need to swap data sources or test with mocks')
Remove or significantly trim basic patterns like simple middleware and repository that Claude already understands well - focus on project-specific conventions instead
Add validation checkpoints for database operations, especially for the transaction pattern (e.g., 'Verify transaction succeeded before proceeding')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some patterns Claude already knows well (basic repository pattern, middleware pattern). Some sections like the simple queue pattern and rate limiter could be trimmed as these are standard implementations. | 2 / 3 |
Actionability | Excellent executable TypeScript code throughout with complete, copy-paste ready examples. Each pattern includes full implementation with proper typing, error handling, and usage examples. | 3 / 3 |
Workflow Clarity | Patterns are presented as isolated examples without clear guidance on when to use which pattern or how they connect. Missing validation checkpoints for database operations and no explicit workflow for implementing these patterns in a new project. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers, but the file is quite long (~400 lines) and could benefit from splitting into separate files (e.g., CACHING.md, AUTH.md, DATABASE.md) with this file serving as an overview with links. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
91%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
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.