distributed-mesh

Generate mesh.json and install sync scripts for cross-machine squad state synchronization.

9|1|Updated Jul 21, 2025
One-click install
npx skills add https://github.com/usepowershell/PoshMcp --skill distributed-mesh-usepowershell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/usepowershell/PoshMcp/tree/main/.copilot/skills/distributed-mesh
Command: npx skills add https://github.com/usepowershell/PoshMcp --skill distributed-mesh-usepowershell

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, curl.

What problem does it solve?

Enable agents and squads distributed across machines or organizations to read and share squad state by materializing remote files locally using git or HTTP fetches so agents can operate as if all files are on the same filesystem.

Core Features & Use Cases

  • Zone-based topology: Define local, remote-trusted (git), and remote-opaque (HTTP contract) squads in a single mesh.json to control how state is synced.
  • Bundled sync tools: Provide cross-platform sync scripts (sync-mesh.sh and sync-mesh.ps1) that clone/pull git repos for Zone 2 and fetch published SUMMARY.md for Zone 3.
  • Operational workflow: Generate mesh.json, copy sync scripts to the project root, optionally initialize a shared Zone 2 state repo, and record a decision entry for team awareness.

Quick Start

Configure a distributed mesh with named squads and their zones, copy the provided sync-mesh.sh and sync-mesh.ps1 into the project root, and generate mesh.json at the repository root.

Frequently Asked Questions about distributed-mesh

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

FAQPage Schema
How do I synchronize agent state across different machines using git?

You can synchronize squad state across machines by generating a mesh.json file and installing bundled sync scripts that clone or pull git repositories to materialize remote files locally for cross-machine coordination.

What's the best way to coordinate distributed squads running on separate CI runners?

Coordinating distributed squads on CI runners requires a zone-based topology defined in mesh.json, enabling local, remote-trusted via git, and remote-opaque via HTTP contract fetches to synchronize state before agent execution.

Do I need jq and curl to sync files for cross-machine squad coordination?

Yes, you need jq, git, and curl installed to execute the bundled sync scripts for cross-machine squad coordination, as these dependencies handle JSON parsing, repository cloning, and HTTP contract fetching.

How does a zone-based topology manage remote trusted and remote opaque squads?

A zone-based topology manages remote trusted squads by cloning and pulling git repositories for full state synchronization, while remote opaque squads use HTTP contract fetches to retrieve only published summary files.

Can I initialize a shared state repository for distributed agent synchronization?

Yes, you can initialize a shared Zone 2 state repository during mesh configuration to provide a central git remote that trusted squads clone and pull from to materialize their state locally.

Why use HTTP contract fetches for remote opaque squads instead of git clone?

HTTP contract fetches are used for remote opaque squads to avoid granting git access to untrusted partners, securely retrieving only published SUMMARY.md files instead of synchronizing the entire repository state.