CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

nodejs-best-practices

Node.js best practices e patterns

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 ./skills/backend/nodejs/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 a lean, well-organized conventions reference with mostly executable code examples for both Express and NestJS. Its main weaknesses are the stubbed NestJS error filter, the unbacked 'Testes configurados' checklist item, and the absence of any sequenced workflow linking the convention sections together.

Suggestions

Complete the NestJS AllExceptionsFilter stub with real handling code and show constructor injection of UsersService so both NestJS examples are copy-paste ready.

Back the 'Testes configurados' checklist item with concrete guidance, e.g., a minimal Jest setup snippet and the npm test script command.

Add a brief sequenced workflow (choose Express vs NestJS, scaffold the structure, add error handling, configure env vars, set up tests) so the sections read as a process with the checklist as the verification step.

DimensionReasoningScore

Conciseness

The body is lean and code-forward with no padded prose — sections are headers, short framing lines, code blocks, and directory trees. Minor instances could be trimmed (the hello-world Express route and basic dotenv require re-teach what Claude already knows), matching anchor 4 rather than anchor 5's 'every token earns its place'.

4 / 5

Actionability

Most guidance is concrete and executable — the Express route, error-handling middleware, dotenv config, and both directory trees are copy-paste ready. Minor gaps prevent anchor 5: the NestJS AllExceptionsFilter is a '// Handle error' stub and the UsersController references an uninjected this.usersService.

4 / 5

Workflow Clarity

The body presents independent convention sections with no sequenced process connecting them; the final checklist gestures at validation but has no checkpoints or feedback loops. This matches anchor 3 rather than anchor 2 because the checklist and clear organization exist, and the ~118-line multi-topic body does not qualify for the simple-skill exception to score 5.

3 / 5

Progressive Disclosure

A single, well-sectioned file with clear headers (Framework, Estrutura, Error Handling, Environment Variables, Checklist) that is easy to navigate, with nothing that clearly belongs in a separate file — anchor 4. Not anchor 5 because the body exceeds 50 lines and topics implied by the checklist and sources (testing, security) have no referenced deep-dives.

4 / 5

Total

15

/

20

Passed

Description

36%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 a bare topic label: it names the Node.js domain but states no concrete capabilities and gives no usage timing within the description field itself. The separate triggers field carries the trigger guidance, leaving the description thin on both specificity and completeness.

Suggestions

State concrete capabilities in the description, e.g., 'Applies Node.js conventions for project structure, error handling middleware, environment-variable configuration, and Express/NestJS application scaffolding.'

Add an explicit 'Use when...' clause to the description itself, e.g., 'Use when building or reviewing Node.js, Express, or NestJS services, or when structuring/configuring a Node.js codebase.'

Surface natural trigger terms (node, backend, API, TypeScript, REST) in the description rather than relying solely on the separate triggers field.

DimensionReasoningScore

Specificity

The description 'Node.js best practices e patterns' names the domain but contains no concrete actions — 'best practices e patterns' is a generic topic label, matching anchor 2. It is above anchor 1 because the domain is explicitly named, but below anchor 3 because no concrete capability (analogous to 'extracts content') is stated.

2 / 5

Completeness

The 'what' is stated only at topic level (Node.js best practices and patterns) and the 'when' is absent from the description itself, though equivalent trigger guidance exists via the frontmatter triggers field. Per the guideline, the missing 'Use when...' clause caps completeness at 3; the vague, action-less 'what' keeps it from rising further.

3 / 5

Trigger Term Quality

'Node.js' is exactly the natural term a user would say when needing this skill, but the description itself omits common variations and synonyms (express, API, backend, server, npm, TypeScript) that only appear in the separate triggers field. This matches anchor 3 — relevant keyword present, variations missing — rather than anchor 4's 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

'Node.js' scopes the skill to a distinct runtime, but 'best practices e patterns' spans frameworks (Express, NestJS), tooling (npm, yarn), and language (TypeScript), creating overlap risk with dedicated skills for each. Anchor 3 fits — somewhat specific but could overlap with similar skills — rather than anchor 4's 'minor overlap risk'.

3 / 5

Total

11

/

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.

Validation — 15 / 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

fernandezbaptiste/cursor-multiagent-system

Path

skills/backend/nodejs/SKILL.md

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.