cli-developer

Use when building CLI tools, implementing argument parsing, or adding interactive prompts. Invoke for parsing flags and subcommands, displaying progress bars and spinners, generating bash/zsh/fish completion scripts, CLI design, shell completions, and cross-platform terminal applications using commander, click, typer, or cobra.

Quality

88%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

This is a well-structured CLI development skill with strong actionability and clear workflow sequencing. The progressive disclosure design is thoughtful with the reference table, but the absence of bundle files means the referenced materials can't be verified. Minor conciseness issues exist with some redundant knowledge listings and constraints that state obvious best practices.

Suggestions

Remove the 'Knowledge Reference' keyword list at the bottom — it provides no actionable guidance and wastes tokens.

Trim MUST DO constraints that Claude already knows (e.g., 'Validate user input early', 'Provide clear, actionable error messages') to focus on CLI-specific non-obvious requirements.

Dimension	Reasoning	Score
Conciseness	Generally efficient but includes some unnecessary items: the 'Knowledge Reference' section at the bottom is just a keyword list that adds no actionable value, and some MUST DO items state things Claude already knows (e.g., 'Validate user input early'). The constraints section is somewhat verbose with inline code examples that could be more tightly organized.	2 / 3
Actionability	Provides a fully executable Node.js quick-start example, concrete TTY detection code snippets in three languages, specific performance targets (50ms startup), and clear command verification steps (run --help, --version). The guidance is specific and copy-paste ready.	3 / 3
Workflow Clarity	The 5-step core workflow is clearly sequenced with explicit validation checkpoints at each stage: verify help text renders, confirm version output, verify TTY detection, run cross-platform smoke tests. Each step includes what to validate before proceeding.	3 / 3
Progressive Disclosure	The reference table with 'Load When' guidance is well-structured and clearly signaled, but no bundle files were provided, meaning the referenced files (references/design-patterns.md, references/node-cli.md, etc.) cannot be verified to exist. The skill appropriately keeps the overview concise and points to detailed references, but the missing bundle undermines confidence in the navigation structure.	2 / 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.

This is a strong skill description that clearly defines its scope around CLI tool development with specific actions, explicit trigger guidance, and natural keywords. It names concrete libraries and covers multiple facets of CLI development (parsing, UI elements, completions, cross-platform support). The description is well-structured with both 'Use when' and 'Invoke for' clauses providing comprehensive guidance for skill selection.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'parsing flags and subcommands', 'displaying progress bars and spinners', 'generating bash/zsh/fish completion scripts', 'argument parsing', 'adding interactive prompts'. These are concrete, actionable capabilities.	3 / 3
Completeness	Explicitly answers both 'what' (parsing flags, displaying progress bars, generating completion scripts, cross-platform terminal applications) and 'when' with an explicit 'Use when building CLI tools, implementing argument parsing, or adding interactive prompts' clause.	3 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'CLI tools', 'argument parsing', 'interactive prompts', 'flags', 'subcommands', 'progress bars', 'spinners', 'bash/zsh/fish completion scripts', 'shell completions', 'terminal applications', plus specific library names like 'commander', 'click', 'typer', 'cobra'.	3 / 3
Distinctiveness Conflict Risk	Clearly carved out niche around CLI tooling with distinct triggers like 'CLI tools', 'argument parsing', 'shell completions', and specific framework names (commander, click, typer, cobra). Unlikely to conflict with general coding or other 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: Jeffallan/claude-skills
Commit: e8be415

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