SKILLEMALL.ai

AB 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.

ClawHub Agent Skills author: xb19960921 v1.1.0 MIT-0 19 files · 9 scripts body ≈ 2 356 tokens Open the sourceclawhub.ai↗ analyzed 5 d ago

Coordinate multi-agent swarm execution with a lightweight Pub/Sub protocol, standardized SwarmCommand messages, token-budget control, agent status tracking…

As a process B 71/100 · Nearly there — weak spots: inputs and preconditions, consistency, running it twice

ReferenceAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
B
71/100
Nearly there
Progress reporting w 2
0
Inputs and preconditions w 11
30
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    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: 16. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "last_updated"
    • note frontmatter-key unknown frontmatter key "changelog"

    Process rating: all ten parameters 71/100

    • 0Progress reporting. Says nothing while it works
    • 30Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 12 mutating operations with no state check
    • 40Consistency. Frontmatter name (swarm-coordinator) differs from the folder (swarm-executor)
    • 50Failures and branches. 0 branches, has a failure section
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 100Steps. 65 steps
    • 100Result and completion. Output format and completion criterion are stated
    • 100When it triggers. States when to use and when not to
    • 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.

    External checks

    ClawHub: suspicious
    The skill is purpose-aligned swarm coordination code, but its bundled deployment can expose coordination and monitoring services with weak defaults, so users should review it carefully before use.
    LLM: suspicious (high) · VirusTotal: · 16 Sept 2026