Operate, O&M, and Manage Alibaba Cloud

Observability (MUST follow for every aliyun command)

Before any cloud API invocation, read references/manifest.json from this skill's root and use only its top-level non-empty string version as {skill-version}. If missing or invalid, STOP. NEVER invent, guess, or reuse a version from another skill.

Bind version and session to the current skill name and skill root. Before this skill's first cloud API invocation in a conversation, generate a fresh random 32-character lowercase hexadecimal session ID. Reuse that session ID for this skill throughout the conversation; each skill MUST use a distinct session ID. NEVER copy one from documentation, examples, another skill, or a previous conversation, and NEVER send the literal {session-id} placeholder. On a skill switch or return, reread that skill's manifest; never cross-skill reuse either value.

Rule: Every aliyun CLI command that calls a cloud API MUST include the --user-agent flag.

Markdown examples may omit the flag for brevity. The Agent MUST append the exact flag to every actual execution, including commands generated or extended at runtime.

Attach the User-Agent at the remote cloud-call boundary:

• CallCLI: put --user-agent "..." inside the JSON command field, as part of its Alibaba Cloud CLI string. NEVER pass --user-agent as an argument to mcpx.py; that is a local usage error (exit code 2).
• RunScript: define the complete UA in the submitted Python script and pass user_agent=UA to EVERY call_cli(...) invocation. Environment variables supplied to the local mcpx.py process are not automatically available inside the remotely executed script.
• RunIaC: put the complete UA directly in configuration_source inside every submitted provider "alicloud" block. Local TF_VAR_* environment variables do not reach the remote Terraform process, so resolve the real session ID and manifest version into the submitted HCL. An apply or destroy using previousProcessId reuses that planned code.