distributed-mesh

Configure distributed mesh topology using git-based synchronization for cross-machine squads.

1|Updated Dec 23, 2025

Search Tags:#git #distributed #coordination #sync #mesh #squads

Ready to run

npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill distributed-mesh-jonnymuir

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/jonnymuir/Umbraco.Prism/tree/main/.copilot/skills/distributed-mesh
Command: npx skills add https://github.com/jonnymuir/Umbraco.Prism --skill distributed-mesh-jonnymuir

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, jq, curl.

What problem does it solve?

This skill solves the challenge of maintaining context and communication between squads operating on different machines, CI runners, or organizations where direct filesystem access is impossible.

Core Features & Use Cases

Mesh Topology Configuration: Standardizes how squads define their location (local, remote-trusted, or remote-opaque) using a unified mesh.json schema.
Git-based Transport: Leverages git as the transport layer to materialize remote squad state onto the local disk, ensuring agents always work with local files.
Use Case: A developer on a laptop needs to coordinate with a CI squad on a remote server; this skill sets up the sync mechanism so the CI squad's test results appear locally as if they were on the same machine.

Quick Start

Invoke the distributed-mesh skill to configure your squad topology and initialize the necessary synchronization scripts for your project.

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?▼

Synchronize squad state across remote machines by configuring a distributed mesh topology that uses git as the primary transport mechanism to automatically materialize remote state onto local disks.

What is a distributed mesh topology for multi-squad coordination?▼

A distributed mesh topology is a network configuration that standardizes how squads define their location as local, remote-trusted, or remote-opaque using a unified mesh.json schema for cross-machine communication.

Can I coordinate CI runners with my local development laptop without direct filesystem access?▼

Yes, you can coordinate CI runners with local laptops by applying automated git-based synchronization and contract fetching to materialize test results and state locally without direct filesystem access.

Do I need jq and curl to set up cross-machine squad communication?▼

You need jq and curl alongside git to configure the distributed mesh topology, as these dependencies support parsing the unified mesh.json schema and executing the necessary synchronization scripts.

When should I use git-based sync instead of direct filesystem sharing for squads?▼

Use git-based sync for multi-squad environments spanning developer laptops, CI runners, and external partner organizations where direct filesystem access is impossible or restricted.