BF multi-agent-workshop
七阶段（含阶段0任务澄清）多角色工作坊；角色种类与人数均由任务决定。触发词："多角色研讨"、"需求工作坊"、"需求评审"、"圆桌"、"定方案再执行"。
As a process F 37/100 · Will not run — References files that are not bundled: scripts/phases/00-…06-*.md, references/sample-roles/*.md, scripts/run_*.py
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The text references files that are not there: add them or drop the references.
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: 29. 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") - warning
missing-refreference to a missing file: scripts/phases/00-…06-*.md - warning
missing-refreference to a missing file: references/sample-roles/*.md - warning
missing-refreference to a missing file: scripts/run_*.py
Process rating: all ten parameters 37/100
Will not run. References files that are not bundled: scripts/phases/00-…06-*.md, references/sample-roles/*.md, scripts/run_*.py
- 0Tools and files. 3 referenced file(s) missing: scripts/phases/00-…06-*.md, references/sample-roles/*.md, scripts/run_*.py
- 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
- 20When it triggers. No condition that starts the skill
- 100Steps. 44 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3787 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- low 15 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (52 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)
- +3Description length 75: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +4Structure: 21 headings
- +3Step-by-step instructions: 44 items
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (8 of 8)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 64.
External checks
ClawHub: suspicious
The skill is mostly a disclosed local workshop workflow, but it includes under-scoped maintenance commands and unsafe network handling that users should review before installing.
LLM: suspicious (high) · VirusTotal: · 29 May 2026