distributed-mesh

Generates Mesh state files and syncs them via Git for multi-computer collaboration.

3|5|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ronniegeraghty/hyoka --skill distributed-mesh-ronniegeraghty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/ronniegeraghty/hyoka/tree/main/.squad/templates/skills/distributed-mesh
Command: npx skills add https://github.com/ronniegeraghty/hyoka --skill distributed-mesh-ronniegeraghty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables cross-machine squad coordination by using git as the transport to materialize and share mesh state, allowing teams to collaborate without custom daemons.

Core Features & Use Cases

  • Mesh state generation: Produce a mesh.json describing squads, zones, and sync targets based on user input.
  • Bundled sync resources: Copy prebuilt sync-mesh.sh and sync-mesh.ps1 into the project root to initialize or update local state.
  • Guided workflow: Step-by-step agent workflow to initialize Zone 2 state repositories and document decisions for team awareness.

Quick Start

Answer the topology questions in Step 1 and run the bundled sync-mesh script to materialize state.

Frequently Asked Questions about distributed-mesh

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

FAQPage Schema
How do I coordinate multi-machine squads without running a custom daemon?

Multi-machine squad coordination can be achieved by using git as the transport to materialize and share mesh state, allowing distributed teams to sync without custom daemons.

What is the best way to share state across distributed teams using git?

Sharing state across distributed teams with git involves generating a mesh.json file to describe squads, zones, and sync targets, then copying bundled sync scripts to initialize or update local state.

How do I generate mesh state and initialize Zone 2 state repositories?

To generate mesh state and initialize Zone 2 repositories, answer the topology questions in the guided workflow step, run the bundled sync-mesh script, and write a mesh decision entry to document the setup.

Can I use this mesh state sync workflow on both Linux and Windows machines?

Yes, the workflow supports both Linux and Windows machines by copying prebuilt sync-mesh.sh and sync-mesh.ps1 scripts into the project root to initialize or update local state.

Do I need any external dependencies to set up cross-machine coordination with git?

No external dependencies are required to set up cross-machine coordination with git, as the workflow uses bundled sync scripts and a generated mesh.json file to establish reproducible mesh state.