CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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-Anything methodology to OpenClaw without changing the generated Python harness format.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A lean, well-structured methodology document that gives concrete structure, packaging, and workflow guidance with validation checkpoints and a sensible fallback when the external methodology file is absent. Its gaps are the absence of any example CLI command, an unspecified TEST.md format, no explicit fix-and-retry loop, and a primary reference that is external to the bundle rather than shipped in references/.

Suggestions

Add one short example of a generated subcommand (Click decorator, --json flag, REPL behavior) so implementers have copy-paste-ready guidance for the core deliverable.

Make the test workflow a feedback loop: after step 5, add 'If tests fail, fix the harness and re-run before proceeding' to reach explicit validation/recovery.

Ship the condensed HARNESS.md methodology as a references/ file inside the bundle (linking it from SKILL.md) so the primary source of truth survives standalone distribution instead of relying on ../cli-anything-plugin/.

DimensionReasoningScore

Conciseness

The body is tight and rule-driven with no explanations of concepts Claude already knows, but "Use this skill when the user wants OpenClaw to act like the `CLI-Anything` builder." duplicates the frontmatter description and could be trimmed.

4 / 5

Actionability

Concrete guidance throughout — an exact directory layout, specific filenames (test_core.py, utils/<software>_backend.py), exact packaging directives (find_namespace_packages(include=["cli_anything.*"]), console_scripts -> cli-anything-<software>), and `pip install -e .` — but no example CLI command or signature and no specification of TEST.md's content.

4 / 5

Workflow Clarity

The 7-step numbered Workflow is clearly sequenced with validation checkpoints ("Write TEST.md, then tests, then run them"; "Verify local installation with `pip install -e .`") plus a Validate-mode checklist, but there is no explicit error-recovery loop (e.g., 'if tests fail, fix and re-run').

4 / 5

Progressive Disclosure

Well-sectioned content with a single, clearly signaled one-level-deep reference and a graceful fallback ("If it is not available, follow the condensed rules below"), but the sole reference (`../cli-anything-plugin/HARNESS.md`) lives outside the skill bundle, so it dangles when the skill ships standalone.

4 / 5

Total

16

/

20

Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit 'Use when' trigger clause, a clear statement of what it does, and lifecycle-wide action verbs that mirror the body's modes. Its main weaknesses are reliance on the 'CLI-Anything' methodology name as a trigger and omission of the concrete deliverable and natural synonyms like 'command-line interface' or 'CLI wrapper'.

Suggestions

Name the concrete deliverable in the description (e.g., 'generates a stateful Click CLI with --json output and REPL mode as an installable cli-anything-<software> package') so the 'what' is tangible without knowing the methodology.

Add natural trigger synonyms such as 'command-line interface', 'CLI wrapper', or 'expose a GUI application's features as commands' to broaden keyword coverage beyond the 'CLI-Anything' brand name.

DimensionReasoningScore

Specificity

"build, refine, test, or validate a CLI-Anything harness for a GUI application or source repository" lists several concrete actions covering the skill's four modes, but the tangible deliverable (a stateful Click CLI / installable Python package) is never named, leaving minor gaps in coverage.

4 / 5

Completeness

It explicitly answers both questions: the trigger clause "Use when the user wants OpenClaw to build, refine, test, or validate a CLI-Anything harness..." gives a concrete when, and "Adapts the CLI-Anything methodology to OpenClaw without changing the generated Python harness format" states the what.

5 / 5

Trigger Term Quality

Terms like "build", "test", "validate", "CLI-Anything harness", "GUI application", and "source repository" are words a user would plausibly say, but common natural variations ("command-line interface", "CLI wrapper", "expose the GUI as commands") are missing.

4 / 5

Distinctiveness Conflict Risk

The CLI-Anything harness niche is clearly distinct from other skills, but the phrase "build ... for a GUI application or source repository" risks capturing generic 'build a CLI for this app' requests intended for a plain CLI, so overlap risk is minor rather than minimal.

4 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

HKUDS/CLI-Anything

Path

macrocli/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.