distributed-mesh

Configure distributed squads and synchronize Git-based state across machines and zones.

3|Updated Mar 15, 2026

Search Tags:#git #collaboration #distributed systems #state synchronization #squads #mesh networking

Ready to run

npx skills add https://github.com/bradygaster/docx-mcp-server --skill distributed-mesh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/bradygaster/docx-mcp-server/tree/main/.squad/templates/skills/distributed-mesh
Command: npx skills add https://github.com/bradygaster/docx-mcp-server --skill distributed-mesh

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enables squads to collaborate effectively even when their members are distributed across different machines, networks, or organizations, by establishing a clear communication and state synchronization protocol.

Core Features & Use Cases

Mesh Configuration: Define how squads connect and share state across different zones (local, remote-trusted, remote-opaque).
State Synchronization: Provides scripts to pull remote squad state and push local updates, ensuring all agents work with the latest information.
Use Case: A development team spread across multiple laptops and a CI server can use this Skill to ensure all agents have access to the same configuration files and build artifacts, preventing inconsistencies.

Quick Start

Use the distributed-mesh skill to set up a new mesh configuration by answering a few questions about your squads and their zones.

Frequently Asked Questions about distributed-mesh

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

FAQPage Schema

How do I synchronize state across distributed machines using Git?▼

State synchronization across distributed machines is managed by configuring a mesh that pulls remote squad state and pushes local updates using Git for trusted remotes and HTTP fetches for opaque remotes.

What is a distributed mesh for agent collaboration?▼

A distributed mesh for agent collaboration is a network configuration that enables squads spread across different machines and organizations to share state and coordinate tasks by materializing remote files locally before execution.

How do I set up cross-machine squad coordination for agents on different networks?▼

You set up cross-machine squad coordination by configuring a distributed mesh that defines how squads connect across local, remote-trusted, and remote-opaque zones, ensuring all agents access the same configuration files.

Can I use this mesh networking approach for squads spread across different organizations?▼

Yes, you can coordinate squads across different organizations by defining remote-trusted zones for Git-based state synchronization and remote-opaque zones for HTTP fetches, allowing cross-machine agent collaboration without direct network access.

How does state synchronization work with opaque remotes that I cannot fully trust?▼

For opaque remotes, state synchronization uses HTTP fetches to pull remote squad state rather than Git, allowing agents to materialize files locally for execution without exposing internal repositories.