Description

name: cli-anything-openclaw description: Adapt HKUDS CLI-Anything for OpenClaw workflows. Use when the user wants to build, refine, test, or validate an agent-native CLI harness for a GUI application or source repository inside OpenClaw, mentions CLI-Anything, or asks to apply the CLI-Anything methodology on a local path or GitHub repo.

Use this skill as an OpenClaw-native bridge to the upstream CLI-Anything methodology.

What this skill is

This skill packages the core CLI-Anything methodology in a portable form for OpenClaw users.

Use it when the user wants to:

analyze whether a software project is a good fit for an agent-friendly CLI harness
design command groups and workflow structure for a GUI application or repo
refine an existing harness
validate packaging, tests, and CLI entry points using CLI-Anything-style thinking

Accept either:

Derive the software name from the local directory name if needed.

Read these in order:

Acquire source locally if needed.
Analyze architecture, backend surfaces, data model, and current automation affordances.
Decide whether the project is a good fit for an agent-native CLI harness.
If building:
- propose command groups
- propose state model
- propose agent-harness/ layout
If refining:
- inventory current commands and tests
- identify gaps
- prioritize high-impact additions
If validating:
- check packaging, CLI namespace, tests, and JSON output expectations
Always report:
- files changed or proposed
- commands run
- risks / limitations
- next best step

Treat this as a methodology skill, not as a promise that a harness already exists.
Prefer wrapping real software backends rather than reimplementing behavior.
Plan tests before writing them.
Keep outputs concrete and actionable.