BF dev_team
Orchestrate a multi-agent dev/agency team with shared memory, handoffs, and OpenClaw sessions. Use when (1) First-time onboarding — follow references/OPENCLAW_TEAM_SETUP_GUIDE.md (guided variables + master prompt) and references/SKILL-SETUP.md, (2) Running specialized agents (PM, dev, QA, security) on customer or Shopware tasks, (3) Setting up shared team folders and SOUL.md identities, (4) sessions_spawn/sessions_send or control channels (e.g. Telegram), (5) Solo-founder multi-agent pattern from awesome-openclaw-usecases.
As a process F 40/100 · Will not run — References files that are not bundled: ../agent-team-orchestration-1.0.0/SKILL.md
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
body-longSKILL.md body ≈ 6999 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../agent-team-orchestration-1.0.0/SKILL.md
Process rating: all ten parameters 40/100
- 0Tools and files. 1 referenced file(s) missing: ../agent-team-orchestration-1.0.0/SKILL.md
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 15 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 40Consistency. Frontmatter name (dev_team) differs from the folder (dev-team)
- 50When it triggers. No condition that starts the skill
- 70Failures and branches. 8 branches
- 70Execution cost. Instruction body is 6999 tokens
- 85Steps. 61 steps, 1 vague phrases
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (23 tags): a typed call is more reliable
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
- +2Single-language instructions
- +3Description length 528: enough signal without eating the budget
- +4Structure: 39 headings
- +3Step-by-step instructions: 61 items
- +4Has examples (10 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.