Agent Team Orchestration

Build and run multi-agent content production teams on OpenClaw with single-repo architecture, symlink-based file sharing, role-specialized AGENTS.md, and aut...

This package appears internally consistent and implements what it claims: a local, symlink-based multi-agent pipeline. Before using it: (1) read the setup script (scripts/setup-team.sh) to confirm paths and behavior (it only creates dirs, symlinks, and TOOLS.md); (2) back up ~./openclaw/openclaw.json before modifying it and only add trusted agent IDs to subagents.allowAgents; (3) avoid placing secrets or credentials into AGENTS.md, OUTPUT/, or KNOWLEDGE/ (the docs recommend storing architecture info in AGENTS.md so it is auto-loaded — that increases exposure to any agent session that loads it); (4) consider filesystem permissions for the created workspaces so only intended agents/processes can read/write them; (5) run the script in a test environment first to verify behavior. If you want a deeper review, provide your openclaw.json and any AGENTS.md templates you plan to use (redact secrets) so I can check for accidental leakage of sensitive data.

Type: OpenClaw Skill Name: openclaw-agent-team-orchestration Version: 3.0.0 The skill bundle provides a comprehensive framework for multi-agent orchestration using a shared-filesystem architecture. The included setup script (scripts/setup-team.sh) performs standard workspace initialization and symlink creation within the ~/.openclaw directory, which is necessary for the described single-repo design. The documentation and instructions in SKILL.md and the references/ directory are transparent, well-documented, and strictly aligned with the stated purpose of content production and quality control without any indicators of malicious intent or data exfiltration.