senior-backend

Designs and implements backend systems including REST APIs, microservices, database architectures, authentication flows, and security hardening. Use 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". Covers Node.js/Express/Fastify development, PostgreSQL optimization, API security, and backend architecture patterns.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Quality

Content

81%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.

The body is highly actionable with executable commands and well-sequenced, validated workflows, supported by a sound reference structure. Its main weaknesses are padded quick-reference sections that restate known concepts and dead links to a profiles/ directory and agents file that are absent from the bundle.

Suggestions

Remove or trim the "Common Patterns Quick Reference" (HTTP status codes, REST/error response shapes, basic index examples) since these are concepts Claude already knows — keep only tool-specific or non-obvious patterns.

Create the referenced profiles/ directory and agents/engineering/cs-backend-engineer.md, or remove the "Customization profiles" and "Invocation from other agents" sections that depend on them, so no referenced path is a dead link.

Add an explicit rollback-on-failure step to the Database Optimization workflow (the tool advertises rollback support) to close the feedback loop after the "Apply and verify" checkpoint.

Dimension	Reasoning	Score
Conciseness	The tool-usage and workflow sections are lean and earn their tokens, but the "Common Patterns Quick Reference" (HTTP status codes table, basic REST/error response shapes, single/composite/partial index examples) restates concepts Claude already knows, fitting "mostly efficient but includes some unnecessary explanation."	3 / 5
Actionability	Each of the three tools ships multiple copy-paste-ready commands with real flags (e.g. `api_scaffolder.py openapi.yaml --framework express --output src/routes/`, `--dry-run`, `--expect-rate-limit`), and the workflows wire concrete commands into numbered steps covering the common cases.	5 / 5
Workflow Clarity	The Database Optimization and Security Hardening workflows are explicitly sequenced with validation checkpoints (dry-run, "Apply and verify" re-analyze, `--expect-status 400`), and the forcing-question/assumptions sections add a checklist discipline — satisfying the anchor for explicit validation steps and feedback loops.	5 / 5
Progressive Disclosure	Structure is good with a clear Reference Documentation table and one-level-deep references to real files in references/ and scripts/, but the prominent "Customization profiles" section and invocation section reference profiles/ and agents/engineering/cs-backend-engineer.md that do not exist in the bundle — a navigation gap beyond minor.	4 / 5
	Total	17 / 20 Passed

Description

100%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.

The description is a strong, third-person statement that explicitly covers both capability and trigger conditions with concrete, natural phrases. It is comprehensive without padding and clearly distinguishable from neighboring skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "design REST APIs", "implement authentication", "build microservices", "handle database migrations", "load test APIs" — covering the backend domain comprehensively, matching the anchor for several specific concrete actions.	5 / 5
Completeness	Explicitly answers both what ("Designs and implements backend systems including REST APIs, microservices, database architectures, authentication flows, and security hardening") and when ("Use when the user asks to...") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	The "Use when the user asks to..." clause enumerates eight natural phrases a user would actually say ("design REST APIs", "optimize database queries", "set up GraphQL", "load test APIs"), giving comprehensive coverage of natural trigger terms.	5 / 5
Distinctiveness Conflict Risk	The niche is clearly backend engineering with distinct, specific triggers; overlap risk with adjacent skills (e.g. general security) is minimal because the triggers are narrowly backend-scoped.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: alirezarezvani/claude-skills
Path: engineering-team/skills/senior-backend/SKILL.md
Commit: 19392f7

Reviewed: ~8 hours ago

Table of Contents

Discovery Implementation Validation

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.