CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

74

Quality

93%

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

The canonical home for this skill is adding-a-command in caliber-ai-org/ai-setup

SKILL.md
Quality
Evals
Security

Quality

Content

82%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, actionable body with copy-paste examples and a sensible workflow, held back only by minor redundancy and validation that is a checklist rather than an executable feedback loop.

Suggestions

Consolidate the repeated 'Verify…' bullets and the Critical section so each invariant appears once; reference Critical from step 5 instead of restating it.

Turn step 5's verify checklist into an executable validation step (e.g., a tsc --noEmit or a grep confirming the tracked() wrapper) with an explicit 'if it fails, return to step N' loop.

Consider moving the three full Examples into a references/ file and keeping only the minimal pattern inline, reducing the SKILL.md body length.

DimensionReasoningScore

Conciseness

Assumes Claude's competence throughout (no boilerplate about what Commander.js or telemetry is), but the 'Verify…' sub-bullets and step-5 checklist overlap with the Critical section, leaving minor redundancy.

4 / 5

Actionability

Three copy-paste-ready TypeScript examples (simple command, subcommand with args, custom option parser) with exact import paths and registration snippets cover the common cases fully.

5 / 5

Workflow Clarity

A clear 5-step sequence with a verification checklist, but the main flow lacks an explicit validate→fix→retry loop; error recovery is deferred to the Common Issues section rather than inline checkpoints.

4 / 5

Progressive Disclosure

Well-organized into Critical/Instructions/Examples/Common Issues with no nested references, though at ~180 lines the three full code examples could plausibly live in a bundled references file.

4 / 5

Total

17

/

20

Passed

Description

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

An excellent description: third-person, concrete, with explicit triggers and negative scope that sharply bound when it fires. Every dimension lands at the top anchor.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — creating the command file, registration in src/cli.ts, telemetry via tracked(), and option parsing — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what (creates/registers/tracks/parses) and when (concrete trigger phrases), plus a 'Do NOT use for…' clause giving negative scope.

5 / 5

Trigger Term Quality

'Use when user says add command, new CLI command, create subcommand, or adds files to src/commands/' provides comprehensive natural synonyms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

A clear niche (adding commands in this repo's Commander.js pattern) with explicit exclusion of modifying/fixing existing commands yields minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

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