SKILLEMALL.ai

BC multi-agent-intercom

Enables peer-to-peer cross-communication between isolated OpenClaw agents. Resolves the limitation of `sessions_send` which cannot cross agent boundaries. 100% Zero-Intrusive, safe, compliant, with zero console popups and robust multiline support.

ClawHub Agent Skills author: zhangxue1985122219 v1.1.6 MIT-0 5 files body ≈ 844 tokens Open the sourceclawhub.ai analyzed 3 d ago

As a process C 61/100 · Has gaps — weak spots: result and completion, when it triggers, running it twice

ProcedureAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
89/100
safety, quality, tests
Safety 60%
99
Quality 40%
73
Run on models
none yet
Process rating
C
61/100
Has gaps
Result and completion w 14
0
Progress reporting w 2
0
When it triggers w 12
20
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • low Dangerous commands cmd-background-process scripts/intercom.py:112
    Starts a background / autostarted process
    preexec_fn=os.setsid,

Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "when"
  • note frontmatter-key unknown frontmatter key "examples"

Process rating: all ten parameters 61/100

  • 0Result and completion. Does not say what the result is
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 8 mutating operations with no state check
  • 60Tools and files. Uses tools (bash, python) that frontmatter does not declare
  • 70Inputs and preconditions. Inputs and preconditions are listed
  • 100Steps. 11 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 844 tokens
  • low The response is described with custom markup (3 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • +1No license
  • +2Single-language instructions
  • +3Description length 247: enough signal without eating the budget
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 11 items
  • +4Has examples (3 code blocks)
  • +3All 1 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 73.

External checks

ClawHub: suspicious
This skill transparently enables local agents to message each other, but it gives that channel persistent, automatic influence over other agents without clear sender verification or approval controls.
LLM: suspicious (high) · VirusTotal: · 29 May 2026