How do I install the Multi Agent Collaboration skill?

Run npx skillmds@latest add gabrielmoreira/multi-agent-collaboration in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Multi Agent Collaboration skill do?

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. It is listed under AI & ML on SkillMD.

Is Multi Agent Collaboration safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Multi Agent Collaboration?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Multi Agent Collaboration free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Multi Agent Collaboration?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Multi Agent Collaboration by gabrielmoreira

Name: Multi Agent Collaboration
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

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

If the user explicitly requests invoking another agent, prioritize following the request
Otherwise, if you can do it yourself, do not invoke another agent
Check agents before invoking -- do not guess IDs
When context continuation is needed, you must pass --session-id
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:

Do not block - Continue handling other tasks or work
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
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

Mistake 2: Wanting to continue a conversation but not passing session-id

This will create a new conversation, losing context.

Mistake 3: Calling back the source agent

If you just received a message from Agent B, do not call Agent B again.

Optional Commands

View Existing Sessions

qwenpaw chats list --agent-id <your_agent>

Streaming Output

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

JSON Output

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

Full Parameter Reference

qwenpaw agents list

Parameters:

--base-url (optional): Override the API address

No required parameters -- just run it directly.

qwenpaw agents chat

Required parameters (real-time mode):

--from-agent: Sender agent ID
--to-agent: Target agent ID
--text: Message content

Background task parameters:

--background: Background task mode
--task-id: Query task status (used together with --background)

Optional parameters:

--session-id: Reuse session context (copy from previous output)
--new-session: Force create a new session (even if session-id is passed)
--mode: stream (streaming) or final (complete, default)
--timeout: Timeout in seconds (default 300)
--json-output: Output full JSON instead of plain text
--base-url: Override the API address

Background Task Mode Details

When to Use Background Mode?

When the task is a complex task, use --background to submit it to the background:

Should use background mode:

Data analysis (analyzing logs, computing statistics)
Report generation (generating long reports or documents)
Batch processing (processing multiple files)
External API calls (calling slow services)
Complex tasks with uncertain duration

Does not need background mode:

Simple quick queries
Tasks that are clearly going to complete quickly

Background Task Examples

Submitting a Complex Task

qwenpaw agents chat --background \
  --from-agent scheduler \
  --to-agent data_analyst \
  --text "[Agent scheduler requesting] Analyze user behavior in /data/logs/2026-03-26.log and generate a detailed report"