alibabacloud-openagent-chat

Installation
SKILL.md

OpenAgent

Send the user's cloud goal to OpenAgent, continue the same conversation, and return its verified answer. Cloud-side tools perform the business work; this client provides the conversation channel.

Connect once

Resolve scripts/openagent.py relative to this skill, then invoke its absolute path with the host's Python 3.11 or later. Run bootstrap if dependencies need preparation; it installs locked dependencies outside the skill. Keep using this entry from any working directory. Use version to read the installed version without cloud access.

Before accessing an account, run setup status. Reuse an existing valid connection without asking again. Otherwise, ask once for the OpenAgent service region and credential source, reusing choices already explicitly made. The service regions are Hangzhou (cn-hangzhou) and Singapore (ap-southeast-1); this choice is independent of the resource regions in a task. Identify this as OpenAgent Skill connection configuration. Save the choices with setup configure; no separate configuration-plan approval is needed. Read setup for the JSON format and credential guidance.

Connection setup only saves local connection settings. The endpoint follows the selected region. This skill does not read, cache, compare, or change cloud account controls or model-key settings. It does not install its own updates. Connection changes require an explicit user selection; never switch credential sources or regions to work around an error.

Use one conversation for related work

Run task new once in a new host conversation and retain its returned local_session UUID. Send the request with task ask --local-session <local-uuid> --text <request>. Reuse the UUID for follow-ups and recovery; independent host conversations use separate UUIDs. Do not select a global last-used conversation or invent identifiers. For an existing cloud conversation explicitly selected by the user, use task continue. See tasks for inspection, history, cancellation, and recovery.

Preserve the user's scope, context, desired outcome, and constraints in every message, including “query only”, “planning only”, or “submit for review without execution”. Ask only for missing details that change the work. Permission to send a task does not authorize every resource action it might propose.

Read the actual answer and status. Preserve requested identifiers, fields, counts, and complete resource lists; a summary must not replace requested detail. Distinguish proposals, executed changes, pending decisions, and unknown outcomes. Do not infer success from a completed Run alone. Internal tool events are handled by the client and do not authorize local execution.

Installs
2
GitHub Stars
300
First Seen
Oct 20, 2026