Agent skill · software engineering · hkuds
cli-anything
Use when the user wants Reasonix to build, refine, test, or validate a CLI-Anything harness for a GUI application or source repository. Adapts the CLI-Anything methodology to Reasonix without changing the generated Python harness format.
Why this skill is useful
Adds a complete CLI harness generation workflow with executable scripts and specific tool commands for Reasonix that are not commonly known.
What it needs
Requires git, python installed locally. About 4k tokens when loaded. Last updated 2026-08-03. 46,739 stars on the source repository.
What this skill does
CLI-Anything for Reasonix Use this skill when the user wants Reasonix to act like the CLI-Anything builder. Before implementation, use the full methodology source of truth when available: 1. If the current workspace is the CLI-Anything repository, read cli-anything-plugin/HARNESS.md. 2. If Reasonix is running from this adapter directory, also check ../cli-anything-plugin/HARNESS.md. 3. If neither local file is available, clone or download cli-anything-plugin from https://github.com/HKUDS/CLI-Anything/tree/main/cli-anything-plugin, then use HARNESS.md and the resources around it from that folder. 4. Only if local and network retrieval both fail, 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. Reasonix Tool Bindings Reasonix agents build harnesses by combining these built-in tools: Reasonix Tool Role in Harness Workflow --------------- -------------------------- bash Run shell commands, install packages, execute CLI tools, run tests, clone repos writefile Generate Python files (Click CLI, backend modules, tests, setup.py) editfile Make targeted edits to generated code (single replacement) multiedit Apply multiple atomic edits to a single file in one pass readfile Read target software source files, existing harness code, test results grep Search for patterns across the target software codebase (APIs, CLI tools, data models) glob Find files matching patterns in the source tree (.py, .xml, .json, etc.) ls List directory contents to understand project structure mcpcodegraphsearch / mcpcodegraphcontext Optional code graph analysis when CodeGraph is enabled (Reasonix strips the codegraph raw prefix, so the model-visible names omit it) webfetch Fetch documentation, API references, or remote files from the web Recommended Workflow with Reasonix Tools Phase 1 (Analysis) — Use ls + glob to survey the source tree, …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills hkuds/reasonix-skill