BF autofix
A comprehensive, self-evolving skill designed to diagnose and solve OpenClaw issues by following a structured, multi-stage resolution cycle. It incorporates Proactive Prediction (L2), Robustness Checks (L1), Knowledge Creation (L3), and **Diagnosis Report Visualization** (v5.0).
As a process F 49/100 · Will not run — References files that are not bundled: docs/MODULE_03_Enhancement_Reports.md
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.
- 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 Secrets in code
secret-high-entropy-tokendocs/enhancement/MODULE_03_Enhancement_Reports.md:2High-entropy token-like string (may be an id, hash or a credential)name: MODU…rts
Files scanned: 17. 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: docs/MODULE_03_Enhancement_Reports.md
Process rating: all ten parameters 49/100
- 0Tools and files. 1 referenced file(s) missing: docs/MODULE_03_Enhancement_Reports.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (autofix) differs from the folder (autofix-theclaw)
- 70When it triggers. States when to use, but not when not to
- 100Steps. 43 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 1268 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- +4No input/output examples
- -219 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 279: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 43 items
- +4Reference files are cited in the instructions (4 of 5)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.