CLI UX Skill

When to Activate

Writing error messages for a CLI tool
Designing --help output or man pages
Adding config file support or env-var overrides
Implementing autocomplete for shell (bash/zsh/fish)
Adding spinners or progress bars
Reviewing the UX of an existing CLI tool
Designing the initial UX for a new CLI tool where flag naming, config hierarchy, and output format decisions have long-term consequences
Auditing a CLI that developers find hard to use or frequently get wrong — focusing on error message quality and help text clarity
Adding --json and --quiet output modes so a CLI can be scripted and piped without breaking human-readable output

Good error messages tell users what went wrong and what to do next.