SKILLEMALL.ai
GitHub ↗ RU Sign in

BC cli-anything-hermes

Use when the user wants Hermes Agent to build, refine, test, or validate a CLI-Anything harness for a GUI application or source repository. Adapts the CLI-Anything methodology to Hermes without changing the generated Python harness format.

HKUDS/CLI-Anything Agent Skills author: HKUDS Apache-2.0 4 files · 2 scripts body ≈ 1 051 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Adapts the CLI-Anything methodology to Hermes without changing the generated Python harness format.

As a process C 50/100 · Has gaps — References files that are not bundled: ../registry.json

IntegrationGitHubSoftware developmentAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
B
91/100
safety, quality, tests
Safety 60%
100
Quality 40%
78
Run on models
none yet
Process rating
C
50/100
Has gaps
References files that are not bundled: ../registry.json
Tools and files w 18
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning missing-ref reference to a missing file: ../registry.json

Process rating: all ten parameters 50/100

Will not run. References files that are not bundled: ../registry.json
  • 0Tools and files. 1 referenced file(s) missing: ../registry.json
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 40Consistency. Frontmatter name (cli-anything-hermes) differs from the folder (hermes-skill)
  • 60Result and completion. Output format stated, no completion criterion
  • 70When it triggers. States when to use, but not when not to
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 85Steps. 33 steps, 1 vague phrases
  • 100Execution cost. Instruction body is 1051 tokens
  • 100Running it twice. No mutating operations
  • low The response is described with custom markup (4 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • -32 of 2 scripts are never mentioned in SKILL.md
  • +1No license
  • +2Single-language instructions
  • +3Description length 239: enough signal without eating the budget
  • +4Structure: 13 headings
  • +3Step-by-step instructions: 33 items
  • +3Output format is stated explicitly
  • +4Has examples (1 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.