Individual skill

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.

plugins/testing/cli-ux-tester/skills/cli-ux-tester/SKILL.md

Read pinned source

Source commit 0500b275e963c027f6b410e8c49c0446945c574e

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 12, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
2,917
Repository last updated
Nov 12, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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.
Back to top