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
Node.js CLI error handling and UX
Commander framework
100%
100%
Chalk for output
0%
100%
Ora for spinners
0%
100%
TTY color detection
50%
100%
SIGINT handler
100%
100%
POSIX exit codes
33%
66%
Actionable error messages
100%
100%
ESM package type
0%
100%
Node engine constraint
0%
100%
Bin field
100%
100%
Stderr for errors
100%
100%
UX decisions explained
100%
100%
Python CLI interactive and non-interactive modes
Typer framework
0%
100%
Rich for output
0%
100%
questionary for prompts
0%
100%
CI detection
100%
100%
Config priority order
55%
100%
Env var config override
100%
100%
SIGINT handling
88%
100%
requires-python >= 3.10
100%
100%
Correct dependencies
0%
100%
Input validation
75%
100%
Proper exit codes
33%
55%
Stderr for errors
87%
100%
Go CLI configuration and progress indicators
Cobra framework
100%
100%
Viper for configuration
100%
100%
Viper env prefix
100%
100%
Multi-path config
100%
62%
Determinate progress bar
22%
100%
Indeterminate spinner
100%
100%
No stack traces to users
87%
87%
SIGINT graceful exit
0%
100%
POSIX exit codes
0%
0%
Cross-platform build
100%
100%
Stderr for diagnostics
75%
100%
UX decisions documented
100%
100%
Shell completions and help text structure
Shell completions included
100%
100%
Completions for multiple shells
100%
100%
USAGE section in help
100%
100%
OPTIONS with short+long forms
100%
100%
EXAMPLES in help
100%
100%
Kebab-case flags
100%
100%
No broken existing signatures
100%
100%
--version flag works
100%
100%
UX decisions explained
100%
100%
Output template: 5 elements
80%
100%
Errors to stderr
100%
100%
Startup performance and cross-platform path handling
No hardcoded home paths
100%
100%
Platform home API used
100%
100%
Lazy loading of commands
0%
0%
Async file I/O
0%
0%
Startup performance noted
100%
100%
Update check non-blocking
0%
100%
Config stored in home dir
100%
100%
Errors to stderr
100%
100%
ESM module type
0%
100%
Engine constraint
100%
100%
Input validation
100%
100%
Color accessibility, NO_COLOR support, and error message patterns
NO_COLOR env var respected
0%
100%
TTY detection for color
100%
100%
Semantic color: errors red
100%
100%
Semantic color: success green
100%
100%
Symbols alongside colors
0%
100%
Error message: context shown
100%
100%
Error message: solution provided
100%
100%
Stack traces hidden by default
100%
100%
Verbose or debug mode present
0%
0%
Errors to stderr
100%
100%
SIGINT handled
0%
100%
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.