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.
95
100%
Does it follow best practices?
Impact
91%
1.33xAverage score across 6 eval scenarios
Passed
No known issues
Quality
Discovery
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. It excels at providing specific actions, natural trigger terms including framework names, and explicit 'Use when' guidance. The description is well-structured and would allow Claude to confidently select this skill when users need help with command-line interfaces.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'parsing flags and subcommands', 'displaying progress bars and spinners', 'generating bash/zsh/fish completion scripts', and names specific frameworks (commander, click, typer, cobra). | 3 / 3 |
Completeness | Explicitly answers both what (parsing flags, displaying progress bars, generating completion scripts) and when ('Use when building CLI tools, implementing argument parsing, or adding interactive prompts'). The 'Use when...' clause is present at the start. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'CLI tools', 'argument parsing', 'interactive prompts', 'flags', 'subcommands', 'progress bars', 'spinners', 'shell completions', 'bash/zsh/fish', plus specific library names users might mention. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche focused on CLI/terminal tooling with distinct triggers like 'CLI', 'argument parsing', 'shell completions', and specific framework names. Unlikely to conflict with general coding or document skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%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-crafted skill that demonstrates excellent token efficiency while providing comprehensive, actionable guidance for CLI development. The workflow is clearly sequenced with validation steps, the reference table provides excellent progressive disclosure, and the constraints section gives specific do/don't guidance with executable code examples. The content appropriately assumes Claude's competence while adding genuine value through framework-specific patterns and cross-platform considerations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic concepts Claude already knows. Every section serves a purpose with no padding or unnecessary context about what CLIs are or how frameworks work. | 3 / 3 |
Actionability | Provides fully executable Node.js example code, concrete TTY detection snippets for three languages, specific timing targets (50ms), and clear verification steps. The code is copy-paste ready. | 3 / 3 |
Workflow Clarity | The 5-step core workflow is clearly sequenced with explicit validation checkpoints (verify help text, confirm version output, run smoke tests). Each step includes what to verify before proceeding. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, reference table pointing to one-level-deep topic files, and explicit guidance on when to load each reference. Quick-start is inline while detailed examples are appropriately delegated to reference files. | 3 / 3 |
Total | 12 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
5b76101
Table of Contents
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.