CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

commanderjs

Complete Commander.js CLI framework guidance covering command structure, options, arguments, subcommands, action handlers, version management, and TypeScript integration. Use when: building CLI tools, parsing command-line arguments, implementing subcommands, handling options/flags, creating interactive CLIs, or migrating from other CLI frameworks. Keywords: Commander.js, CLI, command-line, arguments, options, flags, subcommands, action handlers, version, help text, TypeScript, yargs, meow, program, parseAsync, opts, args, variadic, required options, default values, custom help, error handling

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

A strong, executable overview with a clear navigation structure, an explicit validation step in the workflow, and verified one-level-deep reference files. The main weakness is redundancy: Do's/Don'ts/Anti-Patterns restate the same handful of rules multiple times, and Navigation Workflow duplicates the How to Use reference list.

Suggestions

Merge the 'Do's' and 'Don'ts' checklists into the 'Anti-Patterns' section so each rule is stated once with WHY/BAD/GOOD, removing roughly 60 lines of duplication (the typed-options-object, option-scope, and parseAsync rules currently appear 3-5 times each).

Remove the 'Navigation Workflow' section or fold its reading order into 'How to Use' \u2014 both sections enumerate the same six reference files, so one navigation guide suffices.

Drop the generic 'Each reference file contains:' bullet list; the named links plus the per-file titles already convey what each file covers.

DimensionReasoningScore

Conciseness

The body avoids basic-concept padding (dense 'Mindset' guidance, executable snippets), but the same rules are restated across sections: the typed-options-object rule appears in 'Mindset', 'Do\u2019s', 'Don\u2019ts', the 'Recommended' pattern, and 'Anti-Patterns'; the option-scope and parseAsync rules each appear three times; and 'Navigation Workflow' re-enumerates the same six reference files already listed under 'How to Use'. It could be meaningfully tightened by merging Do's/Don'ts into Anti-Patterns, which fits anchor 3 ('could be tightened') better than anchor 4 ('minor instances that could be trimmed').

3 / 5

Actionability

Mostly executable guidance: 'Quick Start' and 'Common Patterns' provide copy-paste TypeScript (including a full modular multi-file example), and Anti-Patterns pair BAD/GOOD code. Minor gaps keep it below anchor 5: some action bodies are skeletal ('/* ... */'), 'program' is used undefined in the index.ts snippet, and items like 'Validate options in action handlers' and 'Test CLI with different argument combinations' give no concrete code.

4 / 5

Workflow Clarity

The 'Navigation Workflow' is a clear 7-step sequence with an explicit validation checkpoint ('Test with --help and invalid inputs to verify argument parsing and error handling'), matching anchor 4. It falls short of anchor 5 because there is no error-recovery feedback loop (what to do when validation fails). The destructive/batch cap does not apply since this is not a destructive or batch-operation skill.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references: all six links (references/core-basics.md, options-flags.md, commands-structure.md, actions-handlers.md, typescript-setup.md, practices-patterns.md) exist, contain no nested references, and are internally well-organized by headers. Content is appropriately split with deep API detail in the bundle files and overview patterns in SKILL.md, matching anchor 5.

5 / 5

Total

16

/

20

Passed

Description

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

A strong description that explicitly states both capabilities and 'Use when' triggers with comprehensive, synonym-rich keywords including migration-source frameworks. Only minor issues: capabilities are listed as topics rather than actions, and the broad 'building CLI tools' trigger plus yargs/meow keywords create slight conflict risk with general or competitor-framework CLI skills.

DimensionReasoningScore

Specificity

'Complete Commander.js CLI framework guidance covering command structure, options, arguments, subcommands, action handlers, version management, and TypeScript integration' lists seven specific capability areas \u2014 comprehensive for the domain, but phrased as topics under 'guidance covering' rather than concrete actions (compare anchor 5's verb-led 'Extract\u2026 fill\u2026 merge'). Anchor 4 ('lists several specific actions; minor gaps in coverage') is the best fit.

4 / 5

Completeness

Explicitly answers both: what \u2014 'Complete Commander.js CLI framework covering command structure, options, arguments, subcommands, action handlers, version management, and TypeScript integration' \u2014 and when \u2014 'Use when: building CLI tools, parsing command-line arguments, implementing subcommands, handling options/flags, creating interactive CLIs, or migrating from other CLI frameworks.' This matches anchor 5: both what and when with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Keywords: Commander.js, CLI, command-line, arguments, options, flags, subcommands, action handlers, version, help text, TypeScript, yargs, meow, program, parseAsync, opts, args, variadic, required options, default values, custom help, error handling' covers natural terms comprehensively with synonyms (arguments/args, CLI/command-line) and even competing framework names users would mention, matching anchor 5's 'comprehensive coverage of natural terms including synonyms'.

5 / 5

Distinctiveness Conflict Risk

The Commander.js framing creates a clear niche with distinct triggers, but the trigger 'building CLI tools' and keywords 'yargs, meow' could pull this skill for non-Commander.js CLI work \u2014 minor overlap risk with closely related skills (anchor 4) rather than anchor 5's minimal-conflict profile.

4 / 5

Total

18

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

pantheon-org/tekhne

Path

skills/development/commanderjs/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.