senior-backend
This skill should be used when the user asks to "design REST APIs", "optimize database queries", "implement authentication", "build microservices", "review backend code", "set up GraphQL", "handle database migrations", or "load test APIs". Use for Node.js/Express/Fastify development, PostgreSQL optimization, API security, and backend architecture patterns.
Install with Tessl CLI
npx tessl i github:alirezarezvani/claude-skills --skill senior-backendOverall
score
76%
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
72%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 excels at trigger term coverage and distinctiveness, providing numerous natural phrases users would say and a clear backend development niche. However, it inverts the typical structure by leading with triggers rather than capabilities, leaving the 'what does this do' portion underdeveloped. The skill would benefit from explicit capability statements before the trigger guidance.
Suggestions
Add explicit capability statements at the beginning describing what the skill does (e.g., 'Designs and implements backend services, optimizes database performance, and secures API endpoints').
Restructure to follow the pattern: capabilities first, then 'Use when...' clause with the existing trigger terms.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (backend development) and lists technologies (Node.js/Express/Fastify, PostgreSQL, GraphQL), but the actions are mostly quoted user phrases rather than concrete capability descriptions. Missing explicit statements of what the skill actually does. | 2 / 3 |
Completeness | Has a 'Use when' clause with trigger phrases, but the 'what does this do' portion is weak - it lists technologies and domains but doesn't clearly describe the skill's capabilities or actions. The description focuses heavily on triggers without explaining what the skill actually accomplishes. | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'design REST APIs', 'optimize database queries', 'implement authentication', 'build microservices', 'review backend code', 'set up GraphQL', 'handle database migrations', 'load test APIs'. These are realistic user requests. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche in backend development with specific technology stack (Node.js/Express/Fastify, PostgreSQL) and distinct triggers. The combination of REST APIs, microservices, database optimization, and authentication creates a well-defined scope unlikely to conflict with frontend or other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
73%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive backend engineering skill with excellent actionability - nearly every section provides executable code. The progressive disclosure is well-handled with clear navigation and external references. However, the content could be more concise by trimming verbose output examples, and workflows would benefit from explicit validation checkpoints and error recovery patterns, especially for database migrations.
Suggestions
Add explicit validation checkpoints to workflows, e.g., 'VERIFY: Check migration output shows 0 errors before proceeding to Step 5'
Trim verbose tool output examples - showing 2-3 key lines instead of full output blocks would save tokens while preserving clarity
Add rollback/recovery steps to the Security Hardening and API Design workflows for when validation fails
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally efficient but includes some unnecessary verbosity, such as detailed output examples for every tool command and explanations that could be trimmed. The table of contents and some structural elements add overhead without proportional value. | 2 / 3 |
Actionability | Provides fully executable code examples throughout - bash commands, TypeScript snippets, SQL queries, and YAML configurations are all copy-paste ready with realistic examples and expected outputs. | 3 / 3 |
Workflow Clarity | Workflows have clear numbered steps but lack explicit validation checkpoints and error recovery loops. The Database Optimization Workflow includes a dry-run step, but other workflows don't have clear 'verify before proceeding' gates or rollback guidance. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, a table of contents, and appropriate references to external documentation files. The reference table clearly signals where to find detailed information without nesting multiple levels deep. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 13 / 16 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.