backend-engineer
Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases (PostgreSQL, MongoDB, Redis), APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), testing strategies, security best practices (OWASP Top 10), performance optimization, scalability patterns (microservices, caching, sharding), DevOps practices (Docker, Kubernetes, CI/CD), and monitoring. Use when designing APIs, implementing authentication, optimizing database queries, setting up CI/CD pipelines, handling security vulnerabilities, building microservices, or developing production-ready backend systems.
85
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
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, comprehensive description that clearly articulates backend development capabilities with specific technologies and explicit trigger conditions. The main weakness is its breadth—covering everything from databases to DevOps to security—which could cause conflicts with more specialized skills in a large skill library. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and technologies: 'designing APIs, implementing authentication, optimizing database queries, setting up CI/CD pipelines, handling security vulnerabilities, building microservices.' Also enumerates specific frameworks, databases, and patterns. | 3 / 3 |
Completeness | Clearly answers both what (build robust backend systems with listed technologies and patterns) AND when (explicit 'Use when...' clause with seven specific trigger scenarios like 'designing APIs', 'implementing authentication', 'building microservices'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'APIs', 'authentication', 'database queries', 'CI/CD pipelines', 'security vulnerabilities', 'microservices', 'backend systems', plus specific technology names like 'Node.js', 'Python', 'PostgreSQL', 'Docker', 'Kubernetes'. | 3 / 3 |
Distinctiveness Conflict Risk | While comprehensive for backend development, the broad scope could overlap with more specialized skills for databases, DevOps/Kubernetes, security, or API design. Terms like 'Docker', 'Kubernetes', 'CI/CD' might conflict with dedicated DevOps skills. | 2 / 3 |
Total | 11 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured index/overview skill that excels at organization and conciseness. It effectively serves as a navigation hub to detailed reference materials. However, it lacks concrete executable examples and explicit validation steps in workflows, which limits its immediate actionability for implementation tasks.
Suggestions
Add at least one concrete, executable code example per major section (e.g., a FastAPI endpoint with authentication, a PostgreSQL query with proper parameterization)
Enhance implementation checklists with explicit validation checkpoints, especially for security-critical steps (e.g., 'Validate JWT configuration with test tokens before deploying')
Include a minimal 'Quick Start' code snippet that demonstrates a complete, working endpoint with auth and input validation
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables, bullet points, and brief phrases. No unnecessary explanations of concepts Claude already knows. Every section earns its place. | 3 / 3 |
Actionability | Provides good decision matrices and checklists, but lacks executable code examples. The checklists are actionable but abstract (e.g., 'Choose style → Design schema') rather than copy-paste ready commands or code snippets. | 2 / 3 |
Workflow Clarity | Implementation checklists provide clear sequences, but lack explicit validation checkpoints and feedback loops. For security-critical operations like authentication setup, there's no 'validate then proceed' pattern shown. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear overview and well-organized one-level-deep references to specific topic files. Navigation is intuitive with categorized reference sections (Core Technologies, Security, Performance, Quality). | 3 / 3 |
Total | 10 / 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 |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- siviter-xyz/dot-agent
- Commit
3376255
- 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.