BF agent-builder
Build high-performing OpenClaw agents end-to-end. Use when you want to design a new agent (persona + operating rules) and generate the required OpenClaw workspace files (SOUL.md, IDENTITY.md, AGENTS.md, USER.md, HEARTBEAT.md, optional MEMORY.md + memory/YYYY-MM-DD.md). Also use to iterate on an existing agent's behavior, guardrails, autonomy model, heartbeat plan, and skill roster.
As a process F 39/100 · Will not run — References files that are not bundled: references/openclaw-workspace.md, references/templates.md, references/architecture.md
How to improve
- 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 · 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
missing-refreference to a missing file: references/openclaw-workspace.md - warning
missing-refreference to a missing file: references/templates.md - warning
missing-refreference to a missing file: references/architecture.md
Process rating: all ten parameters 39/100
- 0Tools and files. 3 referenced file(s) missing: references/openclaw-workspace.md, references/templates.md, references/architecture.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 3 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (agent-builder) differs from the folder (agent-builder1)
- 55Failures and branches. 1 branches
- 100Steps. 38 steps
- 100Execution cost. Instruction body is 750 tokens
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
- +1No license
- +2Single-language instructions
- +3Description length 384: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 38 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.