Agent skill

CLI UX Tester

by jeremylongshore in jeremylongshore/tons-of-skills-marketplace

Expert UX evaluator for CLIs, terminal tools, and developer APIs.

Install CLI UX Tester

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill cli-ux-tester -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace cli-ux-tester --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/testing/cli-ux-tester/skills/cli-ux-tester .claude/skills/cli-ux-tester && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "cli-ux-tester" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/testing/cli-ux-tester/skills/cli-ux-tester into .claude/skills/cli-ux-tester/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-ux-tester", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/testing/cli-ux-tester/skills/cli-ux-tester

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill cli-ux-tester -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace cli-ux-tester --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/testing/cli-ux-tester/skills/cli-ux-tester .agents/skills/cli-ux-tester && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "cli-ux-tester" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/testing/cli-ux-tester/skills/cli-ux-tester into .agents/skills/cli-ux-tester/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-ux-tester", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill cli-ux-tester -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace cli-ux-tester --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/testing/cli-ux-tester/skills/cli-ux-tester .cursor/skills/cli-ux-tester && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "cli-ux-tester" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/testing/cli-ux-tester/skills/cli-ux-tester into .cursor/skills/cli-ux-tester/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-ux-tester", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path plugins/testing/cli-ux-tester/skills/cli-ux-tester

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill cli-ux-tester -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace cli-ux-tester --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/testing/cli-ux-tester/skills/cli-ux-tester .gemini/skills/cli-ux-tester && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "cli-ux-tester" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/testing/cli-ux-tester/skills/cli-ux-tester into .gemini/skills/cli-ux-tester/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-ux-tester", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace cli-ux-tester

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill cli-ux-tester -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/testing/cli-ux-tester/skills/cli-ux-tester .github/skills/cli-ux-tester && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "cli-ux-tester" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/testing/cli-ux-tester/skills/cli-ux-tester into .github/skills/cli-ux-tester/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-ux-tester", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill cli-ux-tester -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install jeremylongshore/tons-of-skills-marketplace cli-ux-tester --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/testing/cli-ux-tester/skills/cli-ux-tester .opencode/skills/cli-ux-tester && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "cli-ux-tester" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/plugins/testing/cli-ux-tester/skills/cli-ux-tester into .opencode/skills/cli-ux-tester/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cli-ux-tester", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: cli-ux-tester
GitHub stars: 2.8k
Token cost: ~1.3k tokens
SKILL.md length: 389 words
Files: 4 (incl. scripts)
Skills in repo: 3,342
Repo updated: Oct 10, 2026
First seen: Oct 8, 2026
Licence: MIT

At a glance

Expert UX evaluator for CLIs, terminal tools, and developer APIs.

Works in 5 steps: Detect target CLI → Ask clarifying questions if needed → Run evaluation agents in parallel → …
Reviewing command usability
SKILL.md covers Step 1: Detect target CLI, Step 2: Ask clarifying…, Step 3: Run evaluation agents… and Step 4: Launch synthesizer agent, plus 2 more sections
Runs Shell scripts from its folder

What it does

CLI UX Tester is an agent skill from jeremylongshore/tons-of-skills-marketplace. Expert UX evaluator for CLIs, terminal tools, and developer APIs. Use when reviewing command usability, error messages, help systems, or developer experience.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `scripts/example-test.sh`, `test-scenarios.md` and `testing-checklist.md`).

It sits in Frontend & Design, covering UX design. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

Reviewing command usability
Developer experience

Example prompts

“/cli-ux-tester”

Requirements

Python 3
Node.js
A Bash shell
Pre-approved tools (allowed-tools): Read, Bash, AskUserQuestion, Agent

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Detect target CLI
Ask clarifying questions if needed
Run evaluation agents in parallel
Launch synthesizer agent
Report results

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- Read
- Bash
- AskUserQuestion
- Agent
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 1 file in scripts/ (Shell), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

CLI UX Tester loads about 1.3k tokens when it runs. Until then it costs about 43 tokens; SKILL.md has 389 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~43
When it runs · the whole SKILL.md, loaded when a task matches: ~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
```
allowed-tools: Read, Bash, AskUserQuestion, Agent
```

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 389 words, ~1,306 tokens.

