SKILLEMALL.ai
GitHub ↗ RU Sign in

AD agent-team-orchestration

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows. Use when: (1) Setting up a team of 2+ agents with different specializations, (2) Defining task routing and lifecycle (inbox → spec → build → review → done), (3) Creating handoff protocols between agents, (4) Establishing review and quality gates, (5) Managing async communication and artifact sharing between agents.

modbender/skill-library-mcp Agent Skills author: modbender MIT 5 files body ≈ 1 325 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Orchestrate multi-agent teams with defined roles, task lifecycles, handoff protocols, and review workflows.

As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
95/100
safety, quality, tests
Safety 60%
100
Quality 40%
88
Run on models
none yet
Process rating
D
49/100
Unfinished process
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
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: 5. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 49/100

    • 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
    • 30Running it twice. 2 mutating operations with no state check
    • 40Result and completion. Does not say what the result is
    • 60Tools and files. Uses tools (bash) that frontmatter does not declare
    • 100Steps. 14 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1325 tokens

    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
    • +1No license
    • +2Single-language instructions
    • +3Description length 424: enough signal without eating the budget
    • +4Structure: 18 headings
    • +3Step-by-step instructions: 14 items
    • +4Has examples (4 code blocks)
    • +4Reference files are cited in the instructions (4 of 4)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.