agent-mesh

Coordinate agents via shared filesystem and pub/sub events.

1|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/MCERQUA/jam-skills --skill agent-mesh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-mesh
Source: https://github.com/MCERQUA/jam-skills/tree/main/agent-mesh
Command: npx skills add https://github.com/MCERQUA/jam-skills --skill agent-mesh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill enables seamless coordination and communication between different agents within the JamBot office-of-agents, ensuring efficient workflow and task management.

Core Features & Use Cases

  • Agent Coordination: Send, receive, and acknowledge messages between agents.
  • Bootstrap Sequence: Automatically bootstrap into the mesh at session start.
  • File Management: Manage files and messages using the mesh filesystem.
  • Use Case: Imagine you need to coordinate a task with another agent. Use the agent-mesh skill to send a message, receive a response, and acknowledge its completion.

Quick Start

Start the mesh coordination process with the command '/mesh-on'.

Frequently Asked Questions about agent-mesh

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

FAQPage Schema
How do I coordinate background jobs between multiple agents using a shared filesystem?

Agent coordination across a shared filesystem is managed by sending, receiving, and acknowledging messages between agents. This skill utilizes directories like /mnt/agent-mesh/ to manage tasks, background jobs, and pipelines for seamless workflow.

Can I use pub/sub events for task management across different agents?

Yes, pub/sub events are supported for task management. The mesh communication mechanism allows agents to publish and subscribe to events, handling background jobs and pipeline coordination automatically via the shared filesystem.

What is the best way to bootstrap an agent into a mesh communication network at session start?

The best way to bootstrap into the mesh at session start is using the '/mesh-on' command. This initializes the agent coordination process, connecting it to the shared filesystem for file and message management.

Do I need Python to manage background jobs and agent coordination?

Yes, Python is required to manage background jobs and agent coordination. The skill depends on Python to execute scripts that handle task management, pub/sub events, and mesh communication across the shared filesystem.

How does file management work for agents communicating through a shared mesh?

File management for mesh communication works by utilizing a shared filesystem located at /mnt/agent-mesh/ or /mesh/agent-desk/. Agents read and write files to this central location to send, receive, and acknowledge messages and coordinate tasks.

What are the limitations of using a shared filesystem for agent coordination?

Agent coordination via a shared filesystem requires all participating agents to have access to the exact same mounted directory path. Without this shared environment at /mnt/agent-mesh/, inter-agent messaging, pub/sub events, and task management will not function.