backend-api
Skill do Backend Developer para definição de APIs, banco de dados, e lógica de servidor. Use quando precisar definir schemas de banco, endpoints REST/GraphQL, validação server-side, autenticação, migrations, ou qualquer lógica de backend. Trigger em: "API", "endpoint", "banco de dados", "schema", "migration", "backend", "servidor", "autenticação", "JWT", "middleware", "ORM", "Prisma", "PostgreSQL", "Node.js", "Express", "NestJS", "validação server-side".
86
Quality
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%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 well-crafted skill description that excels across all dimensions. It provides specific capabilities, comprehensive trigger terms covering both concepts and technologies, explicit 'Use when' and 'Trigger em' clauses, and clear backend-specific terminology that distinguishes it from other development skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'definição de APIs, banco de dados, e lógica de servidor', 'definir schemas de banco, endpoints REST/GraphQL, validação server-side, autenticação, migrations'. These are concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('definição de APIs, banco de dados, e lógica de servidor') AND when ('Use quando precisar definir schemas de banco, endpoints REST/GraphQL...') with explicit 'Trigger em:' clause listing specific keywords. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'API', 'endpoint', 'banco de dados', 'schema', 'migration', 'backend', 'JWT', 'middleware', 'ORM', 'Prisma', 'PostgreSQL', 'Node.js', 'Express', 'NestJS'. Includes both generic and technology-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on backend development with distinct triggers like 'backend', 'servidor', 'ORM', 'Prisma', 'PostgreSQL', 'NestJS'. Unlikely to conflict with frontend or general coding skills due to specific backend terminology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%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 backend skill with excellent actionable code examples covering Prisma schemas, Zod validation, middleware patterns, and authentication flows. The main weaknesses are moderate verbosity in explanatory sections and missing explicit validation checkpoints in workflows beyond migrations. The content would benefit from better progressive disclosure by moving detailed patterns to separate reference files.
Suggestions
Add explicit validation checkpoints to the authentication flow (e.g., 'Verify token signature before proceeding', 'Check session exists in DB before generating new tokens')
Move detailed code patterns (middleware, service patterns, validators) to a separate reference file like 'backend-patterns.md' and keep SKILL.md as a concise overview
Remove explanatory sentences like 'O Backend define a fundação de dados e lógica de negócio' that don't add actionable value
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains useful patterns but includes some unnecessary verbosity, such as explaining basic concepts like 'O Backend define a fundação de dados e lógica de negócio' and listing obvious conventions. The code examples are good but some sections could be tightened. | 2 / 3 |
Actionability | Excellent executable code examples throughout - Prisma schema, Zod validators, middleware patterns, and service patterns are all copy-paste ready. The authentication flow is clearly documented with specific steps and the API patterns are concrete. | 3 / 3 |
Workflow Clarity | The migration strategy includes a good zero-downtime checklist with validation steps, but other workflows like the authentication flow lack explicit validation checkpoints. The skill doesn't provide clear feedback loops for error recovery in most processes. | 2 / 3 |
Progressive Disclosure | References external files appropriately (GLOBAL.md, policies, docs/skill-guides/backend-api.md) but the main content is quite long (~300 lines) with inline code that could be split into separate reference files. The structure is decent but could better separate quick-start from detailed patterns. | 2 / 3 |
Total | 9 / 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.
- Repository
- felvieira/claude-skills-fv
- Commit
524725e
- 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.