Download SKILL.mdSave it as .claude/skills/cli-ux-tester/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: cli-ux-tester
description: Expert UX evaluator for CLIs, terminal tools, and developer APIs. Use when reviewing command usability, error messages, help systems, or developer experience.
allowed-tools: Read, Bash, AskUserQuestion, Agent
version: 3.0.0

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:

bash

# Check for executable entry points
ls -la *.sh bin/ scripts/ 2>/dev/null | head -20

# Check for package.json with a bin field (Node.js CLI)
cat package.json 2>/dev/null | grep -A5 '"bin"'

# Check for Python CLI setup
cat setup.py pyproject.toml 2>/dev/null | grep -A5 'console_scripts\|entry_points' | head -20

# Check for Go main package
ls main.go cmd/ 2>/dev/null

# Check README for CLI name and usage
head -50 README.md 2>/dev/null

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:

text

Question: "Which CLI should I evaluate?"
Options:
  - [Each detected entry point]
  - A different installed command (provide the name)
  - A different path (provide the path)

No entry points detected → ask the user to specify:

text

Question: "Which CLI tool should I evaluate?"
Options:
  - An installed command available in $PATH (provide the name)
  - A path to an executable (provide the path)

Proceed directly to Step 3 with whatever the user provides.

Show full SKILL.md (189 more words)Show less

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 {cli_command} and {working_dir}:

Explore agent — codebase mapping:

text

subagent_type: Explore
prompt: "Map the {cli_command} CLI codebase in {working_dir}. Find: all commands and subcommands,
help text locations, error handling code, version output, README and docs files, entry point(s),
flag/argument parsing. Return a structured summary: command tree, key file locations, patterns
observed."

Test agent A — discovery and help:

text

subagent_type: general-purpose
prompt: "Test {cli_command}'s help system and discoverability (run from {working_dir}).
Run: {cli_command} --help, {cli_command} -h, {cli_command} help, {cli_command} (no args),
{cli_command} --version, {cli_command} -v, {cli_command} version, {cli_command} invalid-subcommand,
{cli_command} --invalid-flag. For each subcommand found, also run: {cli_command} subcommand --help.
Capture exact output. Note: what works, what fails, what's missing."

Test agent B — error handling and consistency:

text

subagent_type: general-purpose
prompt: "Test {cli_command}'s error handling and consistency (run from {working_dir}).
Run: commands with missing required args, invalid flag values, nonexistent files, wrong syntax.
Check whether flag names are consistent across subcommands (--verbose always means the same thing).
Check exit codes with echo $?. Capture exact outputs. Note every inconsistency."

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.

Pass:

The working directory
The CLI entry point (command name, script path, or executable)
Any relevant context from the user's message (e.g., "focus on error messages")
The full output from all three evaluation agents (Explore, Test A, Test B)
Path to testing-checklist.md
Path to test-scenarios.md

Step 5: Report results

When the agent completes, inform the user:

text

✅ Evaluation complete!
📁 Results saved to: {timestamped_directory}
📊 Overall score: {overall_score}/5
🔍 Top issues: {brief_summary}

Clean up with: rm -rf CLI_UX_EVALUATION_*/

Error handling

CLI not found: Ask the user to confirm the command name or path
Permission denied: Note the issue and ask if they want to test a different entry point
No CLI in current directory: Ask the user to specify which tool to evaluate

Files

SKILL.md and 3 other files (scripts) in plugins/testing/cli-ux-tester/skills/cli-ux-tester of jeremylongshore/tons-of-skills-marketplace.

SKILL.md
scripts/example-test.sh
test-scenarios.md
testing-checklist.md

Open the folder on GitHubat commit cfae287

Compare with similar skills

CLI UX Tester next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

CLI UX Tester compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
CLI UX Tester this skilljeremylongshore/tons-of-skills-marketplace	2.8k	—	~1.3k	Automated safety check: Notes	MIT	yesterday
Product Design Workflow BundleXiaomiMiMo/MiMo-Code	14k	—	~721	Automated safety check: Pass	MIT	2 days ago
Archestra Docs Writerarchestra-ai/archestra	4.4k	—	~5.3k	Automated safety check: Pass	Custom licence	today
Chief Architectananddtyagi/cc-marketplace	687	—	~8.4k	Automated safety check: Pass	None	8 mo ago
Impeccablebestofjs/bestofjs	3.1k	26 repos	~2.6k	Automated safety check: Pass	MIT	6 days ago
Interface Design for Dashboards and Appsholaboss-ai/holaOS	11k	3 repos	~6k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

