senior-backend
Comprehensive backend development skill for building scalable backend systems using NodeJS, Express, Go, Python, Postgres, GraphQL, REST APIs. Includes API scaffolding, database optimization, security implementation, and performance tuning. Use when designing APIs, optimizing database queries, implementing business logic, handling authentication/authorization, or reviewing backend code.
Install with Tessl CLI
npx tessl i github:sc30gsw/claude-code-customes --skill senior-backend53
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
92%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly articulates capabilities with specific technologies and actions, includes natural trigger terms developers would use, and provides explicit 'Use when' guidance. The main weakness is its broad scope covering multiple languages and domains, which could create conflicts with more specialized skills in a large skill library.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'API scaffolding, database optimization, security implementation, and performance tuning' along with specific technologies (NodeJS, Express, Go, Python, Postgres, GraphQL, REST APIs). | 3 / 3 |
Completeness | Clearly answers both what (building scalable backend systems with specific technologies and capabilities) AND when (explicit 'Use when...' clause covering designing APIs, optimizing queries, implementing business logic, handling auth, reviewing code). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'APIs', 'database queries', 'authentication', 'authorization', 'backend code', 'NodeJS', 'Express', 'Go', 'Python', 'Postgres', 'GraphQL', 'REST' - these are all terms developers naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | While it specifies backend development, the broad scope (multiple languages, databases, APIs) could overlap with language-specific skills or database-specific skills. Terms like 'reviewing backend code' could conflict with general code review skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
7%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is a template shell with no substantive content. It lists tools and references without providing any actual backend development guidance, executable code, or specific patterns. The content consists almost entirely of generic placeholders and best practices Claude already knows, making it essentially useless for its stated purpose of building scalable backend systems.
Suggestions
Replace placeholder script descriptions with actual usage examples showing real arguments and expected outputs (e.g., 'python scripts/api_scaffolder.py ./myapp --framework express --db postgres' with sample generated output)
Add concrete, executable code examples for core tasks: a REST endpoint, a GraphQL resolver, a database query with Prisma, an authentication middleware implementation
Remove generic best practices sections (Code Quality, Performance, Security, Maintainability) that explain concepts Claude already knows
Add validation workflows for database migrations showing rollback procedures and verification steps
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with generic placeholder content that adds no value. Descriptions like 'Automated tool for api scaffolder tasks' and 'Comprehensive analysis and optimization tool' are meaningless filler. Lists generic best practices Claude already knows (validate inputs, write tests, keep it simple). | 1 / 3 |
Actionability | No concrete, executable guidance. Script commands use vague placeholders like '[options]' and '[arguments]' without explaining what they do. No actual code examples showing API design, database queries, or security implementation despite claiming to cover these topics. | 1 / 3 |
Workflow Clarity | Workflows are superficial with no real sequencing or validation. 'Run Quality Checks' section just says 'Review recommendations, Apply fixes' with no specifics. No validation checkpoints for database migrations or API changes, which are risky operations. | 1 / 3 |
Progressive Disclosure | Structure exists with clear references to external files (references/*.md, scripts/), but the main content is bloated with generic information that should either be removed or moved to reference files. The overview itself contains too much filler content. | 2 / 3 |
Total | 5 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.