Mob Communication

Coordinate peer-to-peer messaging and lifecycle events within a collaborative mob.

19|5|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/lukacf/meerkat --skill mob-communication
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Mob Communication
Source: https://github.com/lukacf/meerkat/tree/main/meerkat/skills/mob-communication
Command: npx skills add https://github.com/lukacf/meerkat --skill mob-communication

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mob communication enables Meerkat agents to reliably coordinate with peers in a collaborative mob using a defined messaging protocol.

Core Features & Use Cases

  • Discover peers via peers() to identify other meerkats you are wired to.
  • Use peer_message for normal collaboration.
  • Use peer_request only when you want a structured ask (intent + JSON params) and expect a later correlated peer_response.
  • Respond to incoming PeerRequests with PeerResponse.
  • You will receive notifications when peers are added (mob.peer_added) or removed (mob.peer_retired / mob.peer_unwired). These updates are informational — do not reply to them. Use peers() to inspect current connectivity on demand.
  • If a delegated helper fails during startup before it can reliably report for itself, wired peers may receive mob.kickoff_failed or mob.kickoff_cancelled. These are lifecycle notices, not work results.

Quick Start

Send a test message to your current mob using peer_message after discovering peers().

Frequently Asked Questions about Mob Communication

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate peer-to-peer communication in a multi-agent mob?

To coordinate structured peer communication, use peer_request to send an intent with JSON parameters and expect a correlated peer_response later, distinguishing it from standard peer_message collaboration.

What is the difference between peer_message and peer_request for agent collaboration?

To coordinate structured peer communication, use peer_request to send an intent with JSON parameters and expect a correlated peer_response later, distinguishing it from standard peer_message collaboration.

Do I need to reply to mob lifecycle notifications like peer_added or peer_retired?

Mob lifecycle events like mob.kickoff_failed and mob.kickoff_cancelled are informational notices indicating a delegated helper failed during startup before reliably reporting, not actual work results.

Why does a peer receive a mob.kickoff_failed event during multi-agent workflows?

Mob lifecycle events like mob.kickoff_failed and mob.kickoff_cancelled are informational notices indicating a delegated helper failed during startup before reliably reporting, not actual work results.

Can I inspect current peer connectivity on demand in a collaborative mob?

You can respond to incoming PeerRequests with a PeerResponse to provide correlated structured results back to the requesting peer within the collaborative mob workflow.

How do I respond to a structured peer request in a Meerkat mob?

You can respond to incoming PeerRequests with a PeerResponse to provide correlated structured results back to the requesting peer within the collaborative mob workflow.