Agent Team Orchestration 1.0.0
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...
⭐ 0· 115·3 current·3 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (multi-agent orchestration) match the contents: role definitions, task lifecycle, handoffs, review workflows and workspace conventions. No unexpected binaries, env vars, or external services are required.
Instruction Scope
SKILL.md and reference files are detailed playbooks instructing agents to read/write shared directories (/shared/, /workspace/) and to spawn/send sessions. This is expected for orchestration, but the instructions assume the agent platform provides those filesystem and session primitives — confirm those capabilities and access controls before use.
Install Mechanism
No install spec and no code files — lowest-risk form (instruction-only). Nothing is downloaded or written by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. It does recommend verifying access/capabilities (e.g., browser, API access) when assigning tasks, which is appropriate and proportional.
Persistence & Privilege
always:false (normal). The playbook mandates writing artifacts and decision logs to shared storage and instructs overwriting previous versions in place — this is coherent for team workflows but carries data-retention/overwrite and information-exposure risk depending on your environment's access controls and backup/versioning policies.
Assessment
This skill is a textual playbook (no code) and appears to do what it says. Before installing/using it: 1) Verify your agent platform provides the shared/workspace directories and enforce access controls so sensitive data isn't exposed across agents. 2) Avoid allowing blind overwrites in /shared/ — enable versioning or require unique task directories to prevent data loss. 3) Limit who/which agent can read other agents' personal workspaces if that would expose secrets. 4) Start with a small pilot (2–3 tasks) to validate the conventions and permissions. If your runtime doesn't provide the sessions_spawn/sessions_send primitives or a secured shared filesystem, adapt the playbook or restrict its use.Like a lobster shell, security has layers — review code before you run it.
latestvk97fztbc7y58n0mwmmbamh3t9183b7ah
License
MIT-0
Free to use, modify, and redistribute. No attribution required.