SKILLEMALL.ai

BF botlearn-healthcheck

botlearn-healthcheck — BotLearn autonomous health inspector for OpenClaw instances across 5 domains (hardware, config, security, skills, autonomy); triggers on system check, health report, diagnostics, or scheduled heartbeat inspection.

ClawHub Agent Skills author: asterisk622 v1.0.7 MIT-0 2 files body ≈ 1 944 tokens Open the sourceclawhub.ai analyzed 2 d ago

As a process F 62/100 · Will not run — References files that are not bundled: scripts/collect-status.sh, scripts/collect-env.sh, scripts/collect-config.sh

AnalyzerData and analyticsInfrastructuretype and topics are labelled automatically from the skill text
JSON
Technical rating
B
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
58
Run on models
none yet
Process rating
F
62/100
Will not run
References files that are not bundled: scripts/collect-status.sh, scripts/collect-env.sh, scripts/collect-config.sh
Tools and files w 18
0
Running it twice w 4
30
Consistency w 8
40
the three weakest of ten parameters · all ten
This is a copy of a skill from another catalog; the rating counts the canonical one: botlearn-healthcheck (ClawHub)

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. 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: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: scripts/collect-status.sh
  • warning missing-ref reference to a missing file: scripts/collect-env.sh
  • warning missing-ref reference to a missing file: scripts/collect-config.sh
  • warning missing-ref reference to a missing file: scripts/collect-logs.sh
  • warning missing-ref reference to a missing file: scripts/collect-skills.sh
  • warning missing-ref reference to a missing file: scripts/collect-precheck.sh
  • warning missing-ref reference to a missing file: scripts/collect-channels.sh
  • warning missing-ref reference to a missing file: scripts/collect-security.sh
  • warning missing-ref reference to a missing file: scripts/collect-workspace-audit.sh
  • warning missing-ref reference to a missing file: scripts/collect-*.sh
  • note frontmatter-key unknown frontmatter key "triggers"

Process rating: all ten parameters 62/100

Will not run. References files that are not bundled: scripts/collect-status.sh, scripts/collect-env.sh, scripts/collect-config.sh
  • 0Tools and files. 10 referenced file(s) missing: scripts/collect-status.sh, scripts/collect-env.sh, scripts/collect-config.sh
  • 30Running it twice. 1 mutating operations with no state check
  • 40Consistency. Frontmatter name (botlearn-healthcheck) differs from the folder (xiaoding-botlearn-healthcheck)
  • 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
  • 100Steps. 12 steps
  • 100Failures and branches. 2 branches, has a failure section
  • 100Execution cost. Instruction body is 1944 tokens
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 11 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (3 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)
  • +4No input/output examples
  • +1No license
  • +2Single-language instructions
  • +3Description length 236: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 12 items
  • +3Output format is stated explicitly

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

External checks

ClawHub: suspicious
This appears to be a legitimate OpenClaw health-check skill, but it can trigger broad local diagnostics too easily and collect sensitive system data without a clear upfront consent step.
LLM: suspicious (high) · VirusTotal: · 29 May 2026