Agent skill · writing content · jeremylongshore
cli-ux-tester
Expert UX evaluator for CLIs, terminal tools, and developer APIs. Use when reviewing command usability, error messages, help systems, or developer experience.
Why this skill is useful
Adds a structured evaluation process for CLI usability, including parallel agent execution and specific testing prompts that enhance the AI's ability to assess command-line tools.
What it needs
Requires bash installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
CLI UX Tester This skill evaluates the usability of command-line interfaces and developer tools. It identifies the target CLI, asks clarifying questions if needed, runs three evaluation agents in parallel, then passes the collected results to a synthesizer agent to produce artifacts. Architecture: The skill spawns all evaluation sub-agents directly (one Explore agent and two test agents in parallel). This works around the platform constraint that sub-agents cannot spawn further sub-agents. The cli-ux-tester:cli-ux-tester agent acts as a pure synthesizer — it receives the pre-collected test data and produces the scored report and artifacts. Step 1: Detect target CLI Try to identify the CLI to evaluate from the user's message and current directory context. From the user's message: If the user names a specific command or tool (e.g., "review my-tool"), use that as the target. From the current directory: Step 2: Ask clarifying questions if needed Skip this step if the target CLI was already identified from the user's message in Step 1. Otherwise, ask exactly one AskUserQuestion using the appropriate form below: Entry point(s) detected in current directory → ask which to evaluate: No entry points detected → ask the user to specify: Proceed directly to Step 3 with whatever the user provides. Step 3: Run evaluation agents in parallel Locate the reference files first: Use Glob (/testing-checklist.md) to find testing-checklist.md; note the path Use Glob (/test-scenarios.md) to find test-scenarios.md; note the path Then spawn these three agents simultaneously, substituting the actual {clicommand} and {workingdir}: Explore agent — codebase mapping: Test agent A — discovery and help: Test agent B — error handling and consistency: Wait for all three agents to complete and collect their full outputs before proceeding. Step 4: Launch synthesizer agent Once all evaluation results are collected, launch the cli-ux-tester:cli-ux-tester agent. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/cli-ux-tester