/alibabacloud-wuying-console

name: alibabacloud-wuying-console
description: Query and manage Alibaba Cloud WUYING resources from a local agent through the official Aliyun CLI product plugins. Use for cloud computers, cloud browsers, application delivery groups, office sites, users, policies, images, terminals, sessions, reports, and local WUYING CLI setup or troubleshooting. Do not use for browser-only console navigation or unrelated Alibaba Cloud products.

Alibaba Cloud WUYING Console

Operate WUYING through the official `aliyun` CLI and configured official WUYING product plugins. Treat each plugin's live command schema as authoritative. This skill adds cross-product discovery, safety, and agent-friendly execution rules without forking Aliyun CLI or maintaining a scenario-to-Action map.

The configured product scope is `ecd`, `appstream-center`, `eds-user`, `wyota`, and `wss`. A product is executable only when its official plugin is installed and reported as ready by the environment check.

Prerequisites

| Dependency | Minimum | Purpose | |---|---:|---| | Python | 3.10 | Run the bundled environment, catalog, and search helpers | | Aliyun CLI | 3.5.0 | Authenticate and execute official product-plugin commands | | Official WUYING plugins | See [products.json](references/products.json) | Provide the live OpenAPI command schemas |

The bundled scripts use only the Python standard library. They have no third-party package dependency; see [scripts/requirements.txt](scripts/requirements.txt).

Observability

At the start of one user workflow, generate one cryptographically random 32-character lowercase hexadecimal session ID, load the published Skill version from the manifest, and reuse both values for every cloud API command in that workflow:

export SKILL_SESSION_ID="$(python3 -c 'import secrets; print(secrets.token_hex(16))')"
export SKILL_VERSION="$(python3 -c 'import json; print(json.load(open("references/manifest.json"))["version"])')"

Do not regenerate the session ID between discovery, execution, verification, retries, or follow-up questions in the same workflow. Every `aliyun` command that calls a WUYING cloud API MUST include:

--user-agent "AlibabaCloud-Agent-Skills/alibabacloud-wuying-console/${SKILL_SESSION_ID} skill-version/${SKILL_VERSION}"

Local utility and metadata commands such as `aliyun version`, `aliyun configure`, `aliyun plugin`, `aliyun ... --help`, and `aliyun ... --help-all` do not call a business API and do not require this flag.

Start Every Task

1. Create and retain `SKILL_SESSION_ID` as described in Observability. 2. Run `python3 scripts/check_environment.py` from this skill directory. 3. If Aliyun CLI is missing or older than 3.5.0, stop and request authorization before installing or upgrading it. Use an official CLI installation path such as `brew install aliyun-cli` on macOS. For an existing installation, use `aliyun upgrade`, then rerun the environment check. 4. If the result is `blocked`, stop and follow the returned remediation. Do not install software, start OAuth login, or change profiles without user authorization. 5. If the result is `partial`, continue only when the requested operation belongs to a product in `ready_products`. If it requires an `unavailable_products` entry, explain which official plugin is missing and request authorization before installing it. 6. If `updates_available` is non-empty, tell the user which installed plugins have newer stable versions. Do not update automatically. A compatible installed version may continue to run unless the requested command is absent or the user authorizes the update. 7. If the result is `needs_auth`, explain that local authentication is missing and follow [authentication.md](references/authentication.md). 8. Convert the business intent into a short English search phrase and search the generated catalog:

   python3 scripts/search_command_catalog.py "<business keywords>"

The catalog mirrors every command exposed by the configured plugin versions; it is not a hand-maintained scenario map or API allowlist. Search again with alternative business terms when the first result is weak. 9. Before composing arguments, inspect the live schema for the chosen command:

   aliyun <product> <command> --api-version <version> --help

10. Use the product and version listed for that command in the catalog. Always pass `--api-version` explicitly because plugin defaults can expose a different command set.

Orchestration Logic

This is a schema-driven workflow, not a list of hard-coded console scenarios:

1. **Prepare**: verify CLI, authentication, plugin availability, and updates. 2. **Discover**: search the generated cross-product command catalog. 3. **Resolve**: inspect live help and query authoritative resources for required IDs. 4. **Gate**: classify risk and obtain confirmation for mutations or destructive actions. 5. **Execute**: call the smallest matching OpenAPI command with explicit API version, `--cli-ai-mode`, and the workflow User-Agent. 6. **Verify**: inspect the response and, after mutations, query the resulting state.

If any stage cannot establish an authoritative product, command, parameter, target, or permission, stop at that stage and return a focused remediation instead of guessing or falling through to a different product.

Resolve the Operation

• Match the user's intent to catalog commands using the official command name and description across all configured products. Do not maintain or infer a fixed user-phrase-to-Action mapping.
• Inspect live help for the strongest candidates when names or descriptions are similar. Compare required parameters and response meaning before choosing. If the official schemas still leave a material ambiguity, ask a focused question before acting.
• Prefer the latest API version listed for the exact command, unless the user requires an older contract.
• Read live help immediately before execution because pl