adding-a-command

Creates a new CLI command following the Commander.js pattern in src/commands/. Handles command registration in src/cli.ts, telemetry tracking via tracked() wrapper, and option parsing. Use when user says add command, new CLI command, create subcommand, or adds files to src/commands/. Do NOT use for modifying existing commands or fixing bugs in existing commands.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-3

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

The body is highly actionable with executable examples and a well-sequenced, verified workflow, but it is held back by cross-section redundancy and a fully inline structure with no progressive disclosure to reference files. It is a solid, practical skill that would benefit from de-duplication and splitting some detail out.

Suggestions

De-duplicate the rules restated across Critical, Instructions, and Common Issues — state each invariant once in Critical and have Common Issues link back rather than re-explaining the named-export, tracked(), and __exit__ patterns.

Move the three worked Examples and/or the Common Issues catalog into a reference file (e.g. references/examples.md) and link to it from SKILL.md, keeping the main body as a concise overview so progressive disclosure reaches one level deep.

Tighten Instruction steps 1–4 by removing the trailing 'Verify...' micro-checks that duplicate step 5's consolidated verification checklist.

Dimension	Reasoning	Score
Conciseness	The body is codebase-specific (not padded with general concepts Claude knows), but the same rules are restated across the Critical, Instructions, and Common Issues sections — e.g. the named-export rule, the tracked() wrapper, and the __exit__ pattern each appear three times — so it could be tightened.	2 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript snippets for three scenarios (status, sources add, init parser) with exact file paths, import statements, signatures, and registration chains, matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	A clear 5-step sequence culminates in an explicit 'Verify before proceeding' checklist, and the Common Issues section supplies cause→fix error-recovery guidance, satisfying the 'clear sequence with explicit validation steps and error recovery' anchor.	3 / 3
Progressive Disclosure	Content is well-organized into clear sections, but at ~180 lines everything is inline with no external references — the detailed examples and Common Issues catalog could be split into reference files rather than carried entirely in SKILL.md, leaving it short of the one-level-deep reference structure of a 3.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 concise, third-person, and covers concrete capabilities, natural trigger terms, both 'what' and 'when', and clear exclusions that bound its scope. It is a strong, low-conflict description with no significant weaknesses.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions tied to specific artifacts — 'Creates a new CLI command following the Commander.js pattern in src/commands/', 'Handles command registration in src/cli.ts', 'telemetry tracking via tracked() wrapper', and 'option parsing' — matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what it does and when to use it via a clear 'Use when...' clause, and adds a 'Do NOT use for...' exclusion — clearly above the level 2 anchor where 'when' is only implied.	3 / 3
Trigger Term Quality	Captures natural phrases a user would say ('add command', 'new CLI command', 'create subcommand') plus a path-based trigger ('adds files to src/commands/'), giving good coverage of common variations rather than jargon.	3 / 3
Distinctiveness Conflict Risk	Scoped to a specific Commander.js codebase with distinct path-based triggers and an explicit negative trigger excluding modifying/fixing existing commands, making conflicts with other skills unlikely.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: caliber-ai-org/ai-setup
Path: .claude/skills/adding-a-command/SKILL.md
Commit: 7950921

Reviewed: 13 days 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.