Product Design Workflow Bundle
XiaomiMiMo/MiMo-Code
Entry point to a bundle of product design workflows covering context, research, audits, ideation, URL or image to code, design QA and sharing a prototype.
14k GitHub stars~721 tokensUpdated 2 days ago
Frontend & DesignAuto-check passed
Archestra Docs Writer
archestra-ai/archestra
A skill your agent uses when writing, editing, restructuring, or auditing Archestra documentation under docs/pages/ — new feature docs, page rewrites, sidebar and information-architecture changes…
4.4k GitHub stars~5.3k tokensUpdated today
Frontend & DesignAuto-check passed
Chief Architect
ananddtyagi/cc-marketplace
PERSONAL APP ARCHITECT - Strategic development orchestrator for personal productivity applications.
687 GitHub stars~8.4k tokensUpdated 8 mo ago
Frontend & DesignAuto-check passed
Impeccable
bestofjs/bestofjs
A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…
3.1k GitHub starsUsed in 26 repos~2.6k tokens
Frontend & DesignAuto-check passed
Interface Design for Dashboards and Apps
holaboss-ai/holaOS
Pushes an agent past generic defaults when designing dashboards, admin panels, SaaS apps and tools, with attention to structure, type, navigation and how data is shown.
11k GitHub starsUsed in 3 repos~6k tokens
Frontend & DesignAuto-check passed
Animate
growupanand/ConvoForm
Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.
102 GitHub starsUsed in 6 repos~1.9k tokens
Frontend & DesignAuto-check passed

Questions about CLI UX Tester

What does CLI UX Tester do?

Expert UX evaluator for CLIs, terminal tools, and developer APIs. CLI UX Tester is an agent skill from jeremylongshore/tons-of-skills-marketplace. Expert UX evaluator for CLIs, terminal tools, and developer APIs.

When should I use CLI UX Tester?

CLI UX Tester fits situations like: reviewing command usability; developer experience.

How do I install CLI UX Tester in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill cli-ux-tester -a claude-code`. Or copy the skill folder (plugins/testing/cli-ux-tester/skills/cli-ux-tester in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/cli-ux-tester in your project. Claude Code loads it when a task matches its description.

How do I install CLI UX Tester in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill cli-ux-tester -a codex`. Or copy the skill folder (plugins/testing/cli-ux-tester/skills/cli-ux-tester in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/cli-ux-tester in your project. Codex loads it when a task matches its description.

Can I use CLI UX Tester in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill cli-ux-tester -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cli-ux-tester, .gemini/skills/cli-ux-tester, .github/skills/cli-ux-tester and .opencode/skills/cli-ux-tester in your project.

What does CLI UX Tester need to run?

Going by SKILL.md and its folder, CLI UX Tester needs a shell for the scripts in its folder. Our summary lists: Python 3; Node.js; A Bash shell. Its frontmatter pre-approves these tools: Read, Bash, AskUserQuestion, Agent.

Does CLI UX Tester access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is CLI UX Tester safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does CLI UX Tester use?

CLI UX Tester is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does CLI UX Tester use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to CLI UX Tester?

Skills that share tags, products or a category with CLI UX Tester: Product Design Workflow Bundle (XiaomiMiMo/MiMo-Code, 14k stars), Archestra Docs Writer (archestra-ai/archestra, 4.4k stars), Chief Architect (ananddtyagi/cc-marketplace, 687 stars) and Impeccable (bestofjs/bestofjs, 3.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains CLI UX Tester?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install CLI UX Tester

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

CLI UX Tester

Step 1: Detect target CLI

Step 2: Ask clarifying questions if needed

Step 3: Run evaluation agents in parallel

Step 4: Launch synthesizer agent

Step 5: Report results

Error handling

Files

Compare with similar skills

Similar skills

More from jeremylongshore/tons-of-skills-marketplace

Related

Questions about CLI UX Tester