multi-agent-coordination

Trace supervisor-worker handoffs and hierarchies in multi-agent workflows.

7|1|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/nexus-labs-automation/agent-observability --skill multi-agent-coordination-nexus-labs-automation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-agent-coordination
Source: https://github.com/nexus-labs-automation/agent-observability/tree/main/skills/multi-agent-coordination
Command: npx skills add https://github.com/nexus-labs-automation/agent-observability --skill multi-agent-coordination-nexus-labs-automation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Instrument multi-agent workflows to trace coordination, handoffs, and hierarchies across supervisor and worker agents, making it easier to understand decisions and handoffs in complex AI runs.

Core Features & Use Cases

  • Trace supervisor-worker handoffs and agent decisions across runs.
  • Model and verify parent-child relationships in multi-agent orchestration (hub-and-spoke, pipeline, parallel, hierarchical).
  • Collect standardized span attributes (agent.name, agent.parent_id, workflow.state) to enable end-to-end observability.

Quick Start

Start a multi-agent coordination run to observe end-to-end traces, handoffs, and actor hierarchies.

Frequently Asked Questions about multi-agent-coordination

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

FAQPage Schema
How do I trace multi-agent handoffs and parent-child hierarchies in AI workflows?

Trace multi-agent handoffs by attaching standardized span attributes like agent.name, agent.parent_id, and handoff_reason to instrumentation hooks, revealing supervisor-worker relationships and decision paths across complex AI runs.

Does this multi-agent coordination tracing work with LangGraph, CrewAI, and AutoGen patterns?

Multi-agent coordination tracing works with LangGraph, CrewAI, and AutoGen patterns, supporting context propagation across hub-and-spoke, pipeline, parallel, and hierarchical orchestration models to capture composite agent decisions.

What span attributes do I need to instrument for multi-agent observability?

Multi-agent observability requires standardized span attributes including agent.name, agent.parent_id, workflow.state, and handoff_reason, which enable end-to-end tracing of supervisor-worker delegation and task handoffs.

How to coordinate multi-agent workflows and verify supervisor-worker task delegation?

Coordinate multi-agent workflows by modeling parent-child relationships and attaching instrumentation hooks that capture handoff_reason and workflow.state, allowing you to verify task delegation across hierarchical agent structures.

Why does my multi-agent tracing lose context during worker agent handoffs?

Multi-agent tracing loses context during handoffs when instrumentation hooks fail to propagate parent-child relationships or omit agent.parent_id attributes, breaking the supervisor-worker hierarchy chain across orchestration patterns.

What's the best way to model parallel and hierarchical agent orchestration for observability?

Model parallel and hierarchical agent orchestration by mapping parent-child spans with agent.name and workflow.state attributes, capturing handoff_reason to achieve end-to-end observability across complex multi-agent ecosystems.