ClawHub

Multi Agent Orchestrator

v1.0.0

Design, build, and manage multi-agent teams that turn a solo operator into a 1000-person organization. Covers team role design (CEO/PM/Engineer/Analyst/Write...

⭐ 0· 163·0 current·0 all-time
by@miio-jinglin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
ℹ
Purpose & Capability
The name and description (design/build/manage multi-agent teams) match the SKILL.md and reference files. The instructions reference platform CLIs and features (e.g., OpenClaw sessions_send, cron, shared filesystem) but the registry metadata declares no required binaries — this is plausible for an instruction-only, platform-agnostic guide, but users should note that running the examples in practice will require platform tooling (OpenClaw/cron/etc.).
ℹ
Instruction Scope
The SKILL.md stays on-topic (team design, communication patterns, task flows). It instructs agents to read/write shared workspace files, create AGENTS.md, set up cron heartbeats, and use messaging APIs. Those actions are expected for orchestration, but they do involve reading/writing files in a shared workspace; if that workspace contains secrets or system files, agents could access them — the skill does not instruct reading unrelated system files or exfiltrating data to external endpoints.
✓
Install Mechanism
No install spec and no code files are provided, so nothing will be written to disk by the skill itself. This is the lowest-risk form for skills and is coherent for a documentation/instructions package.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths. That aligns with being an instruction-only orchestration guide. There are no unexplained requests for secrets or unrelated service credentials.
✓
Persistence & Privilege
always is false and disable-model-invocation is false (normal). The skill does not request persistent or elevated privileges; it does instruct setting up recurring jobs (cron) and shared directories at the user's discretion, which is normal for orchestration workflows.
Assessment
This skill is an instruction-only playbook for running multi-agent teams and appears coherent with that purpose. Before using it: (1) Ensure the shared workspace you point agents at does not contain secrets or system files — agents will read/write files there. (2) If you plan to run the examples, install and secure any platform tooling referenced (OpenClaw CLI, cron) — the skill doesn't declare those binaries but uses them. (3) Be careful when giving agents network or cloud access (the templates assume data collection and external actions); grant the minimal privileges needed. (4) Because the skill is autonomous-invocable by default, review any automation triggers you enable so agents cannot perform unexpected actions without human oversight. If you want a lower-risk test, run the templates in an isolated workspace or staging environment first.

Like a lobster shell, security has layers — review code before you run it.

latestvk9784yd8k99n55p66hgjbfr5ss83hyndmulti-agentvk9784yd8k99n55p66hgjbfr5ss83hyndorchestrationvk9784yd8k99n55p66hgjbfr5ss83hyndteamvk9784yd8k99n55p66hgjbfr5ss83hynd

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments