Multi-Agent Intercom
v1.1.6Enables peer-to-peer cross-communication between isolated OpenClaw agents. Resolves the limitation of `sessions_send` which cannot cross agent boundaries. 10...
⭐ 1· 235·1 current·1 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill claims to bridge isolated OpenClaw agents and the included Python script calls the local `openclaw agent ... --message` CLI to deliver messages. Requested binaries (python, openclaw) match this purpose and no unrelated credentials or config paths are required.
Instruction Scope
SKILL.md and the script both insist the user run `setup` to print an SOP which must be manually pasted into each agent's AGENTS.md; the script does not auto-edit files. This matches the 'zero-intrusive' claim, but the manual edit step does grant agents new behavior (the SOP tells agents how/when to reply), so the user must review and approve the SOP before pasting.
Install Mechanism
No install spec — the skill is instruction-only with a bundled script. Nothing is downloaded or extracted during installation, which is low-risk.
Credentials
No environment variables or secret credentials are requested. The script only relies on finding executables on PATH (python/openclaw/powershell), which is appropriate for its stated functionality.
Persistence & Privilege
The skill is not forced-always; it does not modify other skills or system settings on its own. It runs detached background processes when sending messages (normal for this use) and exits. Autonomous invocation is allowed by default on the platform but not granted extra privileges by this skill.
Assessment
This skill is internally coherent, but review and control the manual steps before enabling it: 1) Run `python scripts/intercom.py setup` yourself and read the SOP it prints before pasting it into any AGENTS.md — the SOP changes agent behavior, so only paste it where you trust the agent. 2) Confirm the `openclaw` binary on your PATH is the legitimate OpenClaw CLI (an attacker could place a different binary named `openclaw` in PATH). 3) Be aware sends are performed by launching the local OpenClaw CLI in the background (detached), so monitor any unexpected background `openclaw agent` processes. 4) If you want extra caution, test with non-production agents/IDs first to ensure behavior matches expectations.Like a lobster shell, security has layers — review code before you run it.
latestvk9701wfgzfn2hsk4qx0rfskezs83n0s3
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🗣️ Clawdis
Binspython3, python, openclaw
Any binpython3, python