cli-ux-audit

Audit CLI help, commands, errors, and accessibility with reproducible scored reports.

3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/anthril/official-claude-plugins --skill cli-ux-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cli-ux-audit
Source: https://github.com/anthril/official-claude-plugins/tree/main/plugins/package-manager/skills/cli-ux-audit
Command: npx skills add https://github.com/anthril/official-claude-plugins --skill cli-ux-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

CLI UX inconsistencies slow adoption and degrade developer experience across tooling.

Core Features & Use Cases

  • Structured audits of top-level help, subcommands, error messages, and interactive prompts.
  • Reproducible phase-scored reports with actionable fixes for PRs and documentation.
  • Extensible probes via scripts/references/assets to tailor checks for different toolchains.

Quick Start

Run the included probe suite against a target CLI to generate a Phase 2–4 findings report.

Frequently Asked Questions about cli-ux-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit CLI UX quality for developer tooling?

To audit CLI UX quality, run a standardized probe suite against your target CLI to discover help, commands, errors, and accessibility issues. This generates a phase-scored findings report with actionable fixes for your PRs and documentation.

Can I audit CLI error messages and interactive prompts across different languages?

Yes, you can audit CLI error messages and interactive prompts across different languages. The probe suite applies to any CLI by running standardized discovery and invocation phases, ensuring consistent developer tooling regardless of the toolchain.

What is a reproducible phase-scored report for CLI audits?

A reproducible phase-scored report for CLI audits is an actionable document generated by running discovery, invocation, and scoring phases against a target CLI. It details top-level help, subcommands, errors, and prompts with specific fixes.

How do I customize CLI UX audit checks for my specific toolchain?

You can customize CLI UX audit checks by extending the probes via the scripts, references, and assets directories. This allows you to tailor the standardized discovery and invocation phases to fit your specific toolchain requirements.

Do I need a specific configuration file to run a CLI UX audit?

Yes, you need a YAML frontmatter in the SKILL.md file containing the name and description to run the CLI UX audit. Optional scripts, references, and assets directories are supported to further extend probes and references.

What's the best way to improve CLI adoption and developer experience?

The best way to improve CLI adoption is to resolve UX inconsistencies by running structured audits of top-level help, subcommands, and error messages. This produces reproducible, actionable reports that highlight fixes for PRs and documentation.