BF botlearn-healthcheck
Autonomously inspects a live OpenClaw instance across 5 health domains (hardware, config, security, skills, autonomy) and delivers a quantified traffic-light report with actionable fix guidance.
As a process F 46/100 · Will not run — References files that are not bundled: scripts/collect-*.sh
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- The text references files that are not there: add them or drop the references.
- 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 · 3
✓ No critical or high findings
Medium and low: 3
✓ Guard found no suspicious behaviour. 3 matches are attack strings quoted in this security skill's own documentation.
Files scanned: 27. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
body-longSKILL.md body ≈ 5065 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: scripts/collect-*.sh - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 46/100
- 0Tools and files. 1 referenced file(s) missing: scripts/collect-*.sh
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 1 mutating operations with no state check
- 40Consistency. Frontmatter name (botlearn-healthcheck) differs from the folder (botlearn-doctor-1-0-2)
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 5065 tokens
- 100Steps. 21 steps
- 100Failures and branches. 4 branches, has a failure section
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- 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)
- +3Output format is not stated: the model decides each time
- -2128 emoji in the instructions: noise for the model
- -36 of 17 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 194: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 21 items
- +4Has examples (9 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 50.