AF team-builder
Discover, compose, and activate specialist teams from 3 rosters — OpenClaw Core (CEO/Artist), Agency Division (55+ specialists), and Research Lab (autonomous experiment loops via Karpathy's autoresearch). Planner proposes optimal teams; Reviewer validates deliverables.
As a process F 34/100 · Will not run — weak spots: steps, result and completion, when it triggers
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
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: 13. 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")
Process rating: all ten parameters 34/100
- 0Steps. Prose only: no discrete steps
- 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
- 40Consistency. Frontmatter name (team-builder) differs from the folder (oc-team-builder)
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 1688 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
- +1No license
- +2Single-language instructions
- +3Description length 269: enough signal without eating the budget
- +4Structure: 20 headings
- +4Has examples (11 code blocks)
- +4Reference files are cited in the instructions (6 of 6)
- +3All 5 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.
External checks
ClawHub: suspicious
This skill is disclosed as a team and research helper, but its experiment mode can run shell commands, change repositories, and continue autonomously with weak safeguards.
LLM: suspicious (high) · VirusTotal: · 29 May 2026