多Agent团队编排-运营版
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· 31·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/description (multi-agent orchestration) matches the SKILL.md and reference files: role definitions, task lifecycles, handoffs, and review workflows. There are no unexpected required binaries, env vars, or config paths that would be inappropriate for the described purpose.
Instruction Scope
The instructions assume standard agent platform capabilities: spawning/sending sessions, reading/writing shared directories (e.g., /shared/, /workspace/), and commenting on task state. These behaviors are coherent with orchestration, but they do assume the skill is allowed write/read access to shared artifact and workspace locations—verify your platform isolation and permissions before use.
Install Mechanism
No install spec or code is present (instruction-only). Nothing is downloaded or written to disk by the skill itself, which minimizes install-time risk.
Credentials
The skill requires no environment variables, credentials, or external config paths. References to credentials appear only as part of procedural guidance (e.g., escalate when an agent requests credentials), not as required inputs to the skill.
Persistence & Privilege
always is false and model invocation is not disabled (normal defaults). The skill does not request permanent presence or modify other skills' configs; it is a documentation/playbook resource for orchestrators.
Assessment
This is a documentation-only playbook and appears coherent with its stated purpose. Before installing/using it, confirm that your agent platform provides proper isolation and access controls for the shared directories it recommends (e.g., /shared/, /workspace/). Specifically: (1) ensure agents that write to /shared/ cannot access secrets or other sensitive system areas unintentionally; (2) verify spawn/send APIs (sessions_spawn/sessions_send) are restricted so only trusted agents can be started or interrupted; and (3) if you plan to automate escalation that supplies credentials, implement human gating or secure secret management rather than placing secrets in shared files. If those platform controls are in place, this skill is low-risk and appropriate for orchestrating multi-agent workflows.Like a lobster shell, security has layers — review code before you run it.
latestvk975k974c19tycrc2y7tz7jxmd845vv9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.