distributed-mesh

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

Updated Apr 10, 2026

Search Tags:#automation #git #coordination #squad #state-repo #mesh.json #distributed-mesh

Ready to run

npx skills add https://github.com/chdaly/eshop --skill distributed-mesh-chdaly

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, curl, and includes scripts (resource) components.

What problem does it solve?

This skill provides a structured, repeatable pattern to coordinate squads that are distributed across multiple machines by using git as the transport for state information.

Core Features & Use Cases

Orchestrates cross-machine squad coordination by describing zones (local, remote-trusted, remote-opaque) and generating a mesh.json configuration.
Provides bundled, ready-to-copy sync scripts (bash and PowerShell) to materialize remote state locally.
Creates a governance-friendly workflow with a mesh state repository and a decision entry to track configuration.

Quick Start

Run the agent workflow to collect topology, generate mesh.json from the template, copy the bundled sync scripts, initialize the mesh state repository when needed, and publish a mesh decision entry.

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 can coordinate distributed squads across machines by using git as a state transport, generating a mesh.json configuration, and provisioning sync scripts to materialize remote state locally across local, remote-trusted, and remote-opaque zones.

What is a mesh.json configuration used for in cross-machine automation?▼

A mesh.json configuration defines the topology for cross-machine automation, describing zones like local, remote-trusted, and remote-opaque to establish a deterministic workflow for synchronizing squad state information via a git repository.

How do I set up a git state repository for distributed mesh coordination?▼

Setting up a git state repository involves collecting topology details, generating mesh.json, copying bundled bash and PowerShell sync scripts, initializing the repository when needed, and recording a mesh setup decision entry to document the configuration.

Do I need jq and curl to sync remote squad state locally?▼

Yes, you need jq, git, and curl installed to execute the bundled sync scripts, process the mesh.json configuration, and handle the underlying data transfer required to sync remote squad state to your local machine.

Does distributed-mesh work with both bash and PowerShell for state synchronization?▼

Distributed-mesh supports state synchronization across different operating systems by providing bundled, ready-to-copy sync scripts written in both bash and PowerShell to materialize remote state locally.

When should I not use a git-based mesh for cross-machine squad coordination?▼

You should avoid using a git-based mesh if your cross-machine coordination requires real-time state synchronization or if your remote-opaque zones restrict git repository access, as this approach relies on git as a deterministic state transport.