2.5k
GitHub Stars
6
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill team-dispatch- _meta.json277 B
- CHANGELOG.md2.6 KB
- config.json3.1 KB
- README.md7.2 KB
- README.zh.md6.8 KB
- SKILL.md17.8 KB
Overview
This skill orchestrates multi-agent workflows by automatically decomposing requests into DAGs, dispatching tasks to subagents, and tracking durable task state until delivery. It handles parallel execution, retries, fallbacks, and completion notifications to ensure end-to-end delivery. The skill includes installation and environment checks to prepare agent workspaces and templates.
How this skill works
It inspects the incoming request to determine complexity and selects an appropriate decomposition template (development, research, full-stack, analysis, or content). Tasks are modeled as nodes in a DAG with explicit dependencies; ready nodes are dispatched via sessions_spawn and tracked in durable JSON project files. On every subagent completion event the skill runs an immediate scheduling loop: mark task done, inject upstream results into downstream prompts, dispatch newly ready tasks, handle retries/fallbacks, and archive when all tasks finish.
When to use it
- When a request requires coordinated work across multiple agents with dependencies or parallel branches.
- When you need durable task tracking that survives context compaction or restarts.
- When you want automatic retries, fallback agents, or configurable onFailure behaviors.
- When you need event-driven, immediate cascade dispatch on task completion.
- When you require final delivery notification and project archiving.
Best practices
- Run the setup script and environment checks before first use to ensure workspaces, agent templates, and configs exist.
- Model tasks with clear dependencies and timeouts and set sensible retry limits and onFailure policies (block/skip/fallback/manual).
- Use checkpoints for XL projects to pause for user review instead of automatic dispatch.
- Dispatch ready parallel tasks simultaneously rather than serializing to avoid bottlenecks.
- Provide useful upstream results in task descriptions so downstream agents have context for accurate responses.
Example use cases
- Orchestrate a product → coder → tester → writer pipeline for a new feature delivery with automatic handoffs and final archive.
- Run a research → product → writer DAG to produce a market analysis report with visualizations and a final deliverable link.
- Execute a complex data analysis DAG where multiple analyses run in parallel and results are aggregated into a single report.
- Create a demo project to validate the multi-agent loop and confirm automatic archiving and notification behavior.
FAQ
The skill automatically falls back to single-agent role simulation: it keeps the DAG, spawns sessions without agentId, and injects role instructions into prompts to simulate coder/product/tester roles.
How are failures and timeouts handled?
Tasks can retry up to retryLimit, use fallback agents, enter queued state when concurrency limits hit, or follow onFailure policies (block/skip/fallback/manual) per task.
How does the scheduler react to completion events?
Every completion event triggers an immediate scheduling loop: update task state, dispatch all newly ready tasks, persist JSON, and archive/notify if the project is complete.