Agent Team Orchestration
v1.0.0Orchestrate 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.
⭐ 49· 17.6k·210 current·227 all-time
byarminn@arminnaimi
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (team orchestration) align with the content: role definitions, task lifecycle, handoffs, reviews, and file conventions. No unexpected credentials, binaries, or external services are requested.
Instruction Scope
SKILL.md and reference files stick to orchestration concerns (spawning/sending sessions, shared artifact paths, state transitions, escalation). The instructions reference platform primitives (spawn, sessions_send) and shared file paths (/shared, /workspace) which are appropriate for coordination. They do not instruct reading arbitrary host files, exfiltrating data, or contacting external endpoints.
Install Mechanism
This is an instruction-only skill with no install spec and no code files, so nothing is written to disk or fetched during install. Low install risk.
Credentials
No environment variables, credentials, or config paths are required. The docs do mention 'missing access or credentials' as a blocker to escalate, which is a reasonable run-time procedure rather than a demand for secrets.
Persistence & Privilege
The skill is not always-included (always: false). disable-model-invocation is false (agent may invoke autonomously), which is the platform default and reasonable for an orchestration skill. The skill does not request modification of other skills or system-level config.
Assessment
This playbook appears coherent and appropriate for orchestrating agent teams, but before installing consider: (1) Confirm how the platform implements /shared and /workspace — ensure those are sandboxed and don't map to sensitive host paths. (2) Enable artifact versioning or backups (the playbook suggests overwriting in place, which risks data loss). (3) Verify session spawn/send behavior and logging to ensure no unintended external transmission of artifacts. (4) Enforce least privilege for agents (don't give orchestrator or builders more host access than needed). (5) If your workflows require credentials (APIs, infra), ensure those secrets are stored and accessed via secure platform-managed vaults — the skill itself does not request or justify direct credential access. If you want a tighter assessment, provide the platform's mapping of /shared and the exact spawn/send APIs so I can check for any platform-level leakage vectors.Like a lobster shell, security has layers — review code before you run it.
latestvk973e9nvd3xtzn2m3tn5ert5cd811h1f
License
MIT-0
Free to use, modify, and redistribute. No attribution required.