Distributed Mesh
How to coordinate with squads on different machines using git as transport
Install
npx skills add Azure-Samples/agent-skills-dotnet-demo --skill distributed-meshgit clone --depth 1 https://github.com/Azure-Samples/agent-skills-dotnet-demo.git /tmp/agent-skills-dotnet-demo
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills-dotnet-demo/.squad/templates/skills/distributed-mesh ~/.claude/skills/distributed-meshPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
## SCOPE **✅ THIS SKILL PRODUCES (exactly these, nothing more):** 1. **`mesh.json`** — Generated from user answers about zones and squads (which squads participate, what zone each is in, paths/URLs for each), using `mesh.json.example` in this skill's directory as the schema template 2. **`sync-mesh.sh` and `sync-mesh.ps1`** — Copied from this skill's directory into the project root (these are bundled resources, NOT generated code) 3. **Zone 2 state repo initialization** (if applicable) — If the user specified a Zone 2 shared state repo, run `sync-mesh.sh --init` to scaffold the state repo structure 4. **A decision entry** in `.squad/decisions/inbox/` documenting the mesh configuration for team awareness **❌ THIS SKILL DOES NOT PRODUCE:** - **No application code** — No validators, libraries, or modules of any kind - **No test files** — No test suites, test cases, or test scaffolding - **No GENERATING sync scripts** — They are bundled with this skill as pre-built resources. COPY them, don't generate them. - **No daemons or services** — No background processes, servers, or persistent runtimes - **No modifications to existing squad files** beyond the decision entry (no changes to team.md, routing.md, agent charters, etc.) **Your role:** Configure the mesh topology and install the bundled sync scripts. Nothing more. ## Context
Details
- Skill name
distributed-mesh- Repository
- Azure-Samples/agent-skills-dotnet-demo
- Path
.squad/templates/skills/distributed-mesh/SKILL.md- License
- MIT
- Repo updated
- 10 April 2026
FAQ
What does the Distributed Mesh skill do?
How to coordinate with squads on different machines using git as transport
How do I install the Distributed Mesh skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Azure-Samples/agent-skills-dotnet-demo --skill distributed-mesh. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Distributed Mesh popular?
It lives in Azure-Samples/agent-skills-dotnet-demo, which has 45 GitHub stars and 11 forks.
Related skills
Agent Collaboration
45Azure-Samples/agent-skills-dotnet-demo
Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
Agent Conduct
45Azure-Samples/agent-skills-dotnet-demo
Shared hard rules enforced across all squad agents
Architectural Proposals
45Azure-Samples/agent-skills-dotnet-demo
How to write comprehensive architectural proposals that drive alignment before code is written
Gh Auth Isolation
45Azure-Samples/agent-skills-dotnet-demo
Safely manage multiple GitHub identities (EMU + personal) in agent workflows
Diff Intake
48amplitude/mcp-marketplace
Reads a PR or branch diff and produces a structured YAML change brief for downstream analytics instrumentation skills. Use this as the first step whenever a user shares a PR link, branch comparison, or raw diff and wants to understand what changed, what needs tracking, or how to instrument a feature. Trigger on phrases like "review this PR", "what changed in this branch", "help me instrument this diff", "check analytics coverage for this change", or any request to start the analytics review workflow.
Git Workflow
45Azure-Samples/agent-skills-dotnet-demo
Squad branching model: dev-first workflow with insiders preview channel
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.