Token导航 LogoToken导航

Agent Skill · 研究检索

multi-agent-orchestration(多 Agent 编排)

multi-agent-orchestration 用于记录任务执行中的错误、用户纠正、经验和能力缺口,适合在 Codex、Claude、Cursor、Gemini CLI 中希望让 Agent 持续沉淀问题、修正和最佳实践时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

multi-agent-orchestration 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证为 MIT,第三方扫描有未通过项,按安装量在研究检索类的 73,675 个 Skill 里排第 5,030。

总安装 28,224周安装 1,217GitHub Stars 5下载 9,888核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:multi-agent-orchestration(多 Agent 编排)
来源仓库:https://github.com/qodex-ai/ai-agent-skills
仓库路径:skills/multi-agent-orchestration
安装命令:
npx skills add https://github.com/qodex-ai/ai-agent-skills --skill multi-agent-orchestration
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。不同来源提供的安装方式可能略有差异;本站展示可直接复制的安装命令,安装前请核对来源页面。

skills.shnpx skills
npx skills add https://github.com/qodex-ai/ai-agent-skills --skill multi-agent-orchestration

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

通过精心策划的工作流程和协作推理来协调专业代理来解决复杂问题。

支持四种核心编排模式:顺序任务链、并行执行、分层委托和基于共识的辩论 包括 CrewAI、AutoGen、LangGraph 和 OpenAI Swarm 框架的模板和示例 提供代理通信(消息代理、共享内存)、工作流管理(执行、优化、监控)和性能基准测试的实用程序 涵盖代理设计原则、通信模式、工作流设计的最佳实践以及代理冲突和执行缓慢等常见挑战的解决方案

来源仓库内路径:skills/multi-agent-orchestration

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/qodex-ai/ai-agent-skills --skill multi-agent-o…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

multi-agent-orchestration 怎么安装?

在终端执行 npx skills add https://github.com/qodex-ai/ai-agent-skills --skill multi-agent-orchestrati…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

multi-agent-orchestration 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

multi-agent-orchestration 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

multi-agent-orchestration 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

multi-agent-orchestration 用的人多吗?

公开数据是累计安装 28,224 次,近一周安装 1,217 次,下载 9,888 次,GitHub 5 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

multi-agent-orchestration 安全吗?

第三方扫描有未通过项,风险较高。除非你确认过源码,否则不建议直接安装到常用环境。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 3 个目录同时收录,说明这个 Skill 流传比较广。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
multi-agent-orchestration

多 Agent 编排 · 本页

28,2245需要联网MIT未通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Multi-Agent Orchestration

Design and orchestrate sophisticated multi-agent systems where specialized agents collaborate to solve complex problems, combining different expertise and perspectives.

Quick Start

Get started with multi-agent implementations in the examples and utilities:

  • Examples: See examples/ directory for complete implementations:

- orchestration_patterns.py - Sequential, parallel, hierarchical, and consensus orchestration - framework_implementations.py - Templates for CrewAI, AutoGen, LangGraph, and Swarm

  • Utilities: See scripts/ directory for helper modules:

- agent_communication.py - Message broker, shared memory, and communication protocols - workflow_management.py - Workflow execution, optimization, and monitoring - benchmarking.py - Team performance and agent effectiveness metrics

Overview

Multi-agent systems decompose complex problems into specialized sub-tasks, assigning each to an agent with relevant expertise, then coordinating their work toward a unified goal.

When Multi-Agent Systems Shine

  • Complex Workflows: Tasks requiring multiple specialized roles
  • Domain-Specific Expertise: Finance, legal, HR, engineering need different knowledge
  • Parallel Processing: Multiple agents work on different aspects simultaneously
  • Collaborative Reasoning: Agents debate, refine, and improve solutions
  • Resilience: Failures in one agent don't break the entire system
  • Scalability: Easy to add new specialized agents

Architecture Overview

User Request
    ↓
Orchestrator
    ├→ Agent 1 (Specialist) → Task 1
    ├→ Agent 2 (Specialist) → Task 2
    ├→ Agent 3 (Specialist) → Task 3
    ↓
Result Aggregator
    ↓
Final Response

Core Concepts

Agent Definition

