distributed-mesh

Coordinate distributed squads across machines using git as transport.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate distributed squads across machines by using git as the transport to synchronize state and decisions, enabling offline-first collaboration without centralized infrastructure.

Core Features & Use Cases

  • Supports topology-driven setup across local, remote-trusted, and remote-opaque squads.
  • Generates a mesh.json configuration, bundles pre-built sync scripts, and records decisions for team awareness.
  • Guides agent workflows from topology capture to state materialization and governance.

Quick Start

Run the mesh setup steps to generate mesh.json and copy the bundled sync scripts.

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 squads using git?

You can synchronize state across distributed squads by using git as a transport layer to coordinate offline-first collaboration, applying a mesh configuration to initialize state and track cross-machine decisions.

What is the best way to coordinate multiple machines without centralized infrastructure?

Git-backed distributed coordination enables offline-first team collaboration without centralized infrastructure by capturing topology setups and materializing state through bundled synchronization scripts.

How do I set up a cross-machine mesh topology for local and remote squads?

Setting up a cross-machine mesh involves running mesh setup steps to generate a mesh.json configuration, which captures topology for local, remote-trusted, and remote-opaque squads.

Can I track distributed coordination decisions without a centralized server?

Yes, you can track distributed coordination decisions without a centralized server by writing a mesh-setup decision entry into your git repository to maintain team awareness of configurations.

Do I need specific sync scripts to manage state initialization across organizations?

Yes, cross-machine state initialization requires bundled sync scripts like sync-mesh.sh and sync-mesh.ps1 to materialize state and govern agent workflows across organizational boundaries.