distributed-mesh

Name: distributed-mesh
Availability: InStock
Author: barichter

Configure distributed mesh topologies and synchronize state across machines using git and mesh.json.

Updated Apr 12, 2026

Search Tags:#git synchronization #distributed coordination #squad communication #mesh configuration #cross-machine coordination

Ready to run

npx skills add https://github.com/barichter/squad --skill distributed-mesh-barichter

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires sync-mesh.sh, sync-mesh.ps1, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

This Skill enables cross-machine squad coordination, facilitating communication between squads across different machines, organizations, and file systems.

Core Features & Use Cases

Mesh Configuration: Automatically generates mesh.json to configure distributed mesh topology.
Synchronization Scripts: Copies sync scripts for local and remote state materialization.
State Repository Initialization: Optionally initializes a shared state repository for Zone 2.
Decision Documentation: Creates a decision entry documenting the mesh configuration.
Use Case: For organizations with squads on multiple machines, this Skill helps to maintain synchronization and visibility into remote squad states.

Quick Start

Run sync-mesh.sh before agents start to synchronize remote 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 cross-machine squad communication using git?▼

You can coordinate cross-machine squad communication by generating a mesh.json file and using sync-mesh scripts to synchronize distributed state across machines via a shared git repository.

What is mesh.json used for in distributed mesh configuration?▼

Mesh.json is used to configure distributed mesh topology, defining the coordination state and communication structure between squads operating on different machines and file systems.

How do I synchronize remote squad state before agents start?▼

Run the sync-mesh.sh script before agents start to synchronize remote state and materialize the local distributed mesh configuration from the shared git repository.

Can I use sync-mesh.ps1 for cross-machine coordination on Windows?▼

Yes, sync-mesh.ps1 is provided as a synchronization script alongside sync-mesh.sh, enabling local and remote state materialization for cross-machine coordination on Windows environments.

When do I need distributed mesh topology for squad communication?▼

You need distributed mesh topology when managing multi-machine or cross-organizational collaboration scenarios, requiring visibility and synchronization into remote squad states across different file systems.

Does distributed-mesh require a shared state repository for git synchronization?▼

A shared state repository for Zone 2 is optional but recommended, as the Skill can initialize it to maintain synchronization and visibility into remote squad states via git.