skills.rest
sudhakrms
sudhakrmsCOMMUNITY
Explore all skills by this author →
GitHub

distributed-mesh

Generate mesh.json and sync scripts to coordinate squads across machines.

1|Updated Apr 17, 2026
Search Tags:#automation#git#distributed#state-management#mesh#squad-coordination
One-click install
npx skills add https://github.com/sudhakrms/CalendarControl --skill distributed-mesh-sudhakrms
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/sudhakrms/CalendarControl/tree/main/coffee/.copilot/skills/distributed-mesh
Command: npx skills add https://github.com/sudhakrms/CalendarControl --skill distributed-mesh-sudhakrms

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams coordinate squads across multiple machines by materializing remote state using git transport. It eliminates manual syncing and ensures agents read up-to-date mesh state.

Core Features & Use Cases

  • Generate mesh.json from user answers about squads, zones, and file paths using the provided mesh.json.example as the schema.
  • Copy bundled sync scripts (sync-mesh.sh and sync-mesh.ps1) into the project root for deterministic state synchronization.
  • Initialize a Zone 2 shared state repository with sync-mesh --init to scaffold per-squad state and a decisions entry.
  • Create a decision entry documenting the mesh configuration for team awareness.

Quick Start

Run the bundled sync script to materialize remote 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 using git?▼

You coordinate distributed squads across machines by materializing remote state with git transport. This assembles a consistent mesh state from remote sources, ensuring agents read up-to-date data without manual syncing.

What is mesh state synchronization and when do I need it for squad coordination?▼

Mesh state synchronization ensures multiple machines read consistent remote state via git transport. You need it when squads operate across local, remote-trusted, or remote-opaque zones and require up-to-date shared configuration.

How do I generate a mesh.json configuration file from my squad topology?▼

You generate mesh.json by answering questions about squads, zones, and file paths using the provided mesh.json.example as the schema. This topology file serves as the foundation for materializing the remote state.

Can I initialize a shared state repository for Zone 2 using the bundled sync scripts?▼

Yes, you can initialize a Zone 2 shared state repository by running the bundled sync-mesh script with the --init flag. This scaffolds per-squad state and records an initial decisions entry.

Does distributed mesh state management work across different operating systems?▼

Distributed mesh state management supports cross-platform synchronization by providing both sync-mesh.sh and sync-mesh.ps1 scripts. These bundled scripts enable deterministic state materialization on Unix and Windows environments.

Why does my squad coordination workflow require recording a decision entry in mesh.json?▼

Recording a decision entry in mesh.json documents the mesh configuration for team awareness. It ensures that all distributed squads understand the topology and state synchronization setup established from remote sources.

Related Skills

Explore More Software Engineering Skills→
mpauloskympaulosky

distributed-mesh

Coordinate cross-machine squad state by synchronizing state files via git mesh transport.

Community
Advanced
Golnaz89Golnaz89

distributed-mesh

Generate mesh.json and copy sync scripts for git-backed cross-machine squads.

Community
Intermediate
TaylorHustonTaylorHuston
69

git-sync

Sync multiple git repositories in a workspace via a Python CLI.

Community
Basic
sytonesytone
2

distributed-mesh

Coordinate distributed squads across machines using git transport.

Community
Advanced