CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

78%

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

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/javascript-typescript/skills/nodejs-backend-patterns/SKILL.md

The canonical home for this skill is nodejs-backend-patterns in wshobson/agents

SKILL.md
Quality
Evals
Security

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 body is highly actionable—dense with executable TypeScript patterns across the full backend stack—but it is monolithic and long, with no progressive disclosure to bundle files and no sequenced workflow with validation checkpoints for its destructive database operations.

Suggestions

Split the large code catalogs (layered architecture, DI container, middleware, database patterns) into one-level-deep reference files under references/ and keep SKILL.md as a concise overview with signaled links.

Trim repeated full CRUD implementations to a single representative example per layer to reduce token volume while preserving the pattern.

Add an explicit build-and-verify workflow with validation checkpoints (e.g., run tests, confirm DB migrations, validate endpoint responses) for destructive/batch database operations to raise workflow clarity above the cap of 3.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows, but at ~1000 lines it dumps full CRUD implementations across controller/service/repository layers, a complete DI container, and several full middleware files—material that could be trimmed to representative patterns, fitting "mostly efficient but could be tightened."

3 / 5

Actionability

Nearly every section provides complete, copy-paste-ready TypeScript with real imports covering controllers, services, repositories, auth, validation, rate limiting, databases, transactions, caching, and API responses, matching the fully-executable score-5 anchor.

5 / 5

Workflow Clarity

The content is a well-organized pattern catalog rather than a sequenced workflow, and destructive/batch database operations (transactions, deletes) lack explicit validation feedback loops, capping this at 3 per the rubric guideline.

3 / 5

Progressive Disclosure

Section headers give reasonable structure, but no bundle files exist and ~1000 lines of pattern code that clearly belongs in separate reference files are inlined entirely in SKILL.md, matching "some structure... content that should be separate is inline."

3 / 5

Total

14

/

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 uses third-person voice, names a clear niche, and pairs a concrete capability list with an explicit "Use when" trigger clause. Its only soft spot is trigger-term coverage, which is good but omits a few natural synonyms.

DimensionReasoningScore

Specificity

"implementing middleware patterns, error handling, authentication, database integration, and API design best practices" lists multiple specific concrete capability areas with comprehensive coverage of the Node.js backend domain, matching the score-5 anchor.

5 / 5

Completeness

It explicitly answers both what ("Build production-ready Node.js backend services...") and when ("Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures") with concrete trigger phrases, matching the score-5 anchor exactly.

5 / 5

Trigger Term Quality

"Node.js servers, REST APIs, GraphQL backends, or microservices architectures" plus "Express/Fastify" are natural phrases users say, but common synonyms (e.g., "web server", "backend API", "HTTP API") are missing and there are no file-extension-style triggers, fitting score 4.

4 / 5

Distinctiveness Conflict Risk

The description carves a clear niche (Node.js backend services with Express/Fastify) anchored by distinct triggers (REST APIs, GraphQL backends, microservices), yielding minimal conflict risk with unrelated skills.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

Total

15

/

16

Passed

Repository
Dicklesworthstone/pi_agent_rust
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.