CtrlK
BlogDocsLog inGet started
Tessl Logo

nodejs-best-practices

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

54

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

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-best-practices/SKILL.md

The canonical home for this skill is nodejs-best-practices in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 content is a well-organized, concrete decision reference that avoids over-explaining basics, but it is monolithic with no progressive disclosure, repeats its core philosophy across several sections, and scatters time-sensitive version/date markers without a deprecated-patterns section.

Suggestions

Consolidate the repeated decision-making philosophy ('How to Use', 'Anti-Patterns DO/DONT', 'Decision Checklist', closing 'Remember') into a single section to remove redundancy.

Move version- and year-sensitive details (e.g., '(2025)', 'Node.js 22+', '--experimental-strip-types') into a dedicated 'Current runtime notes' or 'Deprecated/old patterns' section so they don't penalize conciseness.

Split the heavier reference material (framework comparison tables, security checklist) into reference files linked one level deep from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient using tables and ASCII trees without explaining basic concepts, but it carries redundancy (the decision-making philosophy is restated in 'How to Use', 'Anti-Patterns', 'Decision Checklist', and the closing 'Remember') and scatters time-sensitive markers like '(2025)' and 'Node.js 22+' outside any deprecated section, which the rubric penalizes.

3 / 5

Actionability

Guidance is concrete and specific — named frameworks (Hono, Fastify, NestJS), a status-code table, and named validation libraries (Zod, Valibot) — giving mostly executable decision guidance; absence of code is acceptable for an instruction skill, but it stops short of 5 because there are almost no copy-paste commands or examples.

4 / 5

Workflow Clarity

The framework decision tree and the pre-implementation checklist provide a rough sequence, but there are no explicit validation checkpoints or feedback loops, and the skill is a reference/principles guide rather than a sequenced process, so it sits at the steps-present-but-checkpoints-implicit anchor.

3 / 5

Progressive Disclosure

The file is well-sectioned with clear numbered headers, but it is a monolithic single file with no bundle references, and content that could be split out (framework comparisons, security checklist) is inlined; the simple-skill exception does not apply given its length.

3 / 5

Total

13

/

20

Passed

Description

66%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 is specific and covers several concrete Node.js domains with natural trigger terms, but it omits any explicit "Use when..." trigger clause, capping its completeness. It is distinctive but slightly broad within the Node.js niche.

Suggestions

Add an explicit "Use when..." clause naming the user situations that should activate this skill (e.g., 'Use when making Node.js framework, async, or security decisions').

Include a few natural synonyms or specific trigger phrases users say (e.g., 'Express vs Fastify', 'Node API design') to broaden trigger coverage.

Tighten the philosophical tagline ('Teaches thinking, not copying') or move it into the body so the description stays purely about capabilities and triggers.

DimensionReasoningScore

Specificity

Names the Node.js domain and lists several concrete capability areas ("Framework selection, async patterns, security, and architecture"), comparable to the several-specific-actions anchor, but these are topic domains rather than discrete executable actions so it stops short of 5.

4 / 5

Completeness

The "what" is clear (development principles and decision-making across four areas), but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms a user would say are present ("Node.js", "framework", "async patterns", "security", "architecture"), giving good keyword coverage; it misses common synonyms and specific product names that would push it to 5.

4 / 5

Distinctiveness Conflict Risk

The Node.js framing carves a mostly distinct niche with minimal conflict risk against non-JS skills, though "development principles" is broad enough to overlap with general backend or architecture skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
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.