SKILLEMALL.ai
GitHub ↗ RU Sign in

BD hermes-doctor

诊断与抢救 Hermes Agent (NousResearch) 故障 — 401/Authentication Fails、provider 切换后 key 没注入、credential_pool 缺条目、HERMES_HOME 被环境变量重定向、gateway lock、stale config、备份恢复。Windows 优先。覆盖 .env / auth.json / HKCU\Environment / config.yaml profile 四处残留点排查、hermes auth 子命令族(v2026.4.3+)、credential_pool 4 种 rotation 策略、已知 issues

ClawHub Hermes author: dongsheng123132 v1.1.0 MIT-0 12 files body ≈ 1 263 tokens Open the sourceclawhub.ai↗ analyzed 4 d ago

As a process D 45/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationInfrastructureAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
65
Run on models
none yet
Process rating
D
45/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 12. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 307 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill
  • note frontmatter-key unknown frontmatter key "homepage"
  • note frontmatter-key unknown frontmatter key "repository"

Process rating: all ten parameters 45/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 1 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 60Consistency. The Hermes dialect needs category and tags
  • 100Steps. 48 steps
  • 100Execution cost. Instruction body is 1263 tokens
  • low The response is described with custom markup (12 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)
  • +3Output format is not stated: the model decides each time
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • +2Single-language instructions
  • +3Description length 307: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 48 items
  • +4Has examples (1 code blocks)
  • +4Reference files are cited in the instructions (7 of 7)
  • +1License stated

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

External checks

ClawHub: suspicious
This appears to be a legitimate Hermes troubleshooting guide, but it needs review because it directs agents to inspect, copy, back up, and modify API keys and auth files without consistently warning users how to protect them.
LLM: suspicious (high) · VirusTotal: · 29 May 2026