Huawei Cloud Resource Query

⚠️ Execution Method (Must Read): This skill executes queries via local Python scripts. Using hcloud, openstack, or other CLI tools or direct API calls is prohibited.

• Query scripts are located under the skill directory scripts/<service_category>/ (e.g., scripts/as/list_scaling_groups.py)
• All scripts and environment check scripts are inside the skill package. You must use skill action=exec to execute them. Do not run them directly in a shell.
• For specific script paths and parameters, refer to references/<service>/guide.md
• Do not attempt hcloud, openstack, curl IAM, or any other CLI/API methods. This skill does not depend on those tools.
• All paths are relative to the skill directory, which is the directory where this SKILL.md is located.

Overview

This skill is a standalone read-only query skill that uses local Python scripts to call the Huawei Cloud Python SDK to query Huawei Cloud resources, available specifications, and existing resource information.

This skill is applicable to the following scenarios:

1. Query available cloud resource specifications in a specific region
2. Query available images for a specific OS type
3. Query disk types and existing disk information
4. Query existing resources and their key attributes
5. Query resources that were not created via Terraform or other IaC tools
6. Prepare real parameters for automation configuration, resource verification, or environment inventory
7. Obtain reusable information such as resource IDs, names, specifications, images, networks, disks, etc.

This skill does NOT handle the following:

1. Creating resources
2. Modifying resources
3. Deleting resources
4. Guessing or fabricating information that has not been queried

---

Capability Scope

This skill provides query capabilities through categorized scripts in the scripts directory, and usage instructions through categorized guides in the references directory.

Capabilities provided by this skill include:

1. Query resource lists
2. Query individual resource details
3. Query selection information such as available specifications, images, and disk types
4. Query key identifiers and dependency relationships of existing resources

Out of Scope (Not Supported)

To avoid misleading users, the following scenarios are explicitly NOT supported by this skill. If a user asks for any of them, directly state that it is unsupported and do not attempt to return unreliable results:

1. Querying raw metric data points — There is no script wrapping ShowMetricData / BatchListMetricData / ListMetrics. The skill cannot retrieve time-series values of metrics (e.g., "RDS CPU utilization over the last 1 hour", "EVS disk throughput in the past 24 hours").
2. Service-level metric value queries — Although CES aggregates metrics from services such as SYS.RDS, SYS.DCS, SYS.DMS, SYS.EVS, SYS.ELB, SYS.ECS, etc., this skill does not provide scripts to fetch the actual metric values of these namespaces. The non-exhaustive list of services whose metric data cannot be queried via this skill:
   • RDS (Relational Database Service) — SYS.RDS
   • DCS (Distributed Cache Service) — SYS.DCS
   • DMS (Distributed Message Service) — SYS.DMS
   • EVS (Elastic Volume Service) — SYS.EVS
   • ELB (Elastic Load Balance) — SYS.ELB
   • ECS (Elastic Cloud Server) — SYS.ECS
   • Other SYS.* namespaces not listed above are likewise unsupported for metric-value queries
3. Services other than CES and EPS — Scripts only exist under scripts/ces/ and scripts/eps/. Any service that does not appear in references/ces/guide.md or references/eps/guide.md is unsupported.
4. Creating / modifying / deleting resources — Write operations are out of scope.

Note: For querying actual monitoring metric data points, use the Huawei Cloud console, CES API directly, or a dedicated metric-data skill if available.

---

Usage Principles

Important: Script paths executed within this skill are all relative to the skill directory, which is the directory where this SKILL.md is located.

1. This skill only performs queries; it does not perform any write operations
2. Prioritize using explicitly specified region, project, AZ, resource name, resource ID, etc. provided by the user
3. Query results must be based on actual API responses; do not infer from experience
4. Returned results should prioritize retaining key fields for subsequent reuse
5. When the result set is large, narrow the scope first by region, name, id, status, tag, etc.
6. If there is no corresponding script or guide for the current resource type, clearly state that it is unsupported; do not return unreliable results
7. If the user has not provided necessary scope information and there are no default values in the environment, confirm the details before executing the query
8. Execute directly according to guide.md; do not read the script contents in the scripts directory
9. Cache results when the output is large
10. You must run -h to view usage before executing each script
11. Do not invent script names; execute according to the script names in guide.md. If a script name is not in guide.md, it means it is not supported

---

Prerequisites

Before use, you must run the environment check script to complete environment validation and dependency installation in one step:

