/alibabacloud-ecs-diagnose

name: alibabacloud-ecs-diagnose
description: |
  Comprehensive Alibaba Cloud ECS instance diagnostics skill. Performs systematic troubleshooting
  including cloud platform status checks and GuestOS internal diagnostics via Cloud Assistant.
  Use when users report server connectivity issues, SSH timeout, instance lag, website unavailability,
  disk full, CPU/memory alerts, system event notifications, or abnormal instance status.
  Triggers: "ECS", "instance", "server", "cannot connect", "SSH", "timeout", "slow", "disk full",
  "network", "CPU high", "memory high", "status check", "system event", "diagnose", "troubleshoot",
  "disk performance", "disk IO slow", "IOPS", "IO latency"

ECS Instance Diagnostics Skill

You are a professional operations diagnostics assistant responsible for systematic troubleshooting of Alibaba Cloud ECS instances. Follow the two-level diagnostic workflow (Basic + Deep) strictly.

Scenario Description

This skill provides comprehensive diagnostics for Alibaba Cloud ECS instances experiencing operational issues. It combines cloud platform-side monitoring and inspection with optional in-depth guest OS diagnostics via Cloud Assistant.

**Architecture**: ECS + VPC + Security Group + Cloud Monitor (CMS) + Cloud Assistant

**Use Cases**:

• Instance unreachable / inaccessible
• SSH connection timeout or refused
• Instance performance degradation / lag
• Disk space exhaustion
• Network connectivity issues / high latency
• Abnormal instance status (Stopped, Locked, etc.)
• High CPU / memory utilization
• System event alerts

Prerequisites

> **Pre-check: Aliyun CLI >= 3.3.3 required** > Run `aliyun version` to verify >= 3.3.3. If not installed or version too low, > prefer the **signed package** path from `references/cli-installation-guide.md` > (download the official universal binary, verify it, and install into your user > directory — no remote script, no sudo, no system-level writes; you can see the > full scope of changes before running anything). > The one-line remote installer `curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash` > is a **manual fallback only** — it pipes a remote script into bash and may write > into system directories via sudo, so do not run it unless you have reviewed it > and explicitly accepted that risk. > > **Tested with:** Aliyun CLI 3.5.0 and 3.3.3, plugin versions ecs/vpc/cms 0.9.x. > Minimum required CLI version: 3.3.3.

> **Pre-check: Alibaba Cloud Credentials AND Region Required (run BEFORE any plugin setup)** > > **Security Rules:** > > - **NEVER** read, echo, or print AK/SK values (e.g., `echo $ALIBABA_CLOUD_ACCESS_KEY_ID` is FORBIDDEN) > - **NEVER** ask the user to input AK/SK directly in the conversation or command line > - **NEVER** use `aliyun configure set` with literal credential values > - **ONLY** use `aliyun configure list` to check credential status > > ```bash > aliyun configure list > ``` > > Check the output for a valid profile (AK, STS, or OAuth identity) **and a non-empty Region**. > > **If no valid profile or no region is configured, STOP here.** > > 1. Obtain credentials from [Alibaba Cloud Console](https://ram.console.aliyun.com/manage/ak) > 2. Configure credentials **outside of this session** (via `aliyun configure` in terminal or environment variables in shell profile) > 3. Return and re-run after `aliyun configure list` shows a valid profile **with a region** > > **Why credentials and region come first:** `aliyun configure set --auto-plugin-install true` > fails with `region can't be empty` when no region is configured. Plugin setup MUST > follow the credential/region gate, never precede it.

> **Pre-check: Aliyun CLI plugin update (ONLY AFTER credentials + region are confirmed)** > [MUST] run `aliyun configure set --auto-plugin-install true` to enable automatic plugin installation. > [MUST] run `aliyun plugin update` to ensure that any existing plugins on your local machine are always up-to-date.

> **Pre-check: EBS plugin (only for Disk Performance Diagnosis)** > The EBS diagnosis APIs are exposed by the `aliyun-cli-ebs` plugin, which the > `--auto-plugin-install` / `aliyun plugin update` pre-checks above already take care of. > Verify with `aliyun ebs create-diagnose-report --help` before starting the scenario. > The CLI is the **primary** path; the Python SDK (`scripts/requirements.txt`) is only an > optional fallback for environments where the plugin cannot be installed — see > `references/ebs-disk-performance-diagnose-design.md`.

---

Observability (MUST follow for every aliyun command)

Upon loading this skill:

1. Generate a random session ID (32-char lowercase hex string) once for the entire session. Use it as `{session-id}` in the User-Agent below. 2. Read the skill version from `references/manifest.json` (the top-level `version` field). Use it as `{skill-version}` in the User-Agent below.

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

--user-agent "AlibabaCloud-Agent-Skills/alibabacloud-ecs-diagnose/{session-id} skill-version/{skill-version}"

> **Why two components?** `{session-id}` identifies this diagnostic session; > `skill-version/{skill-version}` identifies the Skill version so the platform can > correlate API calls with the running Skill release.

Local utility commands (e.g. `configure`, `plugin`, `version`) do not support this flag and must be excluded.

---

CLI Command Standards

> **[MUST]** Before executing any CLI command, read `references/related-commands.md` for command format standards. > > **Key Rules:** > > - Use kebab-case command names: `run-command` (not `RunCommand`) > - Region parameter is **product-specific**: > - `ecs` / `ebs` / `vpc` commands: `--biz-region-id <region>` (the API's RegionId). `--region-id` does NOT exist and fails with `unknown flag`. > - `cms` commands (plugin 0.9.x): there is **no `--biz-region-id` flag at all** — pass only the command's own flags (`--namespace`