distributed-mesh

Coordinate distributed squads across machines using git transport.

2|3|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/sytone/botnexus --skill distributed-mesh-sytone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/sytone/botnexus/tree/main/.copilot/skills/distributed-mesh
Command: npx skills add https://github.com/sytone/botnexus --skill distributed-mesh-sytone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating distributed squads across machines using git as transport to synchronize state and decisions.

Core Features & Use Cases

  • Lightweight workflow to define mesh topology, pull in consolidated state, and publish decisions.
  • Supports Zone 1 local read/write, Zone 2 remote-trusted git-backed state, and Zone 3 remote-opaque published contracts.
  • Produces a mesh.json from user answers, copies bundled sync scripts, and writes a decision entry for visibility.

Quick Start

Run through the steps to configure a distributed mesh: answer topology questions, generate mesh.json from the example, copy the bundled sync scripts into the project root, initialize the mesh state repo if Zone 2 is used, and write 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 synchronize squad state across multiple machines using git?

You synchronize squad state across machines by using git as a transport layer to coordinate distributed squads. This workflow generates a mesh.json file, copies bundled sync scripts, and writes decision entries to ensure cross-machine state visibility.

What is the best way to coordinate distributed squads across remote hosts?

The best way to coordinate distributed squads is defining a mesh topology that supports local, remote-trusted, and remote-opaque zones. This lightweight workflow pulls consolidated state and publishes decisions using git-backed synchronization.

Do I need a mesh.json template to set up cross-machine squad coordination?

Yes, you need a mesh.json template, specifically the mesh.json.example file, to set up cross-machine coordination. The Skill generates the final mesh.json from your topology answers and uses it to configure the distributed state synchronization.

How do I initialize a git-backed state repo for remote-trusted squad zones?

To initialize a git-backed state repo for remote-trusted zones, you run through the configuration steps to generate mesh.json, copy the bundled sync scripts to your project root, and then initialize the mesh state repository.

Can I use this workflow to publish decisions to remote-opaque squads?

Yes, you can use this workflow to publish decisions to remote-opaque squads by treating them as Zone 3 published contracts. The process produces a decision entry in the .squad/decisions directory to ensure distributed visibility.

Why does distributed squad coordination require copying bundled sync scripts?

Distributed squad coordination requires copying bundled sync scripts to provide the lightweight execution logic for git state synchronization. These scripts enable the mesh topology to pull consolidated state and write decision entries across different host environments.