← Back to Skills Marketplace
73
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install multi-agent-communication
Description
Based on two core tools, sessions_spawn and sessions_send, to help users build, manage, and optimize distributed Agent systems, enabling task decomposition,...
Usage Guidance
This skill reads like an internal design/usage doc for a multi-agent orchestration API — it is coherent with that purpose, but several items need clarification before you install or enable it:
- Ask the author/platform: what platform services does this expect (Gateway RPC, SubagentRegistry, Sweeper) and what credentials/permissions are required? Right now the skill declares none, which is surprising given the described integrations.
- Watch defaults: the provided config shows agentToAgent.allow: ["*"]. If applied as-is, that allows unrestricted cross-agent communication. Require a whitelist or tighter defaults in production.
- Invisible child runs: mode="run" is described as completely invisible to the user. Confirm logging, auditing, and limits so background tasks cannot perform covert work on sensitive data.
- Attachment snapshotting: children get copies of attachments that persist independently. Ensure data retention, access controls, and deletion policies are explicit to avoid unintended data duplication/exfiltration.
- Require visibility controls: mandate thread binding or user-visible sessions for any task that touches sensitive data, and enable timeouts/limits (max depth, max children) appropriate for your environment.
- Test in isolation: run the patterns in a sandboxed environment first, and verify there are no unexpected network endpoints or external integrations being contacted.
If the maintainer can provide explicit details on required platform permissions, auditing/logging behavior, and recommended secure config (non-permissive defaults), re-evaluate; until then treat the skill as potentially risky for sensitive environments.
Capability Analysis
Type: OpenClaw Skill
Name: multi-agent-communication
Version: 1.0.0
The skill bundle is a documentation-only package providing instructions and design patterns for multi-agent communication using the 'sessions_spawn' and 'sessions_send' tools. It includes configuration references (config.md) and architectural patterns (patterns.md) for parallel processing and agent collaboration. No executable code or malicious instructions were found; the content is entirely aligned with its stated purpose of managing distributed agent systems.
Capability Assessment
Purpose & Capability
The name/description match the provided instructions: the skill documents two actions (sessions_spawn and sessions_send) and patterns for spawning and messaging Agents. However, the doc references binding to third‑party threads (Discord/Slack), a Gateway RPC, SubagentRegistry, and a Sweeper service — legitimate platform components, but the SKILL.md does not declare what platform privileges, credentials, or integrations are required for those features.
Instruction Scope
Instructions permit invisible 'run' mode child Agents (user-invisible execution) and describe copying attachments (snapshots) into child Agents' independent lifecycles. The doc also describes automatic push mechanisms (Sweeper polling every 1–8s) and thread binding. Those behaviors expand the agent's runtime footprint (background work, duplicated data, cross-agent access) and could be abused for covert processing or unintended data replication if not constrained or audited.
Install Mechanism
Instruction-only skill with no install spec and no code files — nothing is written to disk by the package itself, which minimizes installation risk.
Credentials
The skill declares no required environment variables or credentials, yet describes operations that in a real deployment typically require permissions (posting/reading from chat threads, invoking gateway RPCs, accessing registries, reading/writing shared workspaces). The references/config.md also shows a permissive default (agentToAgent.allow: ["*"]) which would allow all cross-agent communication by default — a risky default if applied in production.
Persistence & Privilege
always:false (good) and autonomous invocation is allowed (the platform default). The ability to spawn persistent 'session' Agents and to run invisible 'run' Agents increases runtime privilege and persistence within the platform; this is a legitimate capability but should be paired with auditing, visibility controls, and strict whitelists to avoid abuse.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install multi-agent-communication - After installation, invoke the skill by name or use
/multi-agent-communication - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
- Initial release of multi-agent-communication skill.
- Introduces two core tools: sessions_spawn (spawns child Agents) and sessions_send (communicates with existing Agents).
- Supports distributed task decomposition, parallel processing, and efficient inter-Agent coordination.
- Provides robust security controls: recursion depth, child process limits, and cross-Agent whitelisting.
- Enables multi-round agent-to-agent negotiation and supports both one-shot and persistent session modes.
Metadata
Frequently Asked Questions
What is Multi-Agent Communication?
Based on two core tools, sessions_spawn and sessions_send, to help users build, manage, and optimize distributed Agent systems, enabling task decomposition,... It is an AI Agent Skill for Claude Code / OpenClaw, with 73 downloads so far.
How do I install Multi-Agent Communication?
Run "/install multi-agent-communication" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Multi-Agent Communication free?
Yes, Multi-Agent Communication is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Multi-Agent Communication support?
Multi-Agent Communication is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Multi-Agent Communication?
It is built and maintained by OpenLark (@openlark); the current version is v1.0.0.
More Skills