multi-agents-orchestration
v1.0.0定义多 Agent 团队两种核心协作模式：后台 spawn 实现统一调度与汇总，Discord @mention 实现角色外显与公开协作。
⭐ 0· 210·0 current·0 all-time
byChaojie Chen@cchaojiejes
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 match the SKILL.md content: it documents multi‑agent orchestration modes, configuration files, and operational steps. All requested concepts (spawn, discord binding, workspaces) are relevant to the stated purpose.
Instruction Scope
The instructions stay within the stated scope: they show how to register agents, spawn subagents, restart the gateway, and optionally expose agents as Discord bots. The SKILL.md references local OpenClaw config files and example Discord token fields only as part of the configuration process and does not instruct the agent to read unrelated system secrets or exfiltrate data.
Install Mechanism
There is no install spec and no code files. The skill is instruction-only, so it does not write code to disk or download external packages.
Credentials
The skill itself declares no required env vars, but the examples show storing Discord BOT_TOKEN and configuring workspaces/openclaw.json. Supplying Discord tokens or using wildcard subagents (e.g., subagents.allowAgents: ["*"]) is expected for Discord integration but increases privilege surface and should be limited and stored securely.
Persistence & Privilege
always:false and no install means the skill does not force permanent inclusion or modify other skills' configs. It instructs the user to restart the OpenClaw gateway for config changes, which is normal operational behavior.
Assessment
This skill is a documentation/configuration guide — it does what it says. Before applying examples: (1) avoid storing Discord BOT_TOKEN or other secrets in world-readable files; prefer secure secret storage and least-privilege bot tokens (narrow scopes, limited guilds/channels). (2) Don't use overly-broad allowances like subagents.allowAgents: ["*"] unless you understand the risk; restrict which agents can be spawned. (3) When exposing agents to Discord, review channel permissions and rate limits to prevent accidental public disclosure or bot loops (Bot-Bot @mention). (4) Test changes in a safe environment before applying to production gateway instances. If you need tighter assurance, ask the skill author for provenance or an explicit change log — this file is instructional only and contains no executable code.Like a lobster shell, security has layers — review code before you run it.
latestvk970cbm5rjaba1ry0hgz219jp982n347
License
MIT-0
Free to use, modify, and redistribute. No attribution required.