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

44%

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

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

Quality

Content

40%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 skill is appropriately lean but offers no concrete, executable guidance: its instructions are generic platitudes and the single detailed reference points to a file that does not exist. As written it cannot guide real backend work.

Suggestions

Replace the abstract Instructions bullets with concrete guidance — at minimum a project-structure skeleton, a sample Express/Fastify route with error-handling middleware, and an example auth middleware snippet.

Create resources/implementation-playbook.md (or fix the path) so the referenced detailed patterns/examples actually resolve, restoring progressive-disclosure navigation.

Turn the Instructions into a sequenced workflow with explicit validation checkpoints (e.g. "after adding a route, run the test suite; only proceed when passing") instead of generic steps.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with no padding or basic-concept explanations, though the opening sentence duplicates the frontmatter description — a minor instance of over-explanation that could be trimmed.	4 / 5
Actionability	Instructions are high-level hints ("Clarify goals… Apply relevant best practices and validate outcomes") with no concrete code, commands, or specific patterns, and the only detailed reference (resources/implementation-playbook.md) does not exist, fitting "minimal concrete guidance; high-level hints but missing the specific steps to execute."	2 / 5
Workflow Clarity	A rough three-bullet sequence exists but steps are generic and poorly defined, with validation mentioned only abstractly ("validate outcomes", "verification") and no concrete checkpoints, fitting the "rough sequence present but many gaps; validation absent/implicit" anchor.	2 / 5
Progressive Disclosure	The body signals a one-level-deep reference to resources/implementation-playbook.md, but that file is absent from the bundle, so navigation is broken — structure is minimal and the reference cannot be followed.	2 / 5
	Total	10 / 20 Passed

Description

48%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 identifies a clear niche but is padded with abstract buzzwords and lacks concrete capabilities or an explicit use-trigger, capping its completeness and specificity. It is distinguishable but reads more like a tagline than an actionable skill description.

Suggestions

Replace abstract adjectives ("scalable, maintainable, production-ready… modern frameworks, best practices") with concrete actions the skill performs, e.g. "Design REST/GraphQL APIs, structure service layers, add auth and error-handling middleware."

Add an explicit "Use when…" clause naming natural user phrasing (e.g. "Use when building a Node.js backend, REST API, or microservice") to satisfy the "when" half of completeness.

Dimension	Reasoning	Score
Specificity	The description names the domain ("building scalable, maintainable, and production-ready Node.js backend applications") but offers no concrete actions — it says "guidance for building" rather than listing what it does, fitting the "names domain but actions minimal or generic" anchor.	2 / 5
Completeness	It gives a clear "what" (guidance for building Node.js backends) but has no "Use when…" clause or equivalent trigger guidance, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	"Node.js backend applications" is a relevant natural term, but it is padded with generic buzzwords ("modern frameworks, architectural patterns, and best practices") and lacks common synonyms or extensions, fitting "some relevant keywords but missing common variations."	3 / 5
Distinctiveness Conflict Risk	"Node.js backend applications" carves out a mostly-distinct niche with minor overlap risk against general web-development skills, fitting "mostly distinct; minor overlap risk with closely related skills."	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

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

	Total	15 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/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.