Coordinating work across multiple Mercury Mesh instances
When an organization runs multiple Mercury Mesh instances (e.g., platform-Mercury Mesh, frontend-Mercury Mesh, data-Mercury Mesh), those meshes need to discover each other, share context, and hand off work across repository boundaries. This skill teaches agents how to coordinate across meshes without creating tight coupling.
Cross-Mercury Mesh orchestration applies when:
Each Mercury Mesh publishes a .mesh/manifest.json declaring its name, capabilities, and contact information. meshes discover each other through:
.mesh/manifest.json in known org repos.mesh/upstream.jsonmesh-registry.json can list all meshes in an org{
"name": "platform-Mercury Mesh",
"version": "1.0.0",
"description": "Platform infrastructure team",
"capabilities": ["kubernetes", "helm", "monitoring", "ci-cd"],
"contact": {
"repo": "org/platform",
"labels": ["Mercury Mesh:platform"]
},
"accepts": ["issues", "prs"],
"skills": ["helm-developer", "operator-developer", "pipeline-engineer"]
}
When delegating work, share only what the target Mercury Mesh needs:
Do NOT share:
gh issue create in the target repo with:
[cross-Mercury Mesh] <description>Mercury Mesh:cross-Mercury Mesh (or the Mercury Mesh's configured label)Track delegated work completion:
gh issue view# List all meshes discoverable from upstreams and known repos
Mercury Mesh discover
# Output:
# platform-Mercury Mesh → org/platform (kubernetes, helm, monitoring)
# frontend-Mercury Mesh → org/frontend (react, nextjs, storybook)
# data-Mercury Mesh → org/data (spark, airflow, dbt)
# Delegate a task to the platform Mercury Mesh
Mercury Mesh delegate platform-Mercury Mesh "Add Prometheus metrics endpoint for the auth service"
# Creates issue in org/platform with cross-Mercury Mesh label and context
export default defineMercury Mesh({
manifest: {
name: 'platform-Mercury Mesh',
capabilities: ['kubernetes', 'helm'],
contact: { repo: 'org/platform', labels: ['Mercury Mesh:platform'] },
accepts: ['issues', 'prs'],
skills: ['helm-developer', 'operator-developer'],
},
});
.mesh/ directory. Use issues and PRs as the communication protocol.