distributed-mesh

Generate mesh.json and sync scripts to coordinate squads via git.

Updated Apr 14, 2026

Search Tags:#git #distributed #coordination #squad #mesh #mesh.json #sync-scripts

Ready to run

npx skills add https://github.com/robpitcher/eShopOnWeb --skill distributed-mesh-robpitcher

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/robpitcher/eShopOnWeb/tree/main/.copilot/skills/distributed-mesh
Command: npx skills add https://github.com/robpitcher/eShopOnWeb --skill distributed-mesh-robpitcher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating work across squads that live on different machines or networks requires a reliable way to share state and decisions without a centralized runtime. This skill provides a repeatable pattern to materialize and synchronize mesh state using git as the transport.

Core Features & Use Cases

Generates mesh.json from user-provided topology (zones, squads, and connection details) using mesh.json.example as a schema.
Provides bundled sync scripts (sync-mesh.sh and sync-mesh.ps1) to initialize and refresh remote state before agents run.
Writes a mesh-state decision entry in .squad/decisions/inbox to document the configuration for team awareness.
Supports three zones (local, remote-trusted, and remote-opaque) and a deterministic workflow for state materialization.

Quick Start

Answer the topology questions and run the provided sync-mesh script to initialize and materialize the mesh state.

Frequently Asked Questions about distributed-mesh

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

FAQPage Schema

How do I coordinate distributed squads across multiple machines using git?▼

You coordinate distributed squads by materializing a mesh state with git as the transport. This involves generating a mesh.json configuration file from topology input and running bundled sync scripts to initialize and refresh state across local and remote machines.

What is a git mesh and when do I need it for state synchronization?▼

A git mesh is a repeatable pattern for sharing state and decisions across squads on different machines without a centralized runtime. You need it when squads span multiple machines or organizations and require deterministic state synchronization.

How do I set up mesh.json for squads across local and remote zones?▼

You set up mesh.json by answering topology questions that define zones, squads, and connection details. The skill uses mesh.json.example as a schema to generate the file and logs a configuration decision entry in .squad/decisions/inbox for team awareness.

Does this distributed coordination approach require a centralized runtime?▼

No, this approach does not require a centralized runtime. It uses git as the transport layer to materialize and synchronize mesh state, supporting local, remote-trusted, and remote-opaque zones directly through repository syncing.

What sync scripts are needed to initialize git mesh state across machines?▼

The required scripts are sync-mesh.sh and sync-mesh.ps1, which are bundled and ready to copy to project roots. These scripts initialize and refresh remote state before agents run, ensuring deterministic setup across the distributed mesh.

Can I use mesh.json to coordinate squads across different organizations?▼

Yes, you can coordinate squads across different organizations by defining remote-opaque zones in mesh.json. The skill handles initialization, state synchronization, and decision logging for topologies spanning local, remote-trusted, and remote-opaque environments.