Subagent Orchestration

Orchestrate OpenClaw subagents effectively. Covers all three agent types (Worker, Researcher, Council) with correct spawning patterns, sandbox constraints, t...

This skill appears to do what it says (orchestrate subagents), but exercise caution before installing and using it: - Do not paste secrets or private conversation history into the task parameter or inline context; prefer sanitized summaries. - Treat any subagent that can exec and read/write files as high privilege; run orchestration experiments in an isolated account or ephemeral environment first. - Only grant web/tool access (toolsAllow) to Researcher subagents when absolutely necessary; restrict which models or endpoints they can call. - Verify the provenance of companion skills and referenced GitHub repos (README points to 'wahajahmed010' while the registry owner differs). Clone and inspect those repos before installing. - Review and limit config defaults (runTimeoutSeconds, maxConcurrent) to reduce blast radius, and prefer lightContext:true as recommended. If you want, I can extract the exact lines that instruct pasting full context or summarize what would be exposed by following the guide step-by-step.

Type: OpenClaw Skill Name: subagent-orchestration Version: 1.3.0 The subagent-orchestration skill provides documentation and templates for managing OpenClaw subagents, focusing on Researcher, Worker, and Council patterns. It includes guidance on using the sessions_spawn tool, managing timeouts, and configuring tool permissions (toolsAllow). The content is strictly educational and operational, aimed at improving agent reliability and avoiding common failure modes like context overflow or gateway timeouts, with no evidence of malicious intent, data exfiltration, or unauthorized execution.