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

65%

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 ./skills/nodejs-backend-patterns/SKILL.md

Quality

Content

43%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 concise and well-organized with clear use/don't-use sections and a single signaled reference, but it lacks any concrete executable guidance and points to a resource file that is missing from the bundle. This makes it more of a stub than an actionable skill.

Suggestions

Add at least one concrete, copy-paste-ready example in the body (e.g., a minimal Express/Fastify server snippet with error-handling middleware) so the skill is actionable without requiring the external file.

Include explicit, runnable validation checkpoints in the Instructions (e.g., 'lint with eslint', 'run tests with npm test') instead of the abstract 'validate outcomes' directive.

Create the referenced `resources/implementation-playbook.md` file or remove the dangling reference so progressive-disclosure navigation resolves to real content.

Dimension	Reasoning	Score
Conciseness	The body is lean with no over-explanation of concepts Claude already knows; the only padding is the marketing-style intro line 'Comprehensive guidance for building scalable, maintainable, and production-ready...'.	4 / 5
Actionability	The Instructions are high-level directives — 'Clarify goals, constraints, and required inputs', 'Apply relevant best practices and validate outcomes' — with no concrete code, commands, or specific steps to execute, relying entirely on an external file.	2 / 5
Workflow Clarity	Only a rough, generic sequence is present with no concrete validation checkpoints or feedback loops; 'validate outcomes' and 'verification' are mentioned abstractly without any executable check.	2 / 5
Progressive Disclosure	The reference to `resources/implementation-playbook.md` is clearly signaled and one level deep, but the referenced file and resources/ directory do not exist in the bundle, so the navigation target is broken.	3 / 5
	Total	11 / 20 Passed

Description

87%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 strong, well-structured description that concretely states capabilities and gives explicit, natural trigger conditions for activation. The only soft spot is keyword/synonym breadth, which keeps trigger_term_quality and specificity just below maximum.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'middleware patterns, error handling, authentication, database integration, and API design best practices' — over a named domain, with only minor coverage gaps; not quite the comprehensive multi-action list of a 5.	4 / 5
Completeness	Explicitly answers both 'what' (build backend services with listed capabilities) and 'when' via a concrete 'Use when creating...' clause with multiple trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user-facing terms — 'Node.js servers, REST APIs, GraphQL backends, or microservices architectures' — with good coverage, though a few common synonyms or file/tech markers are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Node.js backend niche with distinct, specific triggers; minimal realistic overlap with unrelated skills.	5 / 5
	Total	18 / 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: rmyndharis/antigravity-skills
Path: skills/nodejs-backend-patterns/SKILL.md
Commit: 3eff4af

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