CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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.

The body is a well-organized, appropriately terse instruction set that delegates the full methodology to HARNESS.md with a sensible local-then-network-then-condensed fallback chain. It consistently lands just below top marks: no CLI skeleton example, no failure-recovery loop after test runs, and its primary references sit outside the skill bundle.

Suggestions

Add a feedback loop to the Workflow (e.g., 'if tests fail, fix and re-run before updating README') to raise workflow_clarity from a sequence with checkpoints to one with explicit error recovery.

Include a minimal executable Click CLI snippet showing REPL-default and --json output patterns, so the Build mode is actionable even when the external HARNESS.md is unreachable.

Remove the redundant opening line 'Use this skill when the user wants Hermes Agent to act like the CLI-Anything builder' — it duplicates the frontmatter description Claude already reads.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — tables, exact file paths, and packaging rules with no explanation of Click or basic CLI concepts. Minor trimmable instances remain: "Use this skill when the user wants Hermes Agent to act like the `CLI-Anything` builder" restates the frontmatter, and the fallback prose could be tightened, so it sits at anchor 4 rather than anchor 5.

4 / 5

Actionability

Concrete guidance throughout: the exact harness directory tree, `find namespace_packages(include=["cli_anything.*"])`, the `cli-anything-<software>` console script, `pip install -e .` verification, and named test files (`test_core.py`, `test_full_e2e.py`). However, there is no example CLI skeleton or command template, and the core methodology is deferred to an external `HARNESS.md`, leaving gaps short of anchor 5's copy-paste-ready coverage.

4 / 5

Workflow Clarity

The 7-step Workflow is a clear sequence (acquire → analyze → design → implement → TEST.md/tests/run → README → `pip install -e .`) with validation checkpoints at steps 5 and 7, and the Test mode specifies testing the installed command via subprocess. No explicit feedback loop for failed tests or installation errors exists, so it matches anchor 4 rather than anchor 5's error-recovery loops.

4 / 5

Progressive Disclosure

Sections are well organized and the two references (`../cli-anything-plugin/HARNESS.md` with a clone fallback, `../registry.json`) are one level deep and clearly signaled, with bundle scripts/ appropriately reserved for installation. The key methodology reference lives outside the skill directory and cannot be guaranteed present when installed — a minor organization gap that keeps it at anchor 4 rather than anchor 5.

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' clause naming four concrete trigger verbs, a clear artifact ('CLI-Anything harness'), and a well-defined Hermes Agent niche. Its only shortfalls are minor: it omits what the generated harness concretely provides and lacks synonyms like 'CLI' or 'command-line'.

DimensionReasoningScore

Specificity

"build, refine, test, or validate a CLI-Anything harness for a GUI application or source repository" lists several specific actions with a concrete target, but it never states what the harness concretely provides (e.g., Click CLI, REPL, JSON output), leaving minor gaps in coverage short of the comprehensive anchor 5.

4 / 5

Completeness

It explicitly answers both: the 'when' is a concrete "Use when the user wants Hermes Agent to build, refine, test, or validate a CLI-Anything harness" trigger phrase, and the 'what' is "Adapts the CLI-Anything methodology to Hermes without changing the generated Python harness format". This matches anchor 5's both-what-and-when-with-concrete-triggers better than anchor 4, whose 'when' is less specific.

5 / 5

Trigger Term Quality

Natural action verbs ("build", "refine", "test", "validate") plus "GUI application" and "source repository" are phrasings users would actually say, but common synonyms like "CLI", "command-line", or "wrapper" are missing, so coverage falls just short of anchor 5's comprehensive synonym set.

4 / 5

Distinctiveness Conflict Risk

The "Hermes Agent" qualifier carves out a clear niche and the CLI-Anything framing is distinctive, but the trigger verbs could overlap with a closely related parent CLI-Anything builder skill for other agents, which is anchor 4's minor overlap risk rather than anchor 5's minimal risk.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

HKUDS/CLI-Anything

Path

hermes-skill/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.