Use when the user wants Hermes Agent to build, refine, test, or validate a CLI-Anything harness for a GUI application or source repository. Adapts the CLI-Anything methodology to Hermes without changing the generated Python harness format.
82%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
Use this skill when the user wants Hermes Agent to act like the CLI-Anything builder.
Before implementation, use the full methodology source of truth when available:
CLI-Anything repository, read ../cli-anything-plugin/HARNESS.md first.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.Accept either:
./gimp or /path/to/softwareDerive the software name from the local directory name after cloning if needed.
Hermes agents build harnesses by combining these built-in tools:
| Tool | Role in Harness Workflow |
|---|---|
terminal | Run shell commands, install packages, execute CLI tools, run tests |
execute_code | Generate and write Python files (Click CLI, backend modules, tests) |
delegate_task | Parallelize analysis or generation subtasks |
read_file / write_file | Read and write harness source files |
patch | Make targeted edits to generated code |
Consult the Hermes Agent documentation for the exact tool invocation syntax.
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 .For an up-to-date list of supported harnesses and their backend patterns, see registry.json at the repository root.
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.