skills.rest
Golnaz89
Golnaz89COMMUNITY
Explore all skills by this author →
Website𝕏@Golnaz89GitHub

distributed-mesh

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

Updated Jan 5, 2026
Search Tags:#git#mesh#state-sync#distributed-coordination#zone-2#zone-3#decision-entry
One-click install
npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill distributed-mesh-golnaz89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/Golnaz89/golnaz89.github.io/tree/main/.copilot/skills/distributed-mesh
Command: npx skills add https://github.com/Golnaz89/golnaz89.github.io --skill distributed-mesh-golnaz89

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, curl.

What problem does it solve?

Coordinate distributed squads across machines by materializing remote files locally using a git-backed mesh.

Core Features & Use Cases

  • Mesh configuration: generate a mesh.json describing squads and zones.
  • Copy bundled sync scripts: sync-mesh.sh and sync-mesh.ps1 into the project root.
  • Zone 2 init: if a Zone 2 state repo is configured, run sync-mesh.sh --init to scaffold the state repo.
  • Decision entry: write a .squad/decisions/inbox entry documenting the mesh configuration.

Quick Start

Run the distributed-mesh skill to acquire topology prompts, generate mesh.json, and copy the prebuilt sync scripts into your project root.

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

Distributed squad coordination over git works by materializing remote state into the local filesystem via a mesh.json configuration. It uses git transport to sync files across local, remote-trusted, and remote-opaque zones without generating code.

What is git mesh state sync for distributed coordination?▼

Git mesh state sync is a coordination mechanism that materializes remote files locally using a mesh.json configuration and git transport. It enables cross-machine squads to share state by running bundled sync scripts before agent execution.

Do I need jq and curl to run distributed mesh synchronization?▼

Yes, distributed mesh synchronization requires jq, git, and curl as dependencies. These tools facilitate the git transport operations and JSON configuration parsing needed to materialize remote state into your local filesystem.

How do I initialize a Zone 2 state repo for cross-machine coordination?▼

To initialize a Zone 2 state repo, run the bundled sync-mesh.sh script with the --init flag after generating your mesh.json configuration. This scaffolds the state repository required to materialize remote state locally.

What are the limitations of using a git-backed mesh for distributed state sync?▼

A key limitation of git-backed mesh state sync is its strict workflow requirement: you must run sync-mesh to materialize remote state before agent execution. It also enforces no code generation and relies entirely on git transport.

When do I need to record a decision entry in distributed mesh coordination?▼

You record a decision entry in distributed mesh coordination after generating mesh.json, copying sync scripts, and initializing Zone 2 state repos. The skill writes a .squad/decisions/inbox entry documenting the finalized mesh configuration.

Related Skills

Explore More Software Engineering Skills→
lv7devlv7dev

Verification Before Completion

Run verification commands and produce pass/fail status reports.

Community
Basic
Leep-GHLeep-GH

distributed-mesh

Generate mesh.json and sync scripts to materialize remote state via git.

Community
Intermediate
WayneWalterBerryWayneWalterBerry

distributed-mesh

Coordinate cross-machine squads by generating mesh.json from git-based workflows.

Community
Advanced
sytonesytone
2

distributed-mesh

Coordinate distributed squads across machines using git transport.

Community
Advanced