distributed-mesh

Configures git-based state synchronization for squads distributed across multiple machines.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/codebytes/btt --skill distributed-mesh-codebytes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: distributed-mesh
Source: https://github.com/codebytes/btt/tree/main/.squad/templates/skills/distributed-mesh
Command: npx skills add https://github.com/codebytes/btt --skill distributed-mesh-codebytes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jq, git, curl.

What problem does it solve? Coordinating AI agent squads that run on different machines, CI runners, or partner organizations is hard because agents can only read local files. This Skill solves that by using git as the transport layer to materialize remote squad state onto the local filesystem before agents read it. ## Core Features & Use Cases - Mesh topology configuration: Generates a mesh.json file mapping each squad to a zone (local, remote-trusted, or remote-opaque) with its connection details. - Bundled sync scripts: Copies pre-built sync-mesh.sh and sync-mesh.ps1 scripts that pull Zone 2 state via git and fetch Zone 3 published contracts via HTTPS. - State repo initialization: Scaffolds a shared mesh state repository with per-squad directories and placeholder SUMMARY.md files using the --init flag. - Use Case: A developer laptop squad and a CI squad need to share results. The skill generates mesh.json, installs the sync scripts, and each squad runs git pull before work and git push after, with write partitioning preventing merge conflicts. ## Quick Start Ask the agent to set up a distributed mesh for your squads and answer its questions about which squads participate and which zone each one belongs to.

Frequently Asked Questions about distributed-mesh

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

FAQPage Schema
How do I coordinate AI agent squads across different machines?

Use git as the transport layer: each squad pulls remote state before working and pushes its own state after. The mesh.json file maps each squad to a zone (local, remote-trusted, or remote-opaque) and the sync-mesh scripts materialize remote files locally.

What is the difference between remote-trusted and remote-opaque zones?

Remote-trusted squads share git access within the same org, so their full state is cloned or pulled via git. Remote-opaque squads are external organizations with no shared auth, so only their published SUMMARY.md contract is fetched over HTTPS.

How do I avoid git merge conflicts between squads?

Write partitioning prevents conflicts: each squad writes only to its own directory and files, so no two squads ever modify the same file. If a push fails because the branch is behind, run git pull --rebase and push again.

What dependencies does the sync-mesh script require?

The bash script requires jq, git, and curl. The PowerShell version requires only git, using built-in cmdlets for JSON parsing and HTTPS fetches. Bearer tokens for opaque zones are read from environment variables named after each squad.

When should I not use a distributed mesh?

Skip the mesh when all squads run on the same machine, since agents can read local files directly with zero transport. Also avoid building daemons, message queues, or federation protocols; git push and pull are sufficient for agent-timescale coordination.