BD multi-agent-pipeline
多Agent协作研究管线 — 将"调研→框架→执行→审核→迭代→交付"的咨询项目工作流抽象为可复制的标准化协议。触发场景：(1) 新项目需要多Agent协作且横跨多个平台（Claude/Codex/Gemini/Minimax），(2) 咨询类交付物需要多轮结构化审核迭代，(3) 需要建立项目状态追踪机制替代散落的进度文档，(4) 需要防止内部代号/敏感信息泄漏到交付物，(5) 需要明确Human决策节点避免Agent过度自主。核心解决的问题：审核意见靠聊天中转导致失真、内部代号泄漏到v4才发现、Human决策点散落在对话中无法追溯。
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 25. 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 41/100
- 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 (multi-agent-pipeline) differs from the folder (consulting-agent-pipeline)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 19 steps
- 100Execution cost. Instruction body is 1813 tokens
- 100Running it twice. No mutating operations
- low 11 top-level sections: this looks like several domains in one skill
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
- -5TODO / placeholder text left in the skill
- -214 emoji in the instructions: noise for the model
- +1No license
- +2Single-language instructions
- +3Description length 270: enough signal without eating the budget
- +4Structure: 13 headings
- +3Step-by-step instructions: 19 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (5 of 5)
- +3All 5 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.