Best for
- Should Use
- Should Not Use
- You need another agent's expertise, judgment, or second opinion
agentscope-ai/QwenPaw/src/qwenpaw/agents/skills/chat_with_agent-en/SKILL.md
Use this skill when you need to consult another agent, ask for help, or involve a specific agent the user asked for.
Decision brief
Use this skill when you need to consult another agent, ask for help, or involve a specific agent the user asked for.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/agentscope-ai/QwenPaw --skill "src/qwenpaw/agents/skills/chat_with_agent-en"Inspect the Agent Skill "chat_with_agent" from https://github.com/agentscope-ai/QwenPaw/blob/2f34db2d7852f292e082953005e0b13b03fee3e3/src/qwenpaw/agents/skills/chat_with_agent-en/SKILL.md at commit 2f34db2d7852f292e082953005e0b13b03fee3e3. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Follow this flow strictly when using this skill:
Use this skill when you need to ask another agent a question, seek help, request a plan, request a review, request decision support, or engage in any form of communication. If the user explicitly asks to talk to a specific agent, you should also use this skill.
You need another agent's expertise, judgment, or second opinion
You can complete the task yourself and the user has not explicitly asked to involve another agent
1. If the user explicitly requests a specific agent, follow that request — but still look up the agent first; do not guess the ID 2. If you can complete the task yourself, do not call another agent 3. When continuing a conversation, you must pass sessionid 4. By default, prefer…
Permission review
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 89/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 33,124 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Use this skill when you need to ask another agent a question, seek help, request a plan, request a review, request decision support, or engage in any form of communication. If the user explicitly asks to talk to a specific agent, you should also use this skill.
session_idlist_agents() and chat_with_agent(...) for foreground conversations — do not resort to other methodssubmit_to_agent(...) to submit it, then check_agent_task(...) to check the statusFollow this flow strictly when using this skill:
list_agents() and chat_with_agent(...) built-in toolslist_agents() to view the currently available agents, and select one by extracting its IDchat_with_agent(...) to initiate a foreground conversation. Key parameters include:to_agent: the target agent's ID (note: this is the ID, not the name)text: what you want to say to the target agentsession_id: (optional) if you need multiple rounds of conversation with the same agent, pass the same session_id starting from the second round to maintain context continuitytimeout: (optional) estimated time needed for the foreground wait, to avoid premature timeoutssubmit_to_agent(...): submit a background task — only requires to_agent, text, and optionally session_idcheck_agent_task(...): check task status by task_id; returns the final result when completelist_agents()
chat_with_agent(
to_agent="<target_agent_id>",
text="[Agent <your_agent_id> requesting] I need your help determining the approach for this issue.",
)
chat_with_agent(
to_agent="<target_agent_id>",
text="[Agent <your_agent_id> requesting] Please continue expanding on point 2 based on the previous conclusion.",
session_id="<previous_session_id>",
)
submit_to_agent(
to_agent="<target_agent_id>",
text="[Agent <your_agent_id> requesting] Please complete this longer task in the background.",
)
check_agent_task(
task_id="<task_id>",
)
[Agent <your_agent_id> requesting]
This helps the other agent clearly identify who is speaking, improving communication efficiency and accuracy.
Reuse sessions wisely: if you need multiple rounds of conversation with the same agent, be sure to pass the same session_id to maintain context continuity. Otherwise, each call is treated as a new conversation, and the other agent may not correctly understand your needs. You can obtain the session_id from the first round's response, for example:
[SESSION: xxx]
where xxx is the session_id value. This value is typically system-generated and has a long, unique format. Save this session_id and continue using it in subsequent conversations with the same agent.