# CLI Anything for OpenClaw

Builds, tests, and validates CLI-Anything harnesses for OpenClaw.

- Repository: https://github.com/HKUDS/CLI-Anything (58029 stars)
- Category: Engineering
- License: Apache-2.0
- Last updated: 2026-09-22
- Runs scripts: yes, review before use

## Install

Claude Code: `npx skills add HKUDS/CLI-Anything --skill cli-anything -g -a claude-code -y`
Codex: `npx skills add HKUDS/CLI-Anything --skill cli-anything -g -a codex -y`
Cursor: `npx skills add HKUDS/CLI-Anything --skill cli-anything -g -a cursor -y`
Gemini CLI: `npx skills add HKUDS/CLI-Anything --skill cli-anything -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add HKUDS/CLI-Anything`

## Description

Use when the user wants OpenClaw to build, refine, test, or validate a CLI-Anything harness for a GUI application or source repository. Adapts the CLI-Anything methodology to OpenClaw without changing the generated Python harness format.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# CLI-Anything for OpenClaw

Use this skill when the user wants OpenClaw to act like the `CLI-Anything` builder.

If this skill is being used from inside the `CLI-Anything` repository, read `../cli-anything-plugin/HARNESS.md` before implementation. That file is the full methodology source of truth. If it is not available, follow the condensed rules below.

## Inputs

Accept either:

- A local source path such as `./gimp` or `/path/to/software`
- A GitHub repository URL

Derive the software name from the local directory name after cloning if needed.

## Modes

### Build

Use when the user wants a new harness.

Produce this structure:

```text
<software>/
└── agent-harness/
    ├── <SOFTWARE>.md
    ├── setup.py
    └── cli_anything/
        └── <software>/
            ├── README.md
            ├── __init__.py
            ├── __main__.py
            ├── <software>_cli.py
            ├── core/
            ├── utils/
            └── tests/
```

Implement a stateful Click CLI with:

- one-shot subcommands
- REPL mode as the default when no subcommand is given
- `--json` machine-readable output
- session state with undo/redo where the target software supports it

### Refine

Use when the harness already exists.

First inventory current commands and tests, then do gap analysis against the target software. Prefer:

- high-impact missing features
- easy wrappers around existing backend APIs or CLIs
- additions that compose well with existing commands

Do not remove existing commands unless the user explicitly asks for a breaking change.

### Test

Plan tests before writing them. Keep both:

- `test_core.py` for unit coverage
- `test_full_e2e.py` for workflow and backend validation

When possible, test the installed command via subprocess using `cli-anything-<software>` rather than only module imports.

### Validate

Check that the harness:

The rest: https://github.com/HKUDS/CLI-Anything/blob/HEAD/macrocli/SKILL.md