distributed-mesh

Coordinate cross-machine squad state by synchronizing state files via git mesh transport.

Updated Mar 18, 2022
One-click install
npx skills add https://github.com/mpaulosky/dotfiles --skill distributed-mesh-mpaulosky
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/mpaulosky/dotfiles/tree/main/.copilot/skills/distributed-mesh
Command: npx skills add https://github.com/mpaulosky/dotfiles --skill distributed-mesh-mpaulosky

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a repeatable, auditable pattern to coordinate cross-machine squads by using git as the transport for mesh state and decision logs, reducing manual handoffs and drift.

Core Features & Use Cases

  • Supports local, remote-trusted, and remote-opaque zones to distribute state and intent across machines.
  • Generates a mesh.json configuration from user-provided topology and copies bundled sync scripts to initialize project state.
  • Documents the mesh setup by creating a decision entry in .squad/decisions/inbox for team awareness.

Quick Start

Configure the mesh by collecting squad topology, generating mesh.json, copying the bundled sync scripts, optional Zone 2 init, and writing the mesh setup decision.

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 remote machines using git?

Git works as a mesh transport to synchronize squad state files across local, remote-trusted, and remote-opaque zones. It reduces manual handoffs and drift by providing a repeatable, auditable pattern for cross-machine coordination.

What is a mesh.json configuration file used for in distributed squads?

A mesh.json configuration file defines the squad topology for cross-machine coordination, mapping local, remote-trusted, and remote-opaque zones. It is generated from user-provided topology to establish the state synchronization mesh.

How do I initialize a mesh state repo with bundled sync scripts?

Initializing a mesh state repo involves copying the bundled sync-mesh.sh or sync-mesh.ps1 scripts into your project and running them based on your mesh.json configuration. This establishes the git transport for state synchronization across zones.

Can I coordinate squads across remote-opaque zones with this git mesh approach?

Yes, coordinating squads across remote-opaque zones is fully supported alongside local and remote-trusted zones. The mesh.json configuration and bundled sync scripts manage state synchronization across all three zone types using git transport.

Does cross-machine squad coordination require a specific schema or just the sync scripts?

Cross-machine squad coordination requires both a mesh.json schema to define topology and the bundled sync scripts to execute synchronization. The schema configures zones while the scripts initialize and maintain the mesh state repo.

When should I not use git as a transport layer for synchronizing distributed state?

Git as a transport for distributed state is not ideal for real-time synchronization requiring low latency or high-frequency updates. It is designed for auditable, repeatable squad coordination rather than immediate state reflection across machines.