cli-anything-openclaw
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.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/barrontang/cli-anything-openclawUse 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
Inputs
Accept either:
- a local source path
- a GitHub repository URL
Derive the software name from the local directory name if needed.
Required references
Read these in order:
references/harness.md— core methodology and workflowreferences/codex-skill.md— condensed Codex-oriented rules- Relevant command references as needed:
references/cli-anything.mdreferences/cli-anything-refine.mdreferences/cli-anything-validate.mdreferences/cli-anything-test.mdreferences/cli-anything-list.md
Preferred workflow
- 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
Important constraints
- 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.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-barrontang-cli-anything-openclaw": {
"enabled": true,
"auto_update": true
}
}
}