An agent is defined by:

  • Role: What responsibility does it have? (e.g., "Financial Analyst")
  • Goal: What should it accomplish? (e.g., "Analyze financial risks")
  • Expertise: What knowledge/tools does it have?
  • Tools: What capabilities can it access?
  • Context: What information does it need to work effectively?

Orchestration Patterns

1. Sequential Orchestration
  • Agents work one after another
  • Each agent uses output from previous agent
  • Use Case: Steps must follow order (research → analysis → writing)
2. Parallel Orchestration
  • Multiple agents work simultaneously
  • Results aggregated at the end
  • Use Case: Independent tasks (analyze competitors, market, users)
3. Hierarchical Orchestration
  • Senior agent delegates to junior agents
  • Manager coordinates flow
  • Use Case: Large projects with oversight
4. Consensus-Based Orchestration
  • Multiple agents analyze problem
  • Debate and refine ideas
  • Vote or reach consensus
  • Use Case: Complex decisions needing multiple perspectives
5. Tool-Mediated Orchestration
  • Agents use shared tools/databases
  • Minimal direct communication
  • Use Case: Large systems, indirect coordination

Multi-Agent Team Examples

Finance Team

Coordinator Agent
    ├→ Market Analyst Agent
    │   ├ Tools: Market data API, financial news
    │   └ Task: Analyze market conditions
    ├→ Financial Analyst Agent
    │   ├ Tools: Financial statements, ratio calculations
    │   └ Task: Analyze company financials
    ├→ Risk Manager Agent
    │   ├ Tools: Risk models, scenario analysis
    │   └ Task: Assess investment risks
    └→ Report Writer Agent
        ├ Tools: Document generation
        └ Task: Synthesize findings into report

Legal Team

Case Manager Agent (Coordinator)
    ├→ Contract Analyzer Agent
    │   └ Task: Review contract terms
    ├→ Precedent Research Agent
    │   └ Task: Find relevant case law
    ├→ Risk Assessor Agent
    │   └ Task: Identify legal risks
    └→ Document Drafter Agent
        └ Task: Prepare legal documents

Customer Support Team

Support Coordinator
    ├→ Issue Classifier Agent
    │   └ Task: Categorize customer issue
    ├→ Knowledge Base Agent
    │   └ Task: Find relevant documentation
    ├→ Escalation Agent
    │   └ Task: Determine if human escalation needed
    └→ Solution Synthesizer Agent
        └ Task: Prepare comprehensive response

Implementation Frameworks

1. CrewAI

Best For: Teams with clear roles and hierarchical structure

from crewai import Agent, Task, Crew

# Define agents
analyst = Agent(
    role="Financial Analyst",
    goal="Analyze financial data and provide insights",
    backstory="Expert in financial markets with 10+ years experience"
)

researcher = Agent(
    role="Market Researcher",
    goal="Research market trends and competition",
    backstory="Data-driven researcher specializing in market analysis"
)

# Define tasks
analysis_task = Task(
    description="Analyze Q3 financial results for {company}",
    agent=analyst,
    tools=[financial_tool, data_tool]
)

research_task = Task(
    description="Research competitive landscape in {market}",
    agent=researcher,
    tools=[web_search_tool, industry_data_tool]
)

# Create crew and execute
crew = Crew(
    agents=[analyst, researcher],
    tasks=[analysis_task, research_task],
    process=Process.sequential
)

result = crew.kickoff(inputs={"company": "TechCorp", "market": "AI"})

2. AutoGen (Microsoft)

Best For: Complex multi-turn conversations and negotiations

from autogen import AssistantAgent, UserProxyAgent, GroupChat, GroupChatManager

# Define agents
analyst = AssistantAgent(
    name="analyst",
    system_message="You are a financial analyst..."
)

researcher = AssistantAgent(
    name="researcher",
    system_message="You are a market researcher..."
)

# Create group chat
groupchat = GroupChat(
    agents=[analyst, researcher],
    messages=[],
    max_round=10,
    speaker_selection_method="auto"
)

# Manage group conversation
manager = GroupChatManager(groupchat=groupchat)

# User proxy to initiate conversation
user = UserProxyAgent(name="user")

# Have conversation
user.initiate_chat(
    manager,
    message="Analyze if Company X should invest in Y market"
)

3. LangGraph

