Multi-Agent CN
v1.2.0通用多Agent调度系统（中文版）：将主Agent变为纯调度员，所有任务通过 sessions_spawn 委派给5个持久化子Agent。支持轮询调度、先回复再派遣协议、 sessionKey固定复用。用户可自定义调度员角色和子Agent名称/人设。
⭐ 24· 4.3k·43 current·44 all-time
byCLOUD BOY@be1human
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description describe a dispatcher that delegates work to five persistent sub-agents. The SKILL.md contains only delegation rules (sessionKey reuse, round-robin, spawn format) and does not request unrelated binaries, environment variables, or external services — this is coherent with the declared purpose.
Instruction Scope
Instructions constrain the main agent to be a pure scheduler (forbids exec/file I/O) and to always call sessions_spawn with specific fields. This stays within delegation scope. Note: the guide instructs the scheduler to include file paths and full contextual details in the task payloads for sub-agents; that is reasonable for delegation but means any sensitive local paths or secrets you include in tasks could be exposed to child agents. The skill itself does not read files or request system state.
Install Mechanism
Instruction-only skill with no install spec and no code files. Nothing is written to disk or downloaded during install — lowest-risk installation model.
Credentials
No environment variables, credentials, or config paths are required. The lack of requested secrets is proportionate to the described function.
Persistence & Privilege
always is false and the skill is user-invocable. It does not request persistent system-wide privileges or modify other skills. Autonomous invocation is allowed by platform default, which is expected for a skill that spawns sessions.
Assessment
This skill appears to do exactly what it says: act as a dispatcher that spawns five persistent sub-agents. Before installing, confirm you trust the platform's sessions_spawn behavior and any child agents that will receive task payloads. Do not include secrets, private keys, or sensitive filesystem paths in the 'task' field you ask the dispatcher to send to sub-agents unless you are certain those sub-agents are trustworthy. Also note the strict behavioral rules (must reply before spawning, then stop output) — understand that pattern so you don't confuse users with missing followups.Like a lobster shell, security has layers — review code before you run it.
latestvk97a4wwns8g6rb2bcnghk6eq0s810526
License
MIT-0
Free to use, modify, and redistribute. No attribution required.