skills.rest
CarlosSardo
CarlosSardoCOMMUNITY
Explore all skills by this author →
GitHub

distributed-mesh

Generates mesh.json and copies sync-mesh.sh, sync-mesh.ps1 scripts for distributed squads using git transport.

Updated Aug 23, 2026
Search Tags:#automation#git#coordination#distributed-systems#workflows#mesh#state-repo
One-click install
npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill distributed-mesh-carlossardo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/CarlosSardo/nats-poc-simulator/tree/main/.copilot/skills/distributed-mesh
Command: npx skills add https://github.com/CarlosSardo/nats-poc-simulator --skill distributed-mesh-carlossardo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates coordinating squads across multiple machines by using git as the transport layer to share mesh state and synchronization scripts.

Core Features & Use Cases

  • Generates mesh.json from user-defined topology
  • Provides bundled sync-mesh.sh and sync-mesh.ps1 scripts for materializing remote state locally
  • Supports Zone 2 initialization to scaffold a state repository
  • Writes a decision inbox entry documenting the mesh configuration for awareness

Quick Start

Run the mesh configuration workflow to produce mesh.json, copy the bundled sync scripts, initialize the state repository if needed, and write a decision entry.

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

To coordinate distributed squads across machines using git, you generate a mesh.json file from your topology, copy synchronization scripts into your project root, and optionally initialize a git-backed state repository to share mesh state.

When do I need a mesh.json file for distributed team workflows?▼

You need a mesh.json file when your squads span multiple machines or organizations, requiring a shared topology definition to synchronize workflows and coordinate distributed automation across different environments.

Do I need to initialize a git state repository before setting up distributed workflows?▼

Initializing a git state repository is optional but recommended for Zone 2 setups to scaffold a centralized state repository, enabling squads to publish and fetch shared state and synchronization scripts across machines.

What are the limitations of using git as a transport layer for distributed systems coordination?▼

Using git as a transport layer for distributed systems coordination relies on HTTPS fetches for Zone 3 published state and requires manual execution of synchronization scripts, which may introduce latency compared to real-time coordination protocols.

Can I use mesh state synchronization scripts on both Windows and Linux machines?▼

Yes, mesh state synchronization works on both platforms by copying bundled sync-mesh.sh for Linux environments and sync-mesh.ps1 for Windows environments into your project root to materialize remote state locally.

Related Skills

Explore More Software Engineering Skills→
jguadagnojguadagno
18

distributed-mesh

Generate mesh.json and sync scripts for git-based squad coordination.

Community
Intermediate
dotnetdotnet
209

distributed-mesh

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

Official
Intermediate
samChang72samChang72
1

github-workflow-automation

Automate GitHub workflows with AI-powered pull request reviews and issue triage.

Community
Advanced
QuintenpsQuintenps

distributed-mesh

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

Community
Intermediate