Agent Team Orchestration.Bak
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· 89·0 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (multi-agent orchestration) matches the SKILL.md and reference files: they describe roles, lifecycles, handoffs, shared artifact paths, and spawn/send primitives. There are no unrelated required binaries, env vars, or config paths that would be disproportionate to orchestration.
Instruction Scope
Runtime instructions focus on creating tasks, spawning/sending agents, writing and verifying artifacts in shared directories, and comment conventions. The instructions reference platform primitives (sessions_send, spawn) and filesystem paths (e.g., /shared/, /workspace/) in ways that are consistent with orchestration and do not instruct collection or exfiltration of unrelated data.
Install Mechanism
There is no install spec and no code to write to disk (instruction-only skill). This minimizes installation risk — nothing is downloaded or executed by the skill itself.
Credentials
The skill declares no required environment variables, credentials, or config paths. The references note that agents may need credentials as part of normal escalation, but the skill itself does not request or require secrets.
Persistence & Privilege
Flags show always: false and no special privileges. The skill does not request persistent presence or to modify other skills or system-wide settings. Autonomous invocation is allowed by default on the platform, but nothing in the skill adds unusual privileges.
Assessment
This skill appears coherent and appropriate for coordinating multi-agent workflows. Before installing, verify your agent platform enforces workspace isolation and access controls for the shared directories the playbook relies on (/shared/, /workspace/). Specifically: (1) restrict write/read permissions so agents cannot leak secrets or sensitive files into shared artifacts; (2) confirm sessions_send/spawn actions are constrained to authorized agent sessions; (3) avoid storing credentials or production secrets in /shared/; (4) start with a small pilot (2–3 tasks) to validate the orchestration rules and logging; and (5) monitor agent comments, artifact paths, and task transitions until you are comfortable with automated behavior. These operational controls will keep the coherent guidance in this skill from producing unintended data exposure.Like a lobster shell, security has layers — review code before you run it.
latestvk972vgqseqngm04vbgrf32ec2983afk2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.