Build and debug Python applications using AgentScope 2.x. Consult this skill for AgentScope APIs, agent tools, multi-agent orchestration, and agent service deployment.
日本語の概要は準備中です。原文の説明を表示しています。
For external plan request scenarios, guides the Agent to request a clear, actionable, step-by-step plan from a stronger Agent via list_agents and chat_with_agent, emphasizing that the plan is executed by the requester, not by the consulted Agent.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Use this Skill when you need to make an external plan request to a stronger Agent.
The goal of this Skill is not to outsource a task, but rather to:
How to invoke:
list_agents() to check available Agentschat_with_agent(...) to request the stronger Agent to "make a plan"text, explicitly include the prompt: only provide a step-by-step executable plan, do not executesession_idRecommended invocation skeleton:
list_agents()
chat_with_agent(
to_agent="<stronger_agent>",
text="[Agent <auto> requesting] Please help me create an execution plan for the following task. You do not need to execute the task -- just output clear, actionable steps in order.",
)
This Skill handles one thing only:
If what you truly need is a "plan", use this Skill. If what you need is a final answer, architectural judgment, review conclusion, or direct execution, do not misuse this Skill.
The following scenarios are suitable for making an external plan request:
Do not use this Skill in the following situations:
When calling chat_with_agent(...), clearly state:
Execute in this order by default:
list_agents() to confirm available stronger Agentschat_with_agent(...) to request the generation of an execution planWhen requesting the plan, explicitly state:
Common parameters for chat_with_agent:
to_agent: Target Agent IDtext: Request content; must explicitly state "only output the plan, do not execute the task"session_id: Optional; pass this to continue an existing conversationNotes:
base_url generally does not need to be provided; the tool will automatically resolve the current API addresssession_id will automatically create a new sessionPlease help me create an execution plan for the following task. You do not need to execute the task itself -- just output the plan.
Task: [What needs to be done]
Goal: [What the final outcome should be]
Constraints:
Plan requirements:
Output format: [e.g., Output 5-8 numbered steps, 1-3 sentences each]
Example:
chat_with_agent(
to_agent="strong_reasoner",
text="""
Please help me create an execution plan for the following task.
You do not need to execute the task itself -- just output the plan.
Task:
Modify a multi-module feature.
Goal:
Complete the change with low risk and avoid missing integration points.
Constraints:
- Minimize rework
- Include verifiable intermediate checkpoints
Plan requirements:
1. Break it down into actionable steps
2. Indicate the recommended order
3. Mark key dependencies and checkpoints
4. Include verification methods where possible
Output format:
Please output 3-5 numbered steps, each as specific as possible.
""",
)
For follow-up conversations:
chat_with_agent(
to_agent="strong_reasoner",
text="Based on the previous plan, please further refine the checkpoints for steps 3 and 4. Still only provide the plan -- do not execute the task.",
session_id="<previous_session_id>",
)
Treat the stronger Agent's reply as "execution plan input", not as "the task is already done".
What you should do:
Do not deliver the plan as-is to the user as a final result, unless the user specifically asked for the plan itself.
A qualified plan should at least meet the following criteria:
If what you receive is vague advice such as "first analyze, then implement, then test", it is not sufficient -- follow up to request refinement.
When you lack an execution path, request a plan first. The plan must be step-by-step, specific, and actionable. The consulted Agent is responsible for producing the plan, not for executing it. After receiving the plan, the requester executes it themselves.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Build and debug Python applications using AgentScope 2.x. Consult this skill for AgentScope APIs, agent tools, multi-agent orchestration, and agent service deployment.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user explicitly wants to connect to a running Chrome browser, scan local CDP ports, specify a `cdp_port`, or share a single browser across multiple agents/tools. By default, browser_use already launches the browser using managed CDP; if the user does not want to expose browser history, cookies, or other sensitive data, recommend using `private_mode=true` instead.
日本語の概要は準備中です。原文の説明を表示しています。
当用户明确希望连接到已运行的 Chrome 浏览器、扫描本地 CDP 端口、显式指定 `cdp_port`,或让多个 agent / 工具共享同一个浏览器时,使用本 skill。当前 browser_use 默认已使用 managed CDP 启动浏览器;如果用户不希望暴露浏览器历史、Cookies 等敏感信息,推荐改用 `private_mode=true` 的隐私模式。
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user needs to control the browser launch mode for browser_use. By default, browser_use launches the local Chrome/Chromium using managed CDP; `headed` controls whether the window is visible, and `private_mode` controls whether CDP is disabled in favor of Playwright.
日本語の概要は準備中です。原文の説明を表示しています。
当用户需要控制 browser_use 的浏览器启动方式时,使用本 skill。当前 browser_use 默认使用 managed CDP 启动本地 Chrome/Chromium;`headed` 控制是否显示窗口,`private_mode` 控制是否禁用 CDP、改走 Playwright,`browser_args` 传入额外的 Chromium 启动参数,`executable_path` 指定自定义浏览器可执行文件路径。
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to proactively send a one-way message to a user/session/channel, usually only when the user explicitly asks to send to a channel/session or when proactive notification is needed. First query sessions with qwenpaw chats list, then push with qwenpaw channels send.
日本語の概要は準備中です。原文の説明を表示しています。