Agent skill · software engineering · hkuds
cli-anything-hermes
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.
Why this skill is useful
Adds a comprehensive CLI harness generation workflow for GUI applications that includes executable scripts and specific methodologies not found in public documentation.
What it needs
Requires git 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 Hermes Agent 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: 1. If this skill is being used from inside the CLI-Anything repository, read ../cli-anything-plugin/HARNESS.md first. 2. If that local file is unavailable, 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. 3. Only if both local and network retrieval 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. Hermes Tool Bindings 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 executecode Generate and write Python files (Click CLI, backend modules, tests) delegatetask Parallelize analysis or generation subtasks readfile / writefile Read and write harness source files patch Make targeted edits to generated code Consult the Hermes Agent documentation for the exact tool invocation syntax. 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. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills hkuds/hermes-skill