BF meta-skill
Trajectory compiler that converts real OpenClaw session traces (or raw_trajectory_log) into a parameterized, reusable Skill via 4 stages: trace interception → DAG abstraction → schema+code synthesis → registration.
As a process F 24/100 · Will not run — References files that are not bundled: references/schema.json, references/plan.json, references/run-flow.md
GeneratorSoftware developmentInfrastructuretype and topics are labelled automatically from the skill text
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 · 0
✓ No critical or high findings
Files scanned: 7. 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
missing-refreference to a missing file: references/schema.json - warning
missing-refreference to a missing file: references/plan.json - warning
missing-refreference to a missing file: references/run-flow.md - warning
missing-refreference to a missing file: scripts/run.js
Process rating: all ten parameters 24/100
Will not run. References files that are not bundled: references/schema.json, references/plan.json, references/run-flow.md
- 0Tools and files. 4 referenced file(s) missing: references/schema.json, references/plan.json, references/run-flow.md
- 0Result and completion. Does not say what the result is
- 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
- 20When it triggers. No condition that starts the skill
- 25Steps. 1 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 251 tokens
- 100Running it twice. No mutating operations
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)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 214: enough signal without eating the budget
- +4Structure: 7 headings
- +4Reference files are cited in the instructions (2 of 2)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.
External checks
ClawHub: suspicious
This skill appears to do what it claims, but it can turn sensitive local OpenClaw session history into persistent executable skills without enough warnings, staging, or review controls.
LLM: suspicious (high) · VirusTotal: · 29 May 2026