Agent skill · software engineering · hkuds
cli-anything
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.
Why this skill is useful
Provides a structured methodology for building and validating CLI harnesses specific to OpenClaw, which the AI wouldn't reliably generate on its own.
What it needs
Requires click installed locally. About 2k tokens when loaded. Last updated 2026-08-03. 46,739 stars on the source repository.
What this skill does
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: 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: testcore.py for unit coverage testfulle2e.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: uses the clianything.<software> namespace package layout has an installable setup.py entry point supports JSON output has a REPL default path documents usage and tests Backend Rules Prefer 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills hkuds/macrocli