cli-anything

Use when the user wants OpenClaw to build, refine, test, or validate a CLI-Anything harness for a GUI application or source repository. Adapts the CLI-Anythi...

Security Scan

Instruction-only skill that is internally consistent with its stated purpose (building CLI harnesses) and requests no credentials or installs, but it will read local source trees and run/validate code from those trees so run it only on trusted code or in isolation.

Purpose & Capability

The name/description (build/refine/test/validate CLI harnesses) matches the SKILL.md requirements: it expects a local path or repo URL, describes harness layout, testing, packaging, and validation. There are no unrelated env vars, binaries, or install steps requested.

Instruction Scope

The instructions legitimately direct the agent to read local source trees (and, when present, ../cli-anything-plugin/HARNESS.md), analyze architecture, and run tests/installation commands (e.g., pip install -e ., subprocess invocations). This is expected for a harness-builder but means the agent will access and execute code from the target repo — a potential risk if the repo is untrusted.

Install Mechanism

No install spec and no code files are included in the skill package, so nothing is written to disk by the skill itself. The only instructions that may install things are user-directed steps (e.g., pip install -e .) applied to the target repository, which is appropriate for the stated purpose.

Credentials

The skill declares no required environment variables, credentials, or config paths. The SKILL.md does not ask for secrets or unrelated credentials.

Persistence & Privilege

always is false and the skill is user-invocable. It does not request persistent system-wide privileges or modify other skills' configurations.

Assessment

This skill is instruction-only and coherent for building CLI harnesses. Before running it: (1) only use it on source trees you trust or run in an isolated environment (container/VM) because it advises installing and executing code from the target repo; (2) review any ../cli-anything-plugin/HARNESS.md referenced by the instructions if present; (3) inspect changes the agent proposes to ensure it doesn't modify unrelated files; (4) prefer running tests and installation steps manually or in sandboxed CI to limit risk from untrusted repositories.

CLI-Anything for OpenClaw

Use this skill when the user wants OpenClaw to act like the CLI-Anything builder.

If this skill is being used from inside the CLI-Anything repository, read ../cli-anything-plugin/HARNESS.md before implementation. That file is the full methodology source of truth. If it is not available, 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.

Modes

Build

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:

• 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.

Test

Plan tests before writing them. Keep both:

• test_core.py for unit coverage
• test_full_e2e.py for workflow and backend validation

When possible, test the installed command via subprocess using cli-anything-<software> rather than only module imports.

Validate

Check that the harness:

• uses the cli_anything.<software> namespace package layout
• has an installable setup.py entry point
• supports JSON output
• has a REPL default path
• documents usage and tests

Backend Rules

Prefer 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.

Packaging Rules

• Use find_namespace_packages(include=["cli_anything.*"])
• Keep cli_anything/ as a namespace package without a top-level __init__.py
• Expose cli-anything-<software> through console_scripts

Workflow

1. Acquire the source tree locally.
2. Analyze architecture, data model, existing CLIs, and GUI-to-API mappings.
3. Design command groups and state model.
4. Implement the harness.
5. Write TEST.md, then tests, then run them.
6. Update README usage docs.
7. Verify local installation with pip install -e .

Output Expectations

When reporting progress or final results, include:

• target software and source path
• files added or changed
• validation commands run
• open risks or backend limitations