Best For: Complex workflows with state management

from langgraph.graph import Graph, StateGraph
from langgraph.prebuilt import create_agent_executor

# Define state
class AgentState:
    research_findings: str
    analysis: str
    recommendations: str

# Create graph
graph = StateGraph(AgentState)

# Add nodes for each agent
graph.add_node("researcher", research_agent)
graph.add_node("analyst", analyst_agent)
graph.add_node("writer", writer_agent)

# Define edges (workflow)
graph.add_edge("researcher", "analyst")
graph.add_edge("analyst", "writer")

# Set entry/exit points
graph.set_entry_point("researcher")
graph.set_finish_point("writer")

# Compile and run
workflow = graph.compile()
result = workflow.invoke({"topic": "AI trends"})

4. OpenAI Swarm

Best For: Simple agent handoffs and conversational workflows

from swarm import Agent, Swarm

# Define agents
triage_agent = Agent(
    name="Triage Agent",
    instructions="Determine which specialist to route the customer to"
)

billing_agent = Agent(
    name="Billing Specialist",
    instructions="Handle billing and payment questions"
)

technical_agent = Agent(
    name="Technical Support",
    instructions="Handle technical issues"
)

# Define handoff functions
def route_to_billing(reason: str):
    return billing_agent

def route_to_technical(reason: str):
    return technical_agent

# Add tools to triage agent
triage_agent.functions = [route_to_billing, route_to_technical]

# Execute swarm
client = Swarm()
response = client.run(
    agent=triage_agent,
    messages=[{"role": "user", "content": "I have a billing question"}]
)

Orchestration Patterns

Pattern 1: Sequential Task Chain

Agents execute tasks in sequence, each building on previous results:

# Task 1: Research
research_output = research_agent.work("Analyze AI market trends")

# Task 2: Analysis (uses research output)
analysis = analyst_agent.work(f"Analyze these findings: {research_output}")

# Task 3: Report (uses analysis)
report = writer_agent.work(f"Write report on: {analysis}")

When to Use: Steps have dependencies, each builds on previous

Pattern 2: Parallel Execution

Multiple agents work simultaneously, results combined:

import asyncio

async def parallel_teams():
    # All agents work in parallel
    market_task = market_agent.work_async("Analyze market")
    technical_task = tech_agent.work_async("Analyze technology")
    user_task = user_agent.work_async("Analyze user needs")

    # Wait for all to complete
    market_results, tech_results, user_results = await asyncio.gather(
        market_task, technical_task, user_task
    )

    # Synthesize results
    return synthesize(market_results, tech_results, user_results)

When to Use: Independent analyses, need quick results, want diversity

Pattern 3: Hierarchical Structure

Manager agent coordinates specialists:

manager_agent.orchestrate({
    "market_analysis": {
        "agents": [competitor_analyst, trend_analyst],
        "task": "Comprehensive market analysis"
    },
    "technical_evaluation": {
        "agents": [architecture_agent, security_agent],
        "task": "Technical feasibility assessment"
    },
    "synthesis": {
        "agents": [strategy_agent],
        "task": "Create strategic recommendations"
    }
})

When to Use: Clear hierarchy, different teams, complex coordination

Pattern 4: Debate & Consensus

Multiple agents discuss and reach consensus:

agents = [bull_agent, bear_agent, neutral_agent]
question = "Should we invest in this startup?"

# Debate round 1
arguments = {agent: agent.argue(question) for agent in agents}

# Debate round 2 (respond to others)
counter_arguments = {
    agent: agent.respond(arguments) for agent in agents
}

# Reach consensus
consensus = mediator_agent.synthesize_consensus(counter_arguments)

When to Use: Complex decisions, need multiple perspectives, risk assessment

Agent Communication Patterns

1. Direct Communication

Agents pass messages directly to each other:

agent_a.send_message(agent_b, {
    "type": "request",
    "action": "analyze_document",
    "document": doc_content,
    "context": {"deadline": "urgent"}
})

2. Tool-Mediated Communication

Agents use shared tools/databases:

# Agent A writes to shared memory
shared_memory.write("findings", {"market_size": "$5B", "growth": "20%"})

# Agent B reads from shared memory
findings = shared_memory.read("findings")

3. Manager-Based Communication

