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.

54

Quality

61%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./tests/ext_conformance/artifacts/agents-wshobson/javascript-typescript/skills/nodejs-backend-patterns/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

29%

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

This skill is an extensive but bloated reference catalog of Node.js backend patterns. While the code examples are high-quality and executable, the skill massively over-explains concepts Claude already knows (Express setup, CRUD operations, Mongoose models, pg pools) and provides no workflow structure for actually building a backend service. It would benefit enormously from being split into focused sub-files with a concise overview, and from removing patterns that are standard knowledge.

Suggestions

Reduce the SKILL.md to a concise overview (~50-80 lines) with key decision points (e.g., when to use Express vs Fastify, layered vs other architectures) and move detailed code examples into separate bundle files like MIDDLEWARE.md, DATABASE.md, AUTH.md

Remove boilerplate code that Claude already knows how to write (basic Express/Fastify setup, standard CRUD controllers, basic Mongoose models) and focus only on project-specific conventions or non-obvious patterns

Add a clear workflow sequence for building a new backend service (e.g., 1. Set up project structure → 2. Configure database → 3. Implement auth → 4. Add middleware → 5. Validate with health check endpoint) with explicit verification steps

Remove the 15-item best practices list of obvious advice ('Use TypeScript', 'Use HTTPS', 'Write tests') as these waste tokens on things Claude already knows

DimensionReasoningScore

Conciseness

Extremely verbose at ~600+ lines. Includes massive boilerplate code blocks that Claude already knows how to write (basic Express setup, CRUD controllers, Mongoose models, pg connection pools). The 15-item best practices list states obvious things like 'Use TypeScript' and 'Use HTTPS'. Very little here is novel knowledge that Claude doesn't already possess.

1 / 3

Actionability

The code examples are fully executable TypeScript with proper imports, type annotations, and complete implementations. Every pattern shown is copy-paste ready with real libraries (express, fastify, pg, mongoose, jsonwebtoken, zod, ioredis).

3 / 3

Workflow Clarity

There is no sequenced workflow for building a backend service. The skill is a reference catalog of patterns with no clear ordering, no validation checkpoints, and no guidance on when to apply which pattern. For a skill involving database operations and authentication setup, there are no verification steps.

1 / 3

Progressive Disclosure

Monolithic wall of text with all content inline. Hundreds of lines of code that should be split into separate reference files (e.g., database patterns, auth patterns, middleware patterns). The only reference is to a separate testing skill and external URLs. No bundle files exist to support any decomposition.

1 / 3

Total

6

/

12

Passed

Description

92%

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

This is a strong skill description that clearly communicates both capabilities and trigger conditions. It names specific frameworks, patterns, and use cases with natural trigger terms. The only weakness is its broad scope, which could create overlap with more specialized skills covering authentication, database integration, or GraphQL individually.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: middleware patterns, error handling, authentication, database integration, and API design best practices, along with specific frameworks (Express/Fastify).

3 / 3

Completeness

Clearly answers both 'what' (build production-ready Node.js backend services with specific patterns and practices) and 'when' (explicit 'Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures').

3 / 3

Trigger Term Quality

Includes strong natural keywords users would say: 'Node.js', 'Express', 'Fastify', 'REST APIs', 'GraphQL', 'microservices', 'backend', 'servers', 'middleware', 'authentication'. These cover a wide range of terms a developer would naturally use.

3 / 3

Distinctiveness Conflict Risk

While it specifies Node.js and particular frameworks, the scope is quite broad covering REST APIs, GraphQL, microservices, authentication, and database integration — areas that could overlap with database-specific skills, auth-specific skills, or general API design skills.

2 / 3

Total

11

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

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

Warning

Total

10

/

11

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.