AA swarm-coordinator
Coordinate multi-agent swarm execution with a lightweight Pub/Sub protocol, standardized SwarmCommand messages, token-budget control, agent status tracking, negotiation, fallback, and completion gates. Use when building or reviewing multi-agent coordination, swarm execution, task delegation, agent handoff, token quota governance, Redis/in-memory PubSub orchestration, role-based agent teams, or safe parallel AI workflows.
As a process A 83/100 · Runs to the end — weak spots: inputs and preconditions, consistency, running it twice
How to improve
- 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: 16. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "last_updated" - note
frontmatter-keyunknown frontmatter key "changelog"
Process rating: all ten parameters 83/100
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 13 mutating operations with no state check
- 40Consistency. Frontmatter name (swarm-coordinator) differs from the folder (swarm-executor)
- 100Tools and files. No external tools needed
- 100Steps. 65 steps
- 100Result and completion. Output format and completion criterion are stated
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 8 branches, has a failure section
- 100Execution cost. Instruction body is 2356 tokens
- 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
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
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 424: enough signal without eating the budget
- +4Structure: 18 headings
- +3Step-by-step instructions: 65 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.