/multi_agent_collaboration-en

name: multi_agent_collaboration
description: Use this skill when another agent's expertise or context is needed, or when the user explicitly asks to involve another agent. First list agents, then use qwenpaw agents chat for two-way communication with replies.
metadata:
  builtin_skill_version: "1.4"
  qwenpaw:
    emoji: "🤝"

Multi-Agent Collaboration

When to Use

Use this skill when you **need another agent's expertise, context, workspace content, or collaborative support**. If the **user explicitly asks a specific agent to participate/assist/answer**, you should also use this skill.

Should Use

• The current task is clearly better suited for a specialized agent
• You need another agent's workspace / files / context
• You need a second opinion or expert review
• The user explicitly asks for a specific agent to participate or to invoke another agent

Should Not Use

• You can complete the task on your own and the user has not explicitly asked to invoke another agent
• It is just a normal Q&A that does not require a specialized agent
• Information is insufficient -- you should ask the user for clarification first
• You just received a message from Agent B -- **do not call Agent B again** to avoid loops

Decision Rules

1. **If the user explicitly requests invoking another agent, prioritize following the request** 2. **Otherwise, if you can do it yourself, do not invoke another agent** 3. **Check agents before invoking -- do not guess IDs** 4. **When context continuation is needed, you must pass `--session-id`** 5. **Do not call back the source agent**

---

Most Common Commands

1) First Query Available Agents

qwenpaw agents list

2) Start a New Conversation (Real-time Mode)

qwenpaw agents chat \
  --from-agent <your_agent> \
  --to-agent <target_agent> \
  --text "[Agent <your_agent> requesting] ..."

3) Submit a Complex Task (Background Mode)

**Complex tasks** include: data analysis, report generation, batch processing, external API calls, etc.

qwenpaw agents chat --background \
  --from-agent <your_agent> \
  --to-agent <target_agent> \
  --text "[Agent <your_agent> requesting] ..."

**Output**:

[TASK_ID: xxx-xxx-xxx]
[SESSION: ...]

4) Query Background Task Status

qwenpaw agents chat --background --task-id <task_id>

**Important**: Do not query frequently! After submitting a task: 1. **Do not block** - Continue handling other tasks or work 2. **Wait a reasonable time before querying** - Choose based on task complexity:

• Simple analysis: query after 10-20 seconds
• Complex analysis: query after 30-60 seconds
• Batch processing: query after 1-3 minutes

3. **During the wait** - You can reply to the user, handle other requests, or execute other tasks

5) Continue an Existing Conversation

qwenpaw agents chat \
  --from-agent <your_agent> \
  --to-agent <target_agent> \
  --session-id "<session_id>" \
  --text "[Agent <your_agent> requesting] ..."

**Key points**:

• Not passing `--session-id` = new conversation
• Passing `--session-id` = continue conversation (context preserved)
• Use `--background` for complex tasks; record the task_id after submission

---

Task Mode Selection

Real-time Mode vs Background Mode

| Task Type | Mode to Use | Command | |-----------|-------------|---------| | Simple quick query | Real-time mode | `qwenpaw agents chat` | | Complex task (data analysis, batch processing, etc.) | Background mode | `qwenpaw agents chat --background` |

**Examples of complex tasks**:

• Analyzing large amounts of data or log files
• Generating detailed reports
• Batch processing files (10+ files)
• Calling slow external APIs
• Independent tasks that need parallel execution

**Decision criteria**: If you are unsure how long a task will take, or if the task is complex, prefer background mode.

---

Minimal Workflow

Real-time Mode Workflow

1. Determine whether another agent is needed, or whether the user explicitly requested it
2. qwenpaw agents list
3. qwenpaw agents chat to start a conversation
4. Record [SESSION: ...] from the output
5. Include --session-id when context continuation is needed later

Background Mode Workflow

1. Determine whether the task is complex (data analysis, report generation, etc.)
2. qwenpaw agents list
3. qwenpaw agents chat --background to submit the task
4. Record [TASK_ID: ...] from the output
5. Continue handling other work
6. Wait a reasonable time (30-60 seconds) before querying status
7. Use --background --task-id to query results

---

Key Rules

Required Parameters

`qwenpaw agents chat` must include all of the following:

• `--from-agent`
• `--to-agent`
• `--text`

Identity Prefix

Messages should begin with the following prefix:

[Agent my_agent requesting] ...

Session Reuse

The first call will return:

[SESSION: your_agent:to:target_agent:...]

For subsequent follow-ups, you must copy this session_id and pass it via `--session-id`.

---

Brief Examples

User Explicitly Requests Invoking Another Agent

qwenpaw agents list

qwenpaw agents chat \
  --from-agent scheduler_bot \
  --to-agent finance_bot \
  --text "[Agent scheduler_bot requesting] User explicitly asked to consult finance_bot. Please answer what pending financial tasks are there."

New Conversation

qwenpaw agents chat \
  --from-agent scheduler_bot \
  --to-agent finance_bot \
  --text "[Agent scheduler_bot requesting] What pending financial tasks are there today?"

Continue Conversation

qwenpaw agents chat \
  --from-agent scheduler_bot \
  --to-agent finance_bot \
  --session-id "scheduler_bot:to:finance_bot:1710912345:a1b2c3d4" \
  --text "[Agent scheduler_bot requesting] Expand on item 2"

---

Common Mistakes

Mistake 1: Not checking agents first

Do not guess agent IDs. First run:

qwenpaw agents list

#