BD agent-hierarchy-100
A system for designing and managing multi-level subagent hierarchies in OpenClaw. Provides explicit upgrade paths, quality gates, and capability unlocks across escalating agent levels. Use this skill only when the user explicitly asks to build, scale, or upgrade a structured hierarchy of subagents — not for ordinary single-agent tasks.
A system for designing and managing multi-level subagent hierarchies in OpenClaw.
As a process D 42/100 · Unfinished process — weak spots: steps, result and completion, inputs and preconditions
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 24. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8471 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "triggers"
Process rating: all ten parameters 42/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
- 30Running it twice. 104 mutating operations with no state check
- 40Execution cost. Instruction body is 8471 tokens: crowds the task out of the window
- 100Tools and files. No external tools needed
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
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
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- -46 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 337: enough signal without eating the budget
- +4Structure: 112 headings
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 70.