distributed-mesh

Coordinate distributed squads across machines using git as transport.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/lbouriez/Squad-Templates --skill distributed-mesh-lbouriez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/lbouriez/Squad-Templates/tree/main/Nectari-Devops-Squad/.copilot/skills/distributed-mesh
Command: npx skills add https://github.com/lbouriez/Squad-Templates --skill distributed-mesh-lbouriez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, curl.

What problem does it solve?

Coordinating distributed squads across multiple machines requires a reliable, lightweight mechanism to share state without a central host. This skill defines a portable pattern for syncing squad workspaces over git so teams can collaborate across borders and runtimes.

Core Features & Use Cases

  • Zone-based mesh coordination: local, remote-trusted, and remote-opaque configurations.
  • Ready-made mesh state tooling: mesh.json, and bundled sync scripts to materialize remote state locally.
  • Lightweight decision logging for cross-machine collaboration.

Quick Start

Configure your mesh topology, generate mesh.json from your answers, copy the bundled sync scripts, initialize the state repo if required, and record a 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 without a central host?

Git-based mesh coordination uses git as a transport to synchronize squad state across machines without a central host. It defines zones and sync targets in mesh.json, then materializes remote state locally using bundled scripts.

What is a distributed mesh topology for remote squad coordination?

A distributed mesh topology for remote squad coordination connects local, remote-trusted, and remote-opaque zones using git. It allows dispersed squads to declare their zones and sync details in mesh.json, ensuring state synchronization across borders and runtimes.

How do I set up git-based state management for a distributed team?

To set up git-based state management, configure your mesh topology, generate mesh.json from your declared zones and sources, copy the bundled sync scripts, initialize the state repo, and record a decision entry to start collaborating.

Do I need to install application code to materialize remote state with git?

No, you do not need application code to materialize remote state. The skill requires only bundled scripts to materialize remote state locally, relying on git, jq, and curl as dependencies for the synchronization process.

Can I coordinate squads across remote-opaque zones using git?

Yes, you can coordinate squads across remote-opaque zones using git. The skill explicitly supports local, remote-trusted, and remote-opaque configurations, guiding how dispersed squads declare zones and synchronize state without app code.