Build and improve Python command interfaces for GUI applications with OpenClaw. The skill guides source analysis, command design, testing, and packaging, including interactive sessions and structured JSON output for agents.
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.
Review the instructions the agent will receive before you install.
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:
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use Reasonix to build or improve a Python command-line interface for existing software. The workflow covers source analysis, interactive commands, JSON output, tests, documentation, and installation checks using the software’s own backend where possible.
Use Codex to build Python command-line tools for applications with graphical interfaces. Analyze source code, add commands, test against the actual software, validate packaging and documentation, and discover tools already generated or installed.
Inspect and edit 3MF files for 3D printing. Detect cylindrical holes, change their diameters, repair mesh issues, and compare files while preserving BambuStudio and PrusaSlicer metadata when repacking the edited file.
Manage AdGuard Home network filtering from the command line. Update blocklists, register devices, configure DNS rules that map names to addresses, and inspect query logs and statistics through the AdGuard Home REST API.
Generate slides, documents, websites, and diagrams from natural language prompts through AnyGen OpenAPI. Manage reference uploads, check generation progress, and download finished files using commands with structured output for AI agents.
Build and edit audio projects through an Audacity command-line interface: arrange and trim clips, adjust tracks, configure effects, add labels, and render audio files while retaining project state and undo history.