skills.rest
olivomarco
olivomarcoCOMMUNITY
Explore all skills by this author →
Website𝕏@olivomarcoGitHub

distributed-mesh

Generate mesh.json and sync squad state across machines via Git.

66|41|Updated Mar 4, 2026
Search Tags:#git#distributed#coordination#initialization#state#mesh#squads
One-click install
npx skills add https://github.com/olivomarco/vbd-copilot --skill distributed-mesh-olivomarco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/olivomarco/vbd-copilot/tree/main/.copilot/skills/distributed-mesh
Command: npx skills add https://github.com/olivomarco/vbd-copilot --skill distributed-mesh-olivomarco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, curl.

What problem does it solve?

Coordinate squads across multiple machines by using Git as the transport to materialize remote state locally, enabling cross-machine collaboration without persistent daemons.

Core Features & Use Cases

  • Generate a mesh.json configuration from declared squads and zones.
  • Copy bundled sync-mesh.sh and sync-mesh.ps1 into your project to materialize remote state on startup.
  • Initialize Zone 2 state repositories and record a concise mesh decision entry for team awareness.

Quick Start

Describe your squads and zones, then run the included sync-mesh scripts to initialize and synchronize the mesh state before agents start.

Frequently Asked Questions about distributed-mesh

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

FAQPage Schema
How do I coordinate distributed squads across multiple machines without running persistent daemons?▼

You can coordinate distributed squads by using Git as the transport to materialize remote state locally. This enables cross-machine synchronization without requiring persistent background daemons.

What is a Git mesh and how does it manage state initialization for remote agents?▼

A Git mesh manages state initialization by generating a mesh.json configuration from declared squads and zones. The included sync scripts materialize the remote state locally before agents start.

How do I set up cross-machine squad coordination using Git repositories?▼

Describe your squads and zones, then run the bundled sync-mesh.sh or sync-mesh.ps1 scripts. These scripts initialize Zone 2 state repositories and record a mesh decision entry for team awareness.

Do I need any specific dependencies to run the sync-mesh scripts for squad coordination?▼

Yes, you need jq, git, and curl installed on your machine to execute the sync-mesh scripts and manage the distributed mesh state synchronization properly.

Can I use this distributed coordination approach for both local and remote trusted setups?▼

Yes, this Git-based coordination applies to diverse scenarios including local squads, remote-trusted setups, and remote-opaque contracts, satisfying deterministic setup steps across different environments.

Why use Git as a transport layer for distributed state instead of other coordination tools?▼

Using Git as the transport layer allows explicit state materialization locally without persistent daemons. It provides deterministic setup and synchronization across machines using standard version control infrastructure.

Related Skills

Explore More Software Engineering Skills→
lbouriezlbouriez

distributed-mesh

Coordinate distributed squads across machines using git as transport.

Community
Advanced
jperezdelrealjperezdelreal

distributed-mesh

Generate mesh.json manifests and copy sync scripts for distributed squad coordination.

Community
Intermediate
barichterbarichter

distributed-mesh

Configure distributed mesh topologies and synchronize state across machines using git and mesh.json.

Community
Intermediate
QuintenpsQuintenps

distributed-mesh

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

Community
Intermediate