BF dev-team
Multi-agent development team orchestration. Use when managing coding agents (Codex, Claude Code, Gemini, Cursor) for automated software development: (1) Spawning agents for tasks, (2) Monitoring agent status, (3) Managing git worktrees, (4) Automated code review, (5) Handling notifications via Feishu.
Multi-agent development team orchestration.
As a process F 33/100 · Will not run — References files that are not bundled: scripts/dev-board/, assets/logs/reviews/review-<pr>-<ts>.aggregate.json, assets/active-tasks.json
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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: scripts/dev-board/ - warning
missing-refreference to a missing file: assets/logs/reviews/review-<pr>-<ts>.aggregate.json - warning
missing-refreference to a missing file: assets/active-tasks.json - warning
missing-refreference to a missing file: assets/tasks.json - warning
missing-refreference to a missing file: assets/logs/archives/queue-history-YYYY-MM.jsonl - warning
missing-refreference to a missing file: assets/logs/archives/task-history-YYYY-MM.jsonl
Process rating: all ten parameters 33/100
- 0Tools and files. 6 referenced file(s) missing: scripts/dev-board/, assets/logs/reviews/review-<pr>-<ts>.aggregate.json, assets/active-tasks.json
- 0Result and completion. Does not say what the result is
- 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
- 40Consistency. Frontmatter name (dev-team) differs from the folder (team-dev)
- 50Failures and branches. 0 branches, has a failure section
- 100Steps. 111 steps
- 100Execution cost. Instruction body is 2546 tokens
- low The response is described with custom markup (3 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
- -2localhost URLs: will not work for another user
- -32 of 15 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 302: enough signal without eating the budget
- +4Structure: 30 headings
- +3Step-by-step instructions: 111 items
- +4Has examples (16 code blocks)
- +4Reference files are cited in the instructions (7 of 7)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 71.