distributed-mesh

Coordinate remote squad state into local files via mesh.json topology.

Updated Apr 3, 2026

Search Tags:#git #team collaboration #multi-machine #remote state #distributed coordination #mesh sync

Ready to run

npx skills add https://github.com/sachinnair90/gitgloss --skill distributed-mesh-sachinnair90

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, curl.

What problem does it solve?

This Skill solves the problem of coordinating squad work when team members or agents live on different machines, so remote context can still appear locally before the agent reads it.

Core Features & Use Cases

Topology capture: Collects squad names, zones, and connection details into a single mesh configuration.
Remote materialization: Copies bundled sync scripts and uses them to pull or fetch remote squad state onto the local filesystem.
Mesh initialization: Optionally scaffolds a shared state repository for Zone 2 collaboration and records the setup in a decision entry.
Use case: A team with local squads, shared-org Git remotes, and external partner contracts can standardize how every agent sees current state.

Quick Start

Use the distributed-mesh skill to gather the participating squads, write the mesh configuration, copy the sync scripts, and create the 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 sync git state across multiple machines for distributed team collaboration?▼

To coordinate remote squad state across machines, you define a mesh.json topology file mapping participating squads and zones, then use bundled sync scripts to pull remote context directly onto your local filesystem.

How does mesh sync work for agents reading distributed context from local files?▼

Mesh sync works by copying bundled scripts to your machine, which fetch and materialize remote squad state so agents can read distributed context from local files without direct remote queries.

Do I need jq and curl to coordinate remote squad state across machines?▼

Yes, you need jq, git, and curl installed to run the bundled sync scripts that fetch remote squad state and parse the mesh.json topology configuration for distributed coordination.

Can I use distributed-mesh for multi-machine collaboration with external partner organizations?▼

Yes, this supports local, remote-trusted, and remote-opaque collaboration setups, standardizing how agents see current state across laptops, CI runners, cloud VMs, and partner organizations.

What is the best way to initialize a shared state repository for multi-machine git coordination?▼

The best way is using the mesh initialization feature, which optionally scaffolds the shared state repository for Zone 2 collaboration and records the setup configuration in a decision entry.