Skip to main content

Type

agent_communication

Variants

Read Only, Limited, Full Orchestration
Purpose: The Agent Communication skill enables hierarchical agent orchestration, allowing agents to delegate tasks to specialist agents or coordinate multi-agent workflows.

Common Use Cases

Delegating to specialist agentsRoute tasks to agents with specific expertise or capabilities

Orchestrating multi-agent workflowsCoordinate complex workflows across multiple specialized agents

Calling team-based executionsExecute tasks using team agents with shared capabilities

Session continuationResume or extend existing agent sessions

Variants Overview

Choosing a variant: Use Limited for most scenarios with whitelist-based control. Only upgrade to Full Orchestration when unrestricted delegation is required. See Variant Configuration for detailed differences.

Configuration

Example Configuration:
Read Only:
  • allowed_operations: [β€œget_execution_status”] (locked)
  • No execution capability
Limited:
  • max_execution_depth: 2 (recommended)
  • Requires whitelist configuration
  • max_concurrent_calls: 3
Full Orchestration:
  • allowed_operations: [”*”] (all operations)
  • allowed_agents: [”*”] (all agents)
  • max_execution_depth: 5
  • max_concurrent_calls: 10
See: Variant Configuration Guide

Quick Start

View Complete Examples

See full orchestration patterns, deployment workflows, and multi-agent coordination examples

Agent Execution Examples

Single Agent Call

Orchestrator Request:
Orchestrator Action:

Sequential Execution

Orchestrator Request:
Orchestrator Actions:

Team Execution

Orchestrator Request:
Orchestrator Action:

Security Features

Circular Call DetectionPrevents infinite loops where agents call each other recursively

Execution Depth LimitingLimits how deep agent call chains can go

Whitelist-based AccessOnly allows calling explicitly permitted agents and teams

Concurrent LimitsPrevents resource exhaustion by limiting parallel calls

Best Practices

Always specify allowed_agents rather than using ”*” wildcards.
Keep max_execution_depth low (2-3) to prevent complex call chains.
Configure max_concurrent_calls to prevent resource exhaustion.
Best Practice: Set max_execution_depth to prevent infinite loops. A depth of 2-3 is sufficient for most orchestration scenarios.

Solutions:
  • Verify agent ID is in allowed_agents list
  • Check execute_agent is in allowed_operations
  • Confirm target agent exists and is enabled
Solutions:
  • Increase max_execution_depth if appropriate
  • Restructure orchestration to reduce call chain depth
  • Consider using workflow executor for complex chains
Solutions:
  • Review agent call chain for circular references
  • Restructure orchestration logic to avoid loops
  • Use different agents for different stages

Workflow Executor

Alternative for complex multi-step workflows

Contextual Awareness

Share context between orchestrated agents

Knowledge API

Agents can share knowledge base access

View All Skills

Return to built-in skills overview