/alibabacloud-cms-dataset

name: alibabacloud-cms-dataset
description: |
  Alicloud CMS Dataset lifecycle management and querying skill.
  Covers listing, inspecting, creating, updating, deleting datasets and executing dataset queries
  via the aliyun CLI (CMS API version 2024-03-30).
  Triggers: "CMS dataset", "数据集", "创建数据集", "查询数据集", "dataset 查询",
  "ExecuteQuery", "CreateDataset", "GetDataset", "ListDatasets", "UpdateDataset", "DeleteDataset".

CMS Dataset Lifecycle Management and Querying

Manage CloudMonitor (CMS) dataset resources — list, inspect, create, update, delete datasets and execute dataset-level queries — using the `aliyun` CLI.

**Architecture**: `CMS Workspace + Dataset (Schema + Fields) + ExecuteQuery`

---

Installation

Install Aliyun CLI

Run `aliyun version` to verify if version >= `3.3.3`. If not installed or outdated, follow the doc [references/cli-installation-guide.md](references/cli-installation-guide.md) to install or update.

Ensure plugins up-to-date

> [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 are always up-to-date.

---

AI-Mode Lifecycle

> At the **start** of the Core Workflow (before any CLI invocation): > **[MUST] Enable AI-Mode** — AI-mode is required for Agent Skill execution. > ```bash > aliyun configure ai-mode enable > aliyun configure ai-mode set-user-agent --user-agent "AlibabaCloud-Agent-Skills/alibabacloud-cms-dataset" > ```

> **[MUST] Disable AI-Mode at EVERY exit point** — Before delivering the final response for ANY reason, always disable AI-mode first. This applies to ALL exit paths: workflow success, workflow failure, error/exception, user cancellation, session end, or any other scenario where no further CLI commands will be executed. > ```bash > aliyun configure ai-mode disable > ```

---

Authentication

> **Pre-check: Alibaba Cloud Credentials Required** > > **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). > > **If no valid profile exists, 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

---

RAM Policy

See [references/ram-policies.md](references/ram-policies.md) for the full permission list.

Minimum required actions: `cms:ListDatasets`, `cms:GetDataset`, `cms:CreateDataset`, `cms:UpdateDataset`, `cms:DeleteDataset`, `cms:ExecuteQuery`.

> **[MUST] Permission Failure Handling:** When any command or API call fails due to permission errors at any point during execution, follow this process: > 1. Read `references/ram-policies.md` to get the full list of permissions required by this SKILL > 2. Use `ram-permission-diagnose` skill to guide the user through requesting the necessary permissions > 3. Pause and wait until the user confirms that the required permissions have been granted

---

Parameter Confirmation

> **IMPORTANT: Parameter Confirmation** — Before executing any command or API call, > ALL user-customizable parameters (e.g., RegionId, instance names, CIDR blocks, > passwords, domain names, resource specifications, etc.) MUST be confirmed with the > user. Do NOT assume or use default values without explicit user approval.

| Parameter | Required/Optional | Description | Default Value | | --- | --- | --- | --- | | `workspace` | Required | CMS workspace ID | — | | `dataset-name` | Required (except ListDatasets) | Dataset name (4-63 chars) | — | | `region` | Optional | Region ID | CLI profile region | | `schema` | Required (CreateDataset) | Schema JSON object | — | | `description` | Optional | Dataset description | — | | `query` | Required (ExecuteQuery) | Query text | — | | `type` | Auto-filled (ExecuteQuery) | Query type placeholder. Always `SQL`, do not ask user | `SQL` | | `max-results` | Optional (ListDatasets) | Max results per page | — | | `next-token` | Optional (ListDatasets) | Pagination token for next page | — |

---

Naming Rules

Dataset names and schema field names must satisfy:

• Length: 4-63 characters
• Start with a lowercase letter
• Only lowercase letters, digits, and underscores
• No leading/trailing underscore, no consecutive underscores

Regex: `^[a-z](?!.*__)[a-z0-9_]{2,61}[a-z0-9]$`

Invalid names must NOT be silently normalized. Ask the user for a valid replacement.

---

Core Workflow

> **[CRITICAL] Product Binding:** All dataset operations in this skill use the **`cms` product ONLY**. > The correct command pattern is `aliyun cms <action> --api-version 2024-03-30`. > **DO NOT** use any other product for dataset operations — `dataworks`, `adb`, `sls`, `maxcompute`, `opensearch`, `pai`, `dashvector`, or any other service are **WRONG** for this scenario. > If a command fails, check parameters and permissions — do NOT switch to a different product.

All commands use `--api-version 2024-03-30`. Do not pass `--endpoint` by default. Use `--region` (not `--region-id`) when specifying a region.

0. Verify Workspace Exists

> **[MUST]** Before executing any dataset operation, call `get-workspace` to verify the workspace exists. Do NOT skip this step or use ListDatasets to infer workspace existence.

aliyun cms get-workspace --api-version 2024-03-30 \
  --workspace <workspace>

If the workspace does not exist (returns error), create it via `put-workspace`:

aliyun cms put-workspace