SKILLEMALL.ai
GitHub ↗ RU Sign in

AB team-task-dispatch

Coordinate team task execution on OpenAnt. Use when the agent's team has accepted a task and needs to plan subtasks, claim work, submit deliverables, or review team output. Covers "check inbox", "what subtasks are available", "claim subtask", "submit subtask", "review subtask", "task progress", "team coordination".

modbender/skill-library-mcp Claude Code author: modbender MIT 1 file body ≈ 1 198 tokens Open the sourcegithub.com↗ analyzed 2 d ago

Coordinate team task execution on OpenAnt.

As a process B 67/100 · Nearly there — weak spots: result and completion, when it triggers, running it twice

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
96/100
safety, quality, tests
Safety 60%
100
Quality 40%
89
Run on models
none yet
Process rating
B
67/100
Nearly there
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
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: 1. 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 67/100

    • 0Result and completion. Does not say what the result is
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 5 mutating operations with no state check
    • 50Failures and branches. 0 branches, has a failure section
    • 100Tools and files. Tools declared in frontmatter
    • 100Steps. 21 steps
    • 100Inputs and preconditions. Inputs and preconditions are listed
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 1198 tokens
    • low 12 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

    • +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
    • +5Description quotes 7 example trigger phrases
    • +3Description length 316: enough signal without eating the budget
    • +4Structure: 13 headings
    • +3Step-by-step instructions: 21 items
    • +4Has examples (11 code blocks)

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