BC task-dispatcher
智能任务分发与子代理协调中枢。当用户提交任何任务时，执行需求分析、任务拆解、分发策略制定，分发给合适的 subagent 执行，监控进度并阶段汇报，最终汇总结果。失败时自动兜底处理。适用于：（1）用户直接下达的任务（2）cron/heartbeat 触发的任务（3）任何需要多步骤处理的工作。
As a process C 55/100 · Has gaps — 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.
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: 8. 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 55/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
- 20When it triggers. No condition that starts the skill
- 100Tools and files. No external tools needed
- 100Steps. 154 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2773 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- -41 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 146: enough signal without eating the budget
- +4Structure: 60 headings
- +3Step-by-step instructions: 154 items
- +4Has examples (15 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 68.
External checks
ClawHub: suspicious
This is mostly a disclosed task-orchestration skill, but its bundled cleanup rules can automatically delete broad local files without clear enough user control.
LLM: suspicious (high) · VirusTotal: · 29 May 2026