• Linux / macOS: skill action=exec: bash skill://scripts/check_env.sh
• Windows: skill action=exec: powershell -ExecutionPolicy Bypass -File skill://scripts/check_env.ps1

Windows note: Do not use && to chain commands (PowerShell 5.x does not support it); use semicolons if you need to change directories first.

The script will check in order: Python >= 3.6 → install dependencies → validate SDK → validate credentials → validate service availability. If the environment check fails, fix the issues before proceeding with other scripts.

Environment Variables:

Do not output the values of the above environment variables. For additional parameters required by other resource scripts (availability zone, enterprise project, etc.), see the corresponding guide.md.

---

Execution Flow

When this skill is invoked, you must follow these steps. Do not wait for the user to prompt again:

Step 1: Environment Preparation

Run the environment check script to ensure dependencies are installed and credentials are configured:

• Linux / macOS: skill action=exec: bash skill://scripts/check_env.sh
• Windows: skill action=exec: powershell -ExecutionPolicy Bypass -File skill://scripts/check_env.ps1

If the environment check fails, fix the issues as prompted and re-run until it passes.

Step 2: Identify and Execute Query Scripts

1. Based on the user's query intent, read references/<service>/guide.md to determine the script path and parameters to execute
2. First run -h to view script usage:
   • Linux / macOS: skill action=exec: skill://.venv/bin/python3 skill://scripts/<service>/<script>.py -h
   • Windows: skill action=exec: skill://.venv/Scripts/python3.exe skill://scripts/<service>/<script>.py -h
3. Assemble parameters based on user needs and execute the script:
   • Linux / macOS: skill action=exec: skill://.venv/bin/python3 skill://scripts/<service>/<script>.py <parameters>
   • Windows: skill action=exec: skill://.venv/Scripts/python3.exe skill://scripts/<service>/<script>.py <parameters>
4. Format the results and return them to the user

Important:

• All scripts and environment check scripts are inside the skill package. You must use skill action=exec to execute them. Do not run them directly in a shell.
• The venv is automatically created by the check_env script. On Linux/macOS, Python is located at .venv/bin/python3; on Windows, at .venv/Scripts/python3.exe
• Do not use python3 directly to execute scripts
• Do not read the source code of scripts in the scripts directory; just follow the instructions in guide.md
• Cache results when the output is large
• The --project_id parameter is optional; if not provided, it is automatically obtained via IAM API based on region

---

Directory Structure

The directory conventions are as follows (all paths are relative to the skill directory):

1. scripts/<resource_category>/ contains the Python query scripts for corresponding resources. You do not need to read the script contents; just execute the scripts according to the usage instructions in guide.md
2. references/<resource_category>/guide.md contains the usage guide for corresponding resources
3. Each script is responsible for only one clear, single query action
4. Each resource category must maintain at least one guide.md to document script capabilities, parameters, and usage

---

Parameter Confirmation

Before executing query scripts, confirm the following parameters:

For script-specific parameters, see references/<service>/guide.md.

---

Output Format

Query results are output in JSON format and contain the following common fields:

• total: Total number of matched resources
• items: Resource list, each resource contains key fields such as id, name, status, etc.
• Specific fields vary by resource type; see individual guide.md for details

---

Verification Methods

1. Run the environment check script to confirm dependencies and credentials are available
2. Use the -h parameter to view script usage and confirm parameters are correct
3. Execute queries against known resources and compare with console data to verify result accuracy
4. Check whether the returned total count is reasonable

---

Best Practices

1. Narrow the query scope first (specify region, availability zone, etc.) to avoid returning too much data
2. Use --help to view the complete list of supported parameters for a script
3. Cache large query results locally to avoid repeated requests
4. When multiple resource information is needed, query in dependency order (e.g., query VPC first, then subnets)
5. When a script fails, check environment variables and network connectivity first

---

Reference Documentation

• Query script usage guides for each service: references/<service>/guide.md

---

Notes

1. This skill only provides read-only query capabilities; it does not perform any write operations
2. Do not output the values of environment variables such as HW_ACCESS_KEY, HW_SECRET_KEY, etc.
3. All scripts must be executed via skill action=exec; do not run them directly in a shell
4. Do not guess script names; strictly execute according to the names in guide.md
5. You must run the environment check script before querying
6. When using temporary AK/SK, you need to set HW_SECURITY_TOKEN