nodejs-backend-patterns

Comprehensive guidance for building scalable, maintainable, and production-ready Node.js backend applications with modern frameworks, architectural patterns, and best practices.

Quality

28%

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/AI-Agents-Safe-Coding-Skills/skills/nodejs-backend-patterns/SKILL.md

The canonical home for this skill is nodejs-backend-patterns in rmyndharis/antigravity-skills

Quality

Content

25%Scale 1-5

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

This skill is essentially a placeholder that lists broad use cases and delegates all substance to a referenced file that doesn't exist in the bundle. The instructions are entirely generic and could apply to any domain ('clarify goals, apply best practices, validate outcomes'), providing zero Node.js-specific actionable guidance. Without concrete code examples, specific patterns, or executable steps, this skill adds no value beyond what Claude already knows.

Suggestions

Add concrete, executable code examples for at least the most common use cases (e.g., Express/Fastify route setup, middleware pattern, error handling middleware, database connection pattern).

Replace the generic instructions ('Clarify goals, apply best practices') with specific, actionable steps for building a Node.js backend, such as project structure conventions, recommended libraries, and configuration patterns.

Either include the referenced `resources/implementation-playbook.md` in the bundle or inline the essential patterns directly in the SKILL.md so the skill is self-contained enough to be useful.

Add a concrete workflow with validation steps for at least one end-to-end scenario (e.g., setting up a new API endpoint with tests and verification).

Dimension	Reasoning	Score
Conciseness	The 'Use this skill when' and 'Do not use this skill when' sections are somewhat padded and explain things Claude could infer. The instructions section is brief but generic. The overall content is not severely verbose but includes unnecessary framing.	3 / 5
Actionability	The skill provides no concrete code, commands, or specific executable guidance. The instructions are entirely vague ('Clarify goals', 'Apply relevant best practices', 'Provide actionable steps') and delegate everything to a referenced file that doesn't exist in the bundle.	1 / 5
Workflow Clarity	There is a rough sequence implied ('clarify goals, apply best practices, validate outcomes') but no concrete steps, no validation checkpoints, and no specific workflow for any of the listed use cases. The steps are poorly defined and generic.	2 / 5
Progressive Disclosure	The skill references `resources/implementation-playbook.md` for detailed patterns, which is a reasonable structure, but no bundle files are provided so the reference leads nowhere. The SKILL.md itself contains almost no substantive content, making it an empty shell rather than a useful overview.	2 / 5
	Total	8 / 20 Passed

Description

32%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 heavy on buzzwords ('scalable, maintainable, production-ready') but light on concrete actions and trigger guidance. It identifies the domain (Node.js backend) but fails to specify what concrete tasks the skill helps with or when Claude should select it. The lack of specific frameworks, patterns, or use-case triggers makes it poorly suited for skill selection among a large set of skills.

Suggestions

Add a 'Use when...' clause with specific trigger terms like 'Node.js project', 'Express app', 'REST API', 'backend server', 'middleware setup'.

Replace vague buzzwords with concrete actions such as 'Sets up Express/Fastify routes, configures middleware, implements authentication, structures project directories, connects to databases'.

Include specific framework names and technologies (Express, Fastify, NestJS, Prisma, etc.) to improve trigger term quality and distinctiveness from general coding skills.

Dimension	Reasoning	Score
Specificity	Names the domain (Node.js backend applications) but actions are vague and generic — 'building scalable, maintainable, and production-ready' are buzzwords rather than concrete actions. No specific capabilities like 'set up Express routes', 'configure middleware', or 'implement authentication' are mentioned.	2 / 5
Completeness	Has a vague 'what' (guidance for building Node.js apps) but no 'when' clause at all. There is no 'Use when...' or equivalent trigger guidance, and per the rubric, a missing 'Use when...' clause caps completeness at 3, but the 'what' itself is also quite vague, placing this at a 2.	2 / 5
Trigger Term Quality	Includes 'Node.js', 'backend applications', and 'frameworks' which are relevant keywords users might say. However, it misses common natural terms like 'Express', 'API', 'REST', 'server', 'middleware', 'database', 'TypeScript', or specific framework names that users would naturally mention.	3 / 5
Distinctiveness Conflict Risk	Very broad description that could overlap with any web development, JavaScript, API development, or general coding skill. Terms like 'scalable', 'maintainable', 'production-ready', 'best practices' are generic enough to conflict with many other skills.	2 / 5
	Total	9 / 20 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

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

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/nodejs-backend-patterns/SKILL.md
Commit: 57c135b

Reviewed: 3 days 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.