nodejs-backend-patterns

Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.

Quality

64%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/javascript-typescript/skills/nodejs-backend-patterns/SKILL.md

Quality

Content

36%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 an overview that leans on generic best-practice bullets and defers real guidance to a reference file, leaving it light on executable content and workflow structure. Navigation is partially wired but one bundle file is unreachable.

Suggestions

Replace the generic Best Practices list with a few concrete, copy-paste-ready code snippets (e.g., an Express error-handling middleware, a Zod validation guard, a graceful-shutdown hook) or move it into references/details.md and link to it.

Add at least one sequenced workflow with a validation checkpoint — e.g., define route → validate input with Zod → handle errors → test — so multi-step backend tasks have explicit guidance.

Link references/advanced-patterns.md from the body (and confirm details.md does not redundantly cover it) so every bundle file is discoverable one level deep.

Dimension	Reasoning	Score
Conciseness	The 15-item Best Practices list is terse but largely restates common knowledge Claude already has ('Use TypeScript', 'Use HTTPS', 'Never hardcode secrets'), and each bullet's mini-justification could be trimmed, fitting 'mostly efficient but could be tightened'.	3 / 5
Actionability	The body offers only high-level hints and named libraries (Pino, Winston, Zod, Joi) with no code, commands, or concrete steps; executable guidance is deferred to references/details.md, matching 'minimal concrete guidance; missing specific steps'.	2 / 5
Workflow Clarity	There is no real multi-step workflow sequence — only a numbered list of generic best-practice tips — and validation checkpoints are entirely absent, fitting 'rough sequence present but steps poorly defined; validation absent'.	2 / 5
Progressive Disclosure	SKILL.md acts as an overview with a clearly signaled one-level pointer to references/details.md, but the bundled references/advanced-patterns.md is orphaned (never linked) and the 15-item best-practices list is inline content that arguably belongs in a reference file.	3 / 5
	Total	10 / 20 Passed

Description

92%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 strong: it concisely states concrete capabilities and provides explicit, natural-language trigger guidance. Third-person voice is used throughout with no padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (middleware patterns, error handling, authentication, database integration, API design) with comprehensive coverage of backend concerns, matching the 'comprehensive coverage' anchor.	5 / 5
Completeness	Explicitly answers both what (build production-ready services with specific patterns) and when ('Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms users would say ('Node.js servers', 'REST APIs', 'GraphQL backends', 'microservices architectures') with good coverage, but a few natural variations (e.g., 'backend', 'API server') and file extensions are absent, so it sits just below the comprehensive anchor.	4 / 5
Distinctiveness Conflict Risk	Has a clear niche (Node.js backend services) with distinct triggers and minimal overlap risk with unrelated skills.	5 / 5
	Total	19 / 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: wshobson/agents
Path: plugins/javascript-typescript/skills/nodejs-backend-patterns/SKILL.md
Commit: d6837ae

Reviewed: about 11 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.