BF openclaw-doc-finder
(no description)
As a process F 33/100 · Will not run — References files that are not bundled: references/fetched/<doc-name>.md, references/fetched/
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Exfiltration
read-dotenvreferences/troubleshoot.md:169Reads a .env filecat ~/.openclaw/.env | grep -i API_KEY
Files scanned: 8. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Implicit map keys need to be followed by map values at line 4, column 1: **触发条件（满足任一即可）：** ^^^^^^^^^^^^^^^^^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: references/fetched/<doc-name>.md - warning
missing-refreference to a missing file: references/fetched/
Process rating: all ten parameters 33/100
Will not run. References files that are not bundled: references/fetched/<doc-name>.md, references/fetched/
- 0Tools and files. 2 referenced file(s) missing: references/fetched/<doc-name>.md, references/fetched/
- 0Result and completion. Does not say what the result is
- 0When it triggers. No condition that starts the skill
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 100Steps. 40 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1016 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)
- +3Description length 0: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 16 headings
- +3Step-by-step instructions: 40 items
- +4Has examples (6 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.
External checks
ClawHub: suspicious
This appears to be a real OpenClaw documentation helper, but it has review-worthy side effects: silent script execution, persistent lookup logging, and unsafe secret-handling examples.
LLM: suspicious (high) · VirusTotal: · 29 May 2026