Agent Team Orchestration Local Backup
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· 63·0 current·0 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 and description (multi-agent orchestration, roles, handoffs, review workflows) match the SKILL.md content. There are no unexpected required binaries, environment variables, or config paths outside the described team orchestration domain.
Instruction Scope
The instructions direct agents and the orchestrator to create/read/write shared files under /shared/ and per-agent workspaces, to spawn/send sessions (sessions_spawn / sessions_send), and to verify artifact paths. These actions are expected for a team orchestration skill, but they imply broad read/write access to shared directories and the ability to interrupt active sessions. The playbook also recommends overwriting artifacts in place (no v2 copies), which can cause accidental data loss if not managed. There are no instructions to call external endpoints or to collect unrelated system secrets.
Install Mechanism
Instruction-only skill with no install spec and no code files. This is the lowest-risk install profile — nothing gets written to disk by an installer as part of this skill bundle.
Credentials
The skill declares no required environment variables, no primary credential, and no config paths. References in the text to 'missing access or credentials' are procedural (when to escalate) and do not translate into the skill demanding secrets or unrelated credentials.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent platform privileges or configuration changes to other skills. Autonomous invocation is allowed by default (platform behavior) but this skill does not itself grant elevated privileges.
Assessment
This playbook appears internally consistent and safe as an instruction-only orchestration guide. Before installing/use: (1) verify your agent platform enforces workspace isolation and access controls for /shared/ and per-agent workspaces so sensitive data isn't exposed; (2) test the workflow with a small non-sensitive project to validate artifact paths, overwrite behavior, and session spawn/send semantics; (3) configure backups or versioning if you don't want artifacts overwritten in place; (4) be aware sessions_send can interrupt active agents — use it only for urgent cases; and (5) ensure humans retain control of escalation and credential access rather than embedding secrets in shared directories. If you want additional assurance, provide platform-specific details (how /shared/ maps to storage, permission model) so this guidance can be tailored further.Like a lobster shell, security has layers — review code before you run it.
latestvk9762evhrc1bv4yav5ngtyc4ad83kzqd
License
MIT-0
Free to use, modify, and redistribute. No attribution required.