backend-development

Production backend systems development. Stack: Node.js/TypeScript, Python, Go, Rust | NestJS, FastAPI, Django, Express | PostgreSQL, MongoDB, Redis. Capabilities: REST/GraphQL/gRPC APIs, OAuth 2.1/JWT auth, OWASP security, microservices, caching, load balancing, Docker/K8s deployment. Actions: design, build, implement, secure, optimize, deploy, test APIs and services. Keywords: API design, REST, GraphQL, gRPC, authentication, OAuth, JWT, RBAC, database, PostgreSQL, MongoDB, Redis, caching, microservices, Docker, Kubernetes, CI/CD, OWASP, security, performance, scalability, NestJS, FastAPI, Express, middleware, rate limiting. Use when: designing APIs, implementing auth/authz, optimizing queries, building microservices, securing endpoints, deploying containers, setting up CI/CD.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

65%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 SKILL.md body is an effective overview index with excellent progressive disclosure into real reference files, but it leans on high-level checklists and time-sensitive stat-drops instead of executable code or explicit validation gates in its workflows.

Suggestions

Move or date-stamp the 2025-specific statistics (e.g. "98% SQL injection reduction", "Kubernetes 84% adoption", "Vitest 50% faster than Jest") into a dedicated "current guidance" or "deprecated/old patterns" section so they do not penalize conciseness as they age.

Add one or two short executable snippets (e.g. a minimal REST endpoint skeleton or a parameterized-query example) to the body so the most common cases are actionable without opening a reference file.

Convert the arrow-notation checklists into numbered steps with explicit validation gates (e.g. "Run tests → only proceed on green") so workflows include clear validate-then-proceed feedback loops.

Dimension	Reasoning	Score
Conciseness	The body is token-efficient (tables, decision matrix, arrow-notation checklists) and avoids explaining concepts Claude already knows, but time-sensitive items like "Key Best Practices (2025)", "98% SQL injection reduction", and "Vitest 50% faster than Jest" are padding not housed in a deprecated/old-patterns section, keeping it below the lean level 5.	4 / 5
Actionability	The decision matrix and checklists give concrete guidance (e.g. "API: Choose style → Design schema → Validate input → Add auth → ..."), but the body contains no executable code or commands and defers implementation detail to the reference files, fitting the incomplete-guidance anchor rather than the mostly-executable level 4.	3 / 5
Workflow Clarity	Checklists provide clear sequences, but validation is implicit (terminal items like "Test performance", "Health checks") rather than explicit validate-then-proceed gates or fix-and-retry feedback loops, matching the present-sequence-but-implicit-checkpoints anchor.	3 / 5
Progressive Disclosure	The body is a clear overview pointing to 11 well-signaled, one-level-deep reference files grouped by category (Core Technologies, Security & Authentication, Performance & Architecture, Quality & Operations), all of which exist in references/, matching the clear-overview anchor exactly.	5 / 5
	Total	15 / 20 Passed

Description

96%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 dense, well-structured description that explicitly covers what the skill does, when to use it, and a broad set of natural trigger keywords. The only weakness is modest overlap with devops and security skills in its deployment and CI/CD triggers.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions ("design, build, implement, secure, optimize, deploy, test APIs and services") alongside a detailed Capabilities list (REST/GraphQL/gRPC APIs, OAuth 2.1/JWT auth, microservices, caching), giving comprehensive coverage rather than the single-action or minor-gap levels below.	5 / 5
Completeness	It explicitly answers "what" ("Production backend systems development" plus Capabilities) and "when" ("Use when: designing APIs, implementing auth/authz, optimizing queries, building microservices, securing endpoints, deploying containers, setting up CI/CD") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	The explicit Keywords section covers natural terms users say ("API design, REST, GraphQL, authentication, OAuth, JWT, PostgreSQL, Docker, Kubernetes, CI/CD, rate limiting") with synonyms (Docker/Kubernetes, OAuth/JWT), matching the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	The backend stack and trigger phrases carve a mostly-distinct niche, but CI/CD, Docker/K8s deployment, and microservices triggers overlap with closely related devops/architecture skills, so it is not quite minimal-conflict level 5.	4 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: samhvw8/dot-claude
Path: skills/backend-development/SKILL.md
Commit: 28c7616

Reviewed: 23 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.