distributed-mesh

Configure distributed squad communication via unified mesh topology with git-based state synchronization.

Updated Apr 16, 2026

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

Ready to run

npx skills add https://github.com/Quintenps/contactswap-agents --skill distributed-mesh-quintenps

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/Quintenps/contactswap-agents/tree/main/.copilot/skills/distributed-mesh
Command: npx skills add https://github.com/Quintenps/contactswap-agents --skill distributed-mesh-quintenps

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, jq, curl, and includes scripts (resource) components.

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 and connectivity using a unified mesh.json schema.
Automated State Synchronization: Uses git-based transport to materialize remote squad state locally, ensuring agents always have the latest context.
Use Case: A developer laptop needs to pull the latest test results from a remote CI squad and published contract summaries from a partner organization to inform local development decisions.

Quick Start

Invoke the distributed-mesh skill to configure your squad topology and initialize the sync scripts by following the guided prompts.

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 multiple machines using git?▼

Git-based transport facilitates cross-machine state synchronization by mapping local and remote filesystem zones to a unified mesh topology. It materializes remote squad state locally, eliminating the need for complex message queues or service discovery protocols.

What is a mesh topology for distributed squad coordination?▼

A mesh topology for distributed squad coordination standardizes how squads define their location and connectivity using a unified mesh.json schema. It maps local and remote filesystem zones to enable non-persistent agent coordination across different machines or CI runners.

Do I need a message queue or service discovery to coordinate squads across machines?▼

No, you do not need complex message queues or service discovery protocols to coordinate squads across machines. The distributed mesh approach satisfies non-persistent agent coordination requirements solely using git-based transport and HTTP-based contract fetching.

How do I fetch contract summaries from a remote squad when filesystem access is impossible?▼

You can fetch contract summaries from remote squads using HTTP-based contract fetching. This allows opaque remote squads to publish context to your local machine even when direct filesystem access is impossible.

Can I use distributed-mesh to pull CI runner test results to my local development machine?▼

Yes, you can pull the latest test results from a remote CI squad to a developer laptop using the distributed-mesh skill. It automates state synchronization to ensure your local agents have the latest remote context to inform development decisions.

What dependencies do I need to configure a distributed mesh for cross-machine state synchronization?▼

You need git, jq, and curl installed to configure a distributed mesh for cross-machine state synchronization. Git handles the state transport, while curl and jq support HTTP-based contract fetching and JSON schema processing.