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.
83%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
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.
Accept either:
./gimp or /path/to/softwareDerive the software name from the local directory name after cloning if needed.
Use when the user wants a new harness.
Produce this structure:
<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:
--json machine-readable outputUse when the harness already exists.
First inventory current commands and tests, then do gap analysis against the target software. Prefer:
Do not remove existing commands unless the user explicitly asks for a breaking change.
Plan tests before writing them. Keep both:
test_core.py for unit coveragetest_full_e2e.py for workflow and backend validationWhen possible, test the installed command via subprocess using cli-anything-<software> rather than only module imports.
Check that the harness:
cli_anything.<software> namespace package layoutsetup.py entry pointPrefer the real software backend over reimplementation. Wrap the actual executable or scripting interface in utils/<software>_backend.py when possible. Use synthetic reimplementation only when the project explicitly requires it or no viable native backend exists.
find_namespace_packages(include=["cli_anything.*"])cli_anything/ as a namespace package without a top-level __init__.pycli-anything-<software> through console_scriptsTEST.md, then tests, then run them.pip install -e .When reporting progress or final results, include:
HKUDS/CLI-Anything
34f5195
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.