CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

backend-api

Projeta e implementa APIs, dados, autenticacao e logica 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".

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A dense, highly actionable backend reference with excellent decision-oriented guidance (idempotency requirements, migration checkpoint, per-route rate limiting) and mostly executable code. Its main weaknesses are token weight — long rationale paragraphs and two fully inlined stacks — and the absence of a single coherent top-level workflow tying the sections together.

Suggestions

Move the full resilience implementations (withRetry, CircuitBreaker) and the entire better-sqlite3 alternative stack (~120 lines) into a reference file, keeping only the decision rules and short usage examples in SKILL.md — the same gate-then-reference pattern already used for idempotency.

Trim rationale prose for concepts Claude already knows (thundering herd, circuit-breaker state semantics, why rate limiting per route matters) down to one-line decision rules.

Complete the middleware code snippets with imports and type annotations (verifyAccessToken, Role, Express handler types) so they compile as written.

DimensionReasoningScore

Conciseness

The ~680-line body is mostly actionable conventions and code, but includes explanatory prose for concepts Claude already knows ("Retry sem backoff crescente amplifica falha de serviço já sobrecarregado (thundering herd)", the circuit-breaker state walkthrough, and the RLS rationale paragraph), and inlines two complete stacks (Prisma/Express and better-sqlite3) that could be tightened or split out.

3 / 5

Actionability

Concrete, near copy-paste-ready code throughout: full Prisma schema, Zod validator patterns, numbered auth flows ("1. POST /auth/login { email, password } ... 6. Retorna { accessToken, user }"), and a complete better-sqlite3 repository. Minor gaps: middleware snippets omit imports and reference undefined helpers ("verifyAccessToken", "Role", untyped (req, res, next)).

4 / 5

Workflow Clarity

Multi-step processes are clearly sequenced with a strong validation checkpoint for the riskiest operation: "rodar UP em staging → confirmar ... → rodar DOWN e confirmar que volta ao estado anterior ... → só então promover para prod. Se qualquer passo falhar ... repetir o ciclo". However, there is no unified end-to-end workflow for the skill's main task; coverage is per-topic rather than one coherent sequence.

4 / 5

Progressive Disclosure

The one real reference file (references/idempotencia-e-postgres-avancado.md) is well signaled three times with clear purpose ("Detalhe completo (SQL de RLS, extensão btree_gist ...) em references/idempotencia-e-postgres-avancado.md") and is one level deep. Minor gaps: ~250 lines of alternative-stack and resilience implementation code (better-sqlite3 section, CircuitBreaker class) are inlined in SKILL.md where reference files would fit, and several referenced governance files (policies/*.md, docs/skill-guides/*.md) are not part of this bundle.

4 / 5

Total

15

/

20

Passed

Description

91%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person, concise, with an explicit trigger list that comprehensively covers both natural and technical vocabulary for the backend domain. The only weaknesses are slightly abstract capability nouns and a few overly broad trigger terms that could collide with adjacent skills.

DimensionReasoningScore

Specificity

"Projeta e implementa APIs, dados, autenticacao e logica de backend" lists several concrete capability areas (APIs, authentication, data) with only minor gaps — "dados" and "logica de backend" are comparatively abstract, which keeps it below the comprehensive anchor 5.

4 / 5

Completeness

Both parts are explicit: a clear "what" ("Projeta e implementa APIs, dados, autenticacao e logica de backend") and an explicit "when" clause equivalent ("Trigger em: 'API', 'endpoint', 'banco de dados' ...") with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

The trigger list has 17 terms covering natural user language ("API", "endpoint", "banco de dados", "backend", "servidor", "autenticação"), stack synonyms ("JWT", "ORM", "middleware"), and specific technologies ("Prisma", "PostgreSQL", "Node.js", "Express", "NestJS") — comprehensive coverage including both lay and technical phrasings.

5 / 5

Distinctiveness Conflict Risk

Stack-specific triggers ("Prisma", "NestJS", "ORM", "JWT") carve a clear backend niche, but broad terms like "schema", "API" and "banco de dados" create minor overlap risk with closely related skills (database administration, frontend API consumption).

4 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (683 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/03-backend-api/SKILL.md

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.