distributed-mesh

Materialize remote squad state into local directories using git and HTTP fetch.

209|27|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/dotnet/maui-labs --skill distributed-mesh-dotnet
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/dotnet/maui-labs/tree/main/src/Comet/.copilot/skills/distributed-mesh
Command: npx skills add https://github.com/dotnet/maui-labs --skill distributed-mesh-dotnet

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Distributed squad work often breaks the simple “read local files” convention because squad state lives on other machines or other organizations.

Core Features & Use Cases

  • Zone-based coordination: supports local, remote-trusted (shared git auth), and remote-opaque (published contract fetch) communication.
  • Single-file mesh configuration: generates a root mesh.json that describes who participates, which zone they are in, and how to materialize their state.
  • Deterministic sync bootstrapping: copies pre-bundled sync-mesh.sh and sync-mesh.ps1 into the project root and optionally initializes Zone 2 state scaffolding.
  • Team awareness: writes a decision entry in .squad/decisions/inbox/ documenting the mesh so the team can coordinate safely.

Quick Start

Use the distributed-mesh skill to configure zones and connection details for each participating squad, then run sync-mesh before any agents start reading state.

Frequently Asked Questions about distributed-mesh

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate squad state across different machines using git?

To coordinate cross-machine squad state with git, you generate a root mesh.json describing participants and zones, then use bundled sync-mesh scripts to materialize remote state into local filesystem directories.

How does cross-machine team coordination work when machines cannot share direct file access?

Cross-machine team coordination works by using HTTP fetch and git to pull remote squad state into local directories, applying zone-based rules for trusted or opaque remote communication without direct file access.

What is a mesh.json file used for in distributed squad coordination?

A mesh.json file is a single-file configuration used in distributed squad coordination to describe who participates, which communication zone they occupy, and how their remote state is materialized locally.

Can I use this distributed coordination approach for CI runners and partner organizations?

Yes, this distributed coordination approach applies when squads run on different developer machines, CI runners, VMs, or partner organizations that cannot share direct access to each other's files.

What are the communication zones supported for remote state synchronization?

The supported communication zones for remote state synchronization are local, remote-trusted using shared git authentication, and remote-opaque relying on published contract fetch.

Do I need to run sync-mesh before starting agents to read squad state?

Yes, you must run sync-mesh before any agents start reading state to ensure remote squad state is fully materialized into local directories and a decision entry is written to the inbox.