nodejs-best-practices

Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.

Quality

47%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./.agent/skills/nodejs-best-practices/SKILL.md

Quality

Content

62%

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

This skill effectively teaches decision-making principles for Node.js development with clear decision trees and comparison tables. However, it sacrifices actionability by avoiding concrete code examples entirely, and the monolithic structure could benefit from progressive disclosure to separate reference material. Some content explains concepts Claude already knows (HTTP status codes, module systems).

Suggestions

Add at least one executable code example per major section (e.g., actual Zod validation schema, actual error middleware implementation) to improve actionability while maintaining the principles-first approach

Split detailed reference content (security checklist, testing tools comparison) into separate files and link from the main skill to improve progressive disclosure

Remove explanations of concepts Claude knows well (HTTP status code meanings, ESM vs CommonJS basics) to improve conciseness

Dimension	Reasoning	Score
Conciseness	The skill is reasonably efficient but includes some unnecessary explanations Claude would know (e.g., explaining what ESM vs CommonJS is, basic HTTP status codes). The ASCII decision trees add visual bulk that could be tightened.	2 / 3
Actionability	Provides decision frameworks and principles but lacks executable code examples. The content describes patterns conceptually ('Create custom error classes', 'Throw from any layer') without showing actual implementation. This is intentional per the skill's philosophy but reduces immediate actionability.	2 / 3
Workflow Clarity	Clear decision trees and checklists guide multi-step decision-making. The layered architecture flow, validation boundaries, and decision checklist at the end provide explicit sequences. For a principles-focused skill, the workflows are well-structured.	3 / 3
Progressive Disclosure	Content is well-organized with clear sections and headers, but it's a monolithic document with no references to external files for deeper dives. The 200+ lines could benefit from splitting detailed sections (security, testing) into separate reference files.	2 / 3
	Total	9 / 12 Passed

Description

32%

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 its domain (Node.js) and lists relevant topic areas, but lacks concrete action verbs and explicit trigger guidance. The phrase 'Teaches thinking, not copying' is philosophical but doesn't help Claude determine when to select this skill. Without a 'Use when...' clause, Claude cannot reliably choose this skill from a large skill library.

Suggestions

Add an explicit 'Use when...' clause with trigger scenarios like 'Use when the user asks about Node.js architecture decisions, choosing between Express/Fastify/Nest, handling async/await patterns, or securing Node applications'

Replace abstract categories with concrete actions: instead of 'Framework selection', try 'Guides choosing between Express, Fastify, Koa, and NestJS based on project requirements'

Include common user terms and file extensions: 'package.json', 'npm', 'backend API', 'server-side JavaScript', 'middleware'

Dimension	Reasoning	Score
Specificity	Names the domain (Node.js development) and lists several areas (framework selection, async patterns, security, architecture), but these are categories rather than concrete actions. No specific verbs describing what the skill actually does.	2 / 3
Completeness	Describes what areas it covers but has no explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is entirely missing, and 'Teaches thinking, not copying' is vague about actual usage scenarios.	1 / 3
Trigger Term Quality	Includes relevant terms like 'Node.js', 'framework selection', 'async patterns', 'security', 'architecture', but missing common variations users might say like 'Express', 'npm', 'backend', 'API', 'server-side JavaScript'.	2 / 3
Distinctiveness Conflict Risk	Node.js is a specific technology which helps, but 'development principles', 'security', and 'architecture' are broad enough to potentially overlap with general coding skills or other language-specific skills.	2 / 3
	Total	7 / 12 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: lchenrique/politron-ide
Commit: 7114206

Reviewed: 5 months 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.