adding-cli-command

Provides Typer templates, handles registration, and ensures consistency. ALWAYS use this skill when adding or modifying CLI commands. Use when user requests to add/create/implement/build/write a new command (e.g., "add edit command", "create search feature") OR update/modify/change/edit an existing command.

Quality

93%

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

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

A concise, highly actionable skill body with executable templates and clear conventions, weakened only by a workflow that omits an explicit verification step despite covering destructive commands.

Suggestions

Add a final workflow step to verify the command works, e.g. run `<cli_app> <command> --help` and confirm it appears in the registered command list.

For destructive commands, include a checkpoint to test the --force path and confirmation flow before considering the task complete.

Consider a brief note on how to verify registration in commands/__init__.py so a missed add_typer call is caught early.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what Typer or a CLI is, and every section (templates, registration, conventions) earns its tokens.	3 / 3
Actionability	Three fully executable Typer templates plus complete registration code are copy-paste ready; the only placeholder (<cli_app>) is explicitly justified upfront.	3 / 3
Workflow Clarity	The four-step workflow is clearly sequenced, but it lacks any validation/verification checkpoint (e.g., run the CLI to confirm registration works), which the rubric caps at 2 for skills involving destructive commands.	2 / 3
Progressive Disclosure	A single self-contained file organized into well-labeled sections (Workflow, Templates A/B/C, Registration, Conventions) with no nested references and easy header-based navigation.	3 / 3
	Total	11 / 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.

A strong, third-person description that clearly states concrete capabilities and provides explicit, well-covered usage triggers. It distinguishes itself via the Typer/CLI niche and avoids vague fluff.

Dimension	Reasoning	Score
Specificity	"Provides Typer templates, handles registration, and ensures consistency" lists multiple specific concrete actions rather than vague language.	3 / 3
Completeness	Explicitly states both what it does (templates, registration, consistency) and when to use it via an "ALWAYS use this skill... Use when..." trigger clause.	3 / 3
Trigger Term Quality	Covers natural user phrasings broadly ("add/create/implement/build/write", "update/modify/change/edit") with example utterances like "add edit command" and "create search feature".	3 / 3
Distinctiveness Conflict Risk	Scoped to Typer CLI commands with distinct add/modify triggers, making it unlikely to fire for unrelated skills.	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: https-deeplearning-ai/sc-agent-skills-files
Path: L6/.claude/skills/adding-cli-command/SKILL.md
Commit: 438a5a5

Reviewed: 12 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.