Central coordinator manages agent communication:

manager.broadcast("update_all_agents", {
    "new_deadline": "tomorrow",
    "priority": "critical"
})

Best Practices

Agent Design

  • ✓ Clear, specific role and goal
  • ✓ Appropriate tools for the role
  • ✓ Relevant background/expertise
  • ✓ Distinct from other agents
  • ✓ Reasonable scope of work

Workflow Design

  • ✓ Clear task dependencies
  • ✓ Identified handoff points
  • ✓ Error handling between agents
  • ✓ Fallback strategies
  • ✓ Performance monitoring

Communication

  • ✓ Structured message formats
  • ✓ Clear context sharing
  • ✓ Error propagation strategy
  • ✓ Timeout handling
  • ✓ Audit logging

Orchestration

  • ✓ Define process clearly (sequential, parallel, etc.)
  • ✓ Set clear success criteria
  • ✓ Monitor agent performance
  • ✓ Implement feedback loops
  • ✓ Allow human intervention points

Common Challenges & Solutions

Challenge: Agent Conflicts

Solutions:

  • Clear role separation
  • Explicit decision-making rules
  • Consensus mechanisms
  • Conflict resolution agent
  • Clear authority hierarchy

Challenge: Slow Execution

Solutions:

  • Use parallel execution where possible
  • Cache results from expensive operations
  • Pre-process data
  • Optimize agent logic
  • Implement timeout handling

Challenge: Poor Quality Results

Solutions:

  • Better agent prompts/instructions
  • More relevant tools
  • Feedback integration
  • Quality validation agents
  • Result aggregation strategies

Challenge: Complex Workflows

Solutions:

  • Break into smaller teams
  • Hierarchical structure
  • Clear task definitions
  • Good state management
  • Documentation of workflow

Evaluation Metrics

Team Performance:

  • Task completion rate
  • Quality of results
  • Execution time
  • Cost (tokens/API calls)
  • Error rate

Agent Effectiveness:

  • Task success rate
  • Response quality
  • Tool usage efficiency
  • Communication clarity
  • Collaboration score

Advanced Techniques

1. Self-Organizing Teams

Agents autonomously decide roles and workflow:

# Agents negotiate roles based on task
agents = [agent1, agent2, agent3]
task = "complex financial analysis"

# Agents determine best structure
negotiated_structure = self_organize(agents, task)
# Returns optimal workflow for this task

2. Adaptive Workflows

Workflow changes based on progress:

# Monitor progress
if progress < expected_rate:
    # Increase resources
    workflow.add_agent(specialist_agent)
elif quality < threshold:
    # Increase validation
    workflow.insert_review_step()

3. Cross-Agent Learning

Agents learn from each other's work:

# After team execution
execution_trace = crew.get_execution_trace()

# Extract learnings
learnings = extract_patterns(execution_trace)

# Update agent knowledge
for agent, learning in learnings.items():
    agent.update_knowledge(learning)

Resources

Frameworks

Papers

  • "Generative Agents" (Park et al.)
  • "Self-Organizing Multi-Agent Systems" (research papers)

Implementation Checklist

  • Define each agent's role, goal, and expertise
  • Identify available tools/capabilities for each agent
  • Plan workflow (sequential, parallel, hierarchical)
  • Define communication patterns
  • Implement task definitions
  • Set success criteria for each task
  • Add error handling and fallbacks
  • Implement monitoring/logging
  • Test team collaboration
  • Evaluate quality and performance
  • Optimize based on results
  • Document workflow and decisions

Getting Started

  1. Start Small: Begin with 2-3 agents
  2. Clear Workflow: Document how agents interact
  3. Test Thoroughly: Validate agent behavior individually and together
  4. Monitor Closely: Track performance and results
  5. Iterate: Refine based on results
  6. Scale: Add agents and complexity as needed

平台分布

Claude Code

31.33%
按下载量换算3,098

Antigravity

24.26%
按下载量换算2,399

Codex

17.69%
按下载量换算1,749

Gemini CLI

11.53%
按下载量换算1,140

OpenCode

7.72%
按下载量换算763

github-copilot

3.69%
按下载量换算365

安全审计

Gen Agent Trust Hub

未通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。

继续浏览同类 Skills