Use when the user wants Codex to build, refine, test, validate, or list CLI-Anything harnesses for GUI applications or source repositories. Adapts the full CLI-Anything methodology to Codex without changing the generated Python harness format.
84%
Does it follow best practices?
Impact
95%
1.55xAverage score across 3 eval scenarios
Passed
No findings from the security scan
Use this skill when the user wants Codex to act like the CLI-Anything builder.
Before implementation, use the full methodology source of truth:
references/HARNESS.md relative to this skill directory.references/commands/.references/guides/ only when they apply to the target.CLI-Anything repository checkout, read ../cli-anything-plugin/HARNESS.md and
the resources around it.https://github.com/HKUDS/CLI-Anything and use cli-anything-plugin/HARNESS.md.The installer vendors the canonical resources from cli-anything-plugin/ into this
skill so a normal Codex installation is self-contained.
| Path | Purpose |
|---|---|
references/HARNESS.md | Complete methodology and quality rules |
references/commands/cli-anything.md | Build-mode specification |
references/commands/refine.md | Refine-mode specification |
references/commands/test.md | Test-mode specification |
references/commands/validate.md | Validation checklist |
references/commands/list.md | Installed/generated harness discovery |
references/guides/ | On-demand implementation guidance |
scripts/repl_skin.py | Copy into generated harnesses as utils/repl_skin.py |
scripts/preview_bundle.py | Copy into preview-capable harnesses as utils/preview_bundle.py |
scripts/skill_generator.py | Generate canonical and packaged CLI skills |
scripts/templates/SKILL.md.template | Skill generation template used by skill_generator.py |
references/docs/PREVIEW_PROTOCOL.md | Shared preview bundle protocol |
When reading vendored documents, apply these path remappings instead of resolving plugin paths against the current working directory:
| Document reference | Installed skill path |
|---|---|
guides/... | references/guides/... |
cli-anything-plugin/repl_skin.py | scripts/repl_skin.py |
cli-anything-plugin/preview_bundle.py | scripts/preview_bundle.py |
cli-anything-plugin/skill_generator.py | scripts/skill_generator.py |
templates/SKILL.md.template | scripts/templates/SKILL.md.template |
docs/PREVIEW_PROTOCOL.md | references/docs/PREVIEW_PROTOCOL.md |
Accept either:
./gimp or /path/to/softwareDerive the software name from the local directory name after cloning if needed.
Read references/commands/cli-anything.md. Build a complete harness through source
analysis, architecture design, implementation, test planning, test implementation,
test documentation, CLI-specific SKILL.md generation, and local installation.
Read references/commands/refine.md. Inventory current commands and tests, compare
them against the target software, then incrementally add high-impact capabilities
without removing existing commands unless the user requests a breaking change.
Read references/commands/test.md. Run the harness tests against the real backend,
verify installed-command subprocess coverage, and update TEST.md only with passing
results.
Read references/commands/validate.md. Validate the harness against the complete
directory, implementation, test, documentation, packaging, and code-quality checklist.
Read references/commands/list.md. Discover installed and generated CLI-Anything tools
and support human-readable or JSON output as requested.
Use these only when the full methodology cannot be retrieved.
Produce:
<software>/
└── agent-harness/
├── <SOFTWARE>.md
├── setup.py
└── cli_anything/
└── <software>/
├── README.md
├── __init__.py
├── __main__.py
├── <software>_cli.py
├── core/
├── utils/
└── tests/--json machine-readable output.--dry-run.ReplSkin.SKILL.md files.TEST.md before test code.test_core.py for unit coverage.test_full_e2e.py for real-file workflows and real backend validation.cli-anything-<software> command via _resolve_cli().CLI_ANYTHING_FORCE_INSTALLED=1.find_namespace_packages(include=["cli_anything.*"]).cli_anything/ as a namespace package without a top-level __init__.py.cli-anything-<software> through console_scripts.skills/SKILL.md.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.