CtrlK
BlogDocsLog inGet started
Tessl Logo

lirantal/nodejs-cli-best-practices

Guide and audit Node.js CLI application development against 41 established best practices covering UX, distribution, interoperability, accessibility, testing, error handling, development setup, analytics, versioning, and security. Use this skill when building, extending, reviewing, or scaffolding a Node.js CLI — including when someone says "audit my CLI", "review my CLI code", "I'm building a CLI tool", or asks about adding argument parsing, help output, shell completion/autocomplete, error handling, color output, STDIN, --json flags, exit codes, --version flags, or npm publishing. Applies even when best practices are not explicitly mentioned. Also trigger for "how should I implement X in my CLI" or "what's the right way to do Y in a Node.js CLI". Do NOT use for Node.js backend or API development with no CLI entry point.

70

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Overview
Quality
Evals
Security
Files

Quality

Content

72%

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

The content is well-structured and highly actionable with strong progressive disclosure, deferring the full practice catalog to a single clearly-signaled reference file. Its main weaknesses are mild redundancy between the quick-reference table and the phase list, and the absence of explicit validation/feedback checkpoints in the workflows.

Suggestions

Collapse the "Quick reference: which section applies" table into the development-guide phase list (or replace one with the other) to remove the overlapping section-to-topic mapping.

Add an explicit validation checkpoint to the audit workflow, e.g. "After drafting the report, re-scan the code against references/best-practices.md to confirm no applicable practice was missed".

Trim restated guidance in the "Common mistakes to avoid" table where it duplicates the inline instructions above (e.g. the shrinkwrap and priority-grouping rows).

DimensionReasoningScore

Conciseness

The body is dense and operational with no concept padding, but the "Quick reference: which section applies" table substantially overlaps the development-guide phase list and some inline guidance is restated in the "Common mistakes" table, so it could be tightened.

2 / 3

Actionability

Provides concrete format templates for audit reports and dev guidance, specific section references (e.g. §6.4, §9.1), and copy-pasteable fixes like the process.exit(1)/process.exit(0) example, with executable structure throughout.

3 / 3

Workflow Clarity

The two-mode workflow is clearly sequenced with a decision table and per-example numbered steps, but there are no explicit validation/feedback checkpoints (e.g. re-verify the audit against the reference) to recover from errors.

2 / 3

Progressive Disclosure

SKILL.md is a clean overview that offloads all 41 practices with code to the verified references/best-practices.md, with a prominent "Always read" signal and §X.Y section references for one-level-deep navigation.

3 / 3

Total

10

/

12

Passed

Description

100%

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 strong across all dimensions: it states concrete capabilities, provides rich natural-language triggers, answers both what and when, and scopes a clear niche with an explicit exclusion. It uses third person throughout with no voice violations.

DimensionReasoningScore

Specificity

Names multiple concrete actions ("Guide and audit", "building, extending, reviewing, or scaffolding") and enumerates 10 domains plus specific feature topics, matching the comprehensive-actions anchor.

3 / 3

Completeness

Explicitly answers both what (guide/audit Node.js CLI dev against 41 practices) and when via a clear "Use this skill when..." clause plus additional "Also trigger for..." guidance.

3 / 3

Trigger Term Quality

Strong coverage of natural phrasings users would say ("audit my CLI", "review my CLI code", "I'm building a CLI tool", "how should I implement X in my CLI") alongside concrete feature keywords like --json, --version, and shell completion.

3 / 3

Distinctiveness Conflict Risk

Niche is clearly scoped to Node.js CLIs with distinct triggers and an explicit negative boundary ("Do NOT use for Node.js backend or API development with no CLI entry point"), making conflict unlikely.

3 / 3

Total

12

/

12

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

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents