← Back to Skills Marketplace
526
Downloads
1
Stars
2
Active Installs
8
Versions
Install in OpenClaw
/install team-dispatch
Description
Use when a request requires multi-agent workflow orchestration (task decomposition + dependency/DAG + parallel execution), needs durable task tracking across...
Usage Guidance
This package contains many scripts and will modify your OpenClaw installation (create ~/.openclaw symlinks, write agent workspaces, edit openclaw.json, install a watcher/launchd job, and restart the Gateway). Before running anything or allowing an agent to execute the detection/install flow: 1) Inspect scripts/setup.sh, scripts/watch.sh, scripts/watch.py and publish-clawhub.mjs to see exactly what they do (file copies, edits, network calls, service restarts). 2) Backup ~/.openclaw/openclaw.json and any existing agent dirs. 3) Check for any hardcoded paths or placeholders (e.g., the plist uses literal HOME in some entries). 4) Confirm you are comfortable granting the skill permission to edit openclaw.json and to set main.subagents.allowAgents: ["*"], as this widens which subagents the main dispatcher can spawn. 5) If you do not want persistent watchers or automated gateway restarts, avoid running setup.sh or run it with a dry‑run / in a sandbox. 6) Verify which model/provider credentials are required (OAuth/API keys) — the skill doesn’t list them but will likely need provider access to function. If you are unsure, treat this as untrusted code and run inside an isolated environment or review with a sysadmin before installing.
Capability Analysis
Type: OpenClaw Skill
Name: team-dispatch
Version: 1.0.8
The skill bundle implements a complex multi-agent orchestration system that performs significant system-level modifications and installs background persistence. Key indicators include 'watch-install.sh', which installs background services via launchd, systemd, or cron for task monitoring, and 'setup.sh', which modifies the global 'openclaw.json' configuration to grant broad sub-agent spawning permissions ('allowAgents: ["*"]'). Additionally, 'SKILL.md' contains instructions directing the AI agent to automatically execute these high-privilege setup scripts upon reading the file. While these behaviors are aligned with the stated purpose of durable workflow orchestration, the combination of automated persistence and broad configuration changes represents a high-risk profile.
Capability Assessment
Purpose & Capability
Name/description (multi‑agent orchestration) match the included assets: agent templates, workspace files, watcher scripts and setup scripts. Creating agent workspaces, task directories, and a watcher is coherent for this purpose. However, the skill does not declare any required credentials or environment variables despite referencing provider models (openai-codex/gpt-5.4, OAuth) and including scripts that may call network tools (clawhub). That omission is disproportionate to the stated model/provider usage.
Instruction Scope
SKILL.md explicitly instructs the agent to run a detection/install flow and to execute bash <SKILL_DIR>/scripts/setup.sh automatically. The setup writes symlinks, copies templates into ~/.openclaw/agents, creates and edits ~/.openclaw/configs/team-dispatch.json and openclaw.json (agents.list), and restarts the Gateway. These instructions give the agent broad filesystem and configuration modification powers and the discretion to restart services; they also instruct creating persistent system scheduler entries (launchd/cron). While these actions are logically related to provisioning a dispatcher, instructing an agent to perform them automatically is high‑impact and should be confirmed by a human. The SKILL.md also asks to set main.subagents.allowAgents: ["*"], which widens allowed subagent permissions.
Install Mechanism
There is no formal install spec in registry metadata (instruction-only), but the repository includes many scripts (setup.sh, watch.sh, watch.py, publish-clawhub.mjs) and assets (launchd plists). Running setup.sh will copy files into user home directories and create persistent scheduler entries. Because there is no registry install step, the potentially dangerous operations are performed by these included scripts when executed — inspect them before running. The install sources are local (in-repo), not external downloads.
Credentials
The skill declares no required env vars or primary credential, yet SKILL.md configures models (openai-codex/gpt-5.4, oauth) and fallback providers and mentions running clawhub (which requires auth). The watcher and publish script could make outbound calls. Not declaring needed credentials is a mismatch: an operator will likely need provider credentials and gateway access for the provided functionality. Additionally, the skill writes configuration that may include model/provider fields into openclaw.json without documenting where provider secrets should come from.
Persistence & Privilege
The setup flow writes to ~/.openclaw (skills symlink, agents, configs), edits the platform-wide openclaw.json agents.list (ensuring main exists and setting main.subagents.allowAgents: ["*"]) and restarts the Gateway. It also installs scheduler artifacts (launchd plist / watcher) and creates sessions directories. Those are persistent, platform‑wide changes and broaden the dispatcher/main agent's authority. While some persistence is expected for a dispatcher skill, changing agents.list and enabling '*' for subagents plus installing KeepAlive watchers increases the blast radius and should be explicitly authorized by the human operator.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install team-dispatch - After installation, invoke the skill by name or use
/team-dispatch - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.8
Add shield security audit agent; Enhanced watcher with detailed alerts; Change default interval to 300s
v1.0.7
Fix setup.sh set -e exit bug; ClawHub publish workaround; local publish flow docs.
v1.0.6
Daily summary cron, configurable periodic tasks, English config cleanup, launchd plist rename, system scheduler preferred by default, model/version defaults update.
v1.0.5
v1.0.5: Fix Clawhub packaging filters by storing macOS LaunchAgent plist as template assets/launchd/team-dispatch.watch.plist.xml and rendering it to ~/Library/LaunchAgents/ at install time; store Windows watcher script as assets/windows/watch-install.ps1.txt (copy+rename to .ps1 before running).
v1.0.4
v1.0.4: watcher assets moved to assets/ (launchd plist + Windows ps1) to avoid missing files in packages; default watcher backend=openclaw-cron (user override supported) with merged config defaults; script safety (no eval, safer purge) + setup version output from config; verify checks required assets.
v1.0.3
Fix macOS launchd watcher install by rendering an absolute-path LaunchAgent plist before bootstrap; avoid Bootstrap failed: 5 Input/output error when plist paths use ~.
v1.0.1
1.0.1: version bump for ClawHub publish
v1.0.0
1.0.0: initial public release + docs
Metadata
Frequently Asked Questions
What is Team Dispatch?
Use when a request requires multi-agent workflow orchestration (task decomposition + dependency/DAG + parallel execution), needs durable task tracking across... It is an AI Agent Skill for Claude Code / OpenClaw, with 526 downloads so far.
How do I install Team Dispatch?
Run "/install team-dispatch" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Team Dispatch free?
Yes, Team Dispatch is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Team Dispatch support?
Team Dispatch is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Team Dispatch?
It is built and maintained by vvusu (@vvusu); the current version is v1.0.8.
More Skills