/cli-anything-validate
Validate a CLI-Anything harness against the full HARNESS checklist
> /plugin marketplace add HKUDS/CLI-Anything > /plugin install cli-anything@cli-anything
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/cli-anything-validate
Context preview
What this command does when you run it.
Validate a CLI-Anything harness against the full HARNESS checklist
Command definition
cli-anything-validate.mdname: cli-anything-validate
description: Validate a CLI-Anything harness against the full HARNESS checklist
cli-anything-validate Command
Validate an existing harness against directory, implementation, test, docs, packaging, and code-quality requirements.
**Target software**: local path argument (required).
CRITICAL: Resolve PLUGIN_ROOT (absolute paths only)
1. Read `~/.cursor/cli-anything-generator.root` / `%USERPROFILE%\.cursor\cli-anything-generator.root` 2. Else install dir `PLUGIN_ROOT.txt` / default `.../plugins/local/cli-anything` 3. Read `{PLUGIN_ROOT}/references/HARNESS.md` and `{PLUGIN_ROOT}/references/commands/validate.md` via absolute paths
Cursor Tool Bindings
| Cursor tool | Role | |-------------|------| | Glob / Grep / Read | Checklist inventory of harness layout and APIs | | Shell | Optional smoke tests, import checks, `pip show` / entry-point checks | | Write | Only to record validation report if the user asks for a file |
Phase Gates and Resume (hard gate)
Progress: `{software-root}/agent-harness/.cli-anything-progress.json` with `"mode": "validate"`.
- Walk checklist sections; mark each section completed before moving on.
- Resume incomplete validation; finish with a clear pass/fail summary and concrete gaps.
Validate checklist (summary)
- Directory layout under `agent-harness/cli_anything/<software>/`
- Implementation: Click + REPL + `--json` + session patterns per HARNESS
- Tests: unit + E2E + installed CLI
- Docs: README, SOFTWARE.md, TEST.md, skills
- Packaging: namespace packages + console_scripts
What This Command Does
Follow `{PLUGIN_ROOT}/references/commands/validate.md`. Do not silently lower the quality bar.
Read more
name: cli-anything-validate description: Validate a CLI-Anything harness against the full HARNESS checklist
cli-anything-validate Command
Validate an existing harness against directory, implementation, test, docs, packaging, and code-quality requirements.
**Target software**: local path argument (required).
CRITICAL: Resolve PLUGIN_ROOT (absolute paths only)
1. Read `~/.cursor/cli-anything-generator.root` / `%USERPROFILE%\.cursor\cli-anything-generator.root` 2. Else install dir `PLUGIN_ROOT.txt` / default `.../plugins/local/cli-anything` 3. Read `{PLUGIN_ROOT}/references/HARNESS.md` and `{PLUGIN_ROOT}/references/commands/validate.md` via absolute paths
Cursor Tool Bindings
| Cursor tool | Role | |-------------|------| | Glob / Grep / Read | Checklist inventory of harness layout and APIs | | Shell | Optional smoke tests, import checks, `pip show` / entry-point checks | | Write | Only to record validation report if the user asks for a file |
Phase Gates and Resume (hard gate)
Progress: `{software-root}/agent-harness/.cli-anything-progress.json` with `"mode": "validate"`.
- Walk checklist sections; mark each section completed before moving on.
- Resume incomplete validation; finish with a clear pass/fail summary and concrete gaps.
Validate checklist (summary)
- Directory layout under `agent-harness/cli_anything/<software>/`
- Implementation: Click + REPL + `--json` + session patterns per HARNESS
- Tests: unit + E2E + installed CLI
- Docs: README, SOFTWARE.md, TEST.md, skills
- Packaging: namespace packages + console_scripts
What This Command Does
Follow `{PLUGIN_ROOT}/references/commands/validate.md`. Do not silently lower the quality bar.
"CLI-Anything: Making ALL Software Agent-Native" -- CLI-Hub: https://clianything.cc/
Repo: HKUDS/CLI-Anything
Other commands on cli-anything.
refine
Refine an existing CLI harness to improve coverage of the software's functions and usage patterns.

