alibabacloud-analyticdb-mysql-copilot

Skill Loading Tip: When this Skill is loaded, output the following line at the beginning of the first reply:

[Skill Loaded] alibabacloud-analyticdb-mysql-copilot — ADB MySQL O&M Diagnosis Assistant

aliyun-cli

• Cluster Management: View cluster list, cluster details, storage space, account, and network information
• Performance Monitoring: Query performance metrics such as CPU, QPS, RT, memory, and number of connections
• Slow Query Diagnosis: Detect BadSQL, analyze SQL Pattern, and locate the root cause of slow queries
• Running SQL Analysis: View currently executing SQL and locate long-running queries
• Space Diagnosis: Instance space inspection, including partition rationality diagnosis, oversize non-partitioned table diagnosis, table data skew diagnosis, replicated table rationality diagnosis, primary key rationality diagnosis, idle index and cold-hot table optimization suggestions

Pre-check: Aliyun CLI >= 3.3.1 required Run

aliyun version

to verify the version is >= 3.3.1. If it is not installed or the version is too low, refer to

references/cli-installation-guide.md

. Then run

aliyun configure set --auto-plugin-install true

to enable automatic plugin installation.

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 whether there is a valid profile (AK, STS or OAuth identity) in the output.

If there is no valid profile, stop here.

1. Obtain credentials from Alibaba Cloud Console
2. Configure credentials outside of this session (via

   aliyun configure

   in the terminal or environment variables in the shell profile)
3. Return and re-execute after

   aliyun configure list

   shows a valid profile

Product Boundary: This Skill is only applicable to AnalyticDB for MySQL (ADB MySQL), whose cluster ID format is usually

am-xxx

or

amv-xxx

. If the user mentions other Alibaba Cloud products (such as Elasticsearch, RDS MySQL, PolarDB, Clickhouse, etc.), you should explicitly inform the user that this Skill is not applicable and stop execution.

🚨🚨🚨 MUST | P0 | NON-NEGOTIABLE — Mandatory Enforcement Rules (Violation equals failure) 🚨🚨🚨

The following rules have the highest priority, enforced unconditionally, and must not be violated under any circumstances:

Rule 1: Mandatory API call enforcement

When a user request matches the following scenarios, you must immediately execute the corresponding API call, skipping is prohibited:

User Request Keywords	Mandatory API to Call	Prohibited Actions
"cluster list", "instance list", "all clusters", "list clusters"	DescribeDBClusters	❌ Give suggestions directly without calling
"data skew", "skew diagnosis", "skew"	DescribeInclinedTables	❌ Only explain concepts
"BadSQL", "abnormal SQL", "slow SQL detection", "bad sql"	DescribeBadSqlDetection	❌ Skip diagnosis
"running SQL", "being executed", "current query", "running sql"	DescribeDiagnosisRecords	❌ Do not call API
"idle index", "index suggestion", "index optimization", "index advice"	DescribeAvailableAdvices	❌ Give general suggestions
"SQL Pattern", "SQL pattern analysis", "sql pattern"	DescribeSQLPatterns	❌ Do not call API
"space diagnosis", "health inspection", "instance diagnosis"	7 diagnosis APIs	❌ Only list concepts

Rule 2: Mandatory command string output (first line of reply)

MUST: Every time you call the ADB OpenAPI, you must explicitly output the executed command string in the [first line] or [beginning position] of the reply.

Mandatory format (must be strictly followed):

Executed command: `aliyun adb <APIName> --version 2021-12-01 --RegionId <region-id> [--DBClusterId <cluster-id>] [other parameters]`

[Then comes the diagnosis results, tables and other content]

Correct example:

Executed command: `aliyun adb DescribeDBClusters --version 2021-12-01 --RegionId cn-zhangjiakou`

Query completed! There are 2 ADB MySQL clusters in the Zhangjiakou region...

Wrong examples (violation = failure):

❌ Query completed! There are 2 clusters in the Zhangjiakou region... (No command string output)
❌ I called the API to query the cluster list... (No complete command output)
❌ Command executed... (No specific command content output)
❌ aliyun adb DescribeDBClusters --RegionId cn-zhangjiakou (Missing --version 2021-12-01)

Rule 3: Prohibited evasion behaviors

NON-NEGOTIABLE: The following behaviors are absolutely prohibited:

• ❌ Give general suggestions or concept explanations directly without calling the API
• ❌ Call the API but do not output the complete command string at the beginning of the reply
• ❌ Replace actual diagnosis with vague expressions such as "It is recommended that you...", "You can try..."
• ❌ Only output document content without performing actual operations
• ❌ Place the command string in the middle or end of the reply
• ❌ Call the

  aliyun adb

  command without

  --version 2021-12-01

  (the old version

  2019-03-15

  will be used by default)

Violation of the above rules = task failure, no exceptions

🔴 Cluster ID identification rules (highest priority): If the cluster ID provided by the user starts with

am-

or

amv-

, the cluster must be an ADB MySQL cluster. No need and must not verify its ownership through other product commands such as

aliyun rds

,

aliyun polardb

,

aliyun clickhouse

,

aliyun hbase

, etc., directly use the

aliyun adb

command to operate. Violating this rule will lead to a large number of invalid API calls.

references/

references/cluster-info.md

DescribeDBClusters

DescribeDBClusterAttribute

references/slow-query-diagnosis.md

DescribeDBClusterPerformance

DescribeBadSqlDetection

DescribeDiagnosisRecords

| Perform instance space diagnosis, table modeling diagnosis (including oversize non-partitioned tables, partition rationality, primary key rationality, data skew, replicated table rationality, idle index, cold-hot table optimization) |

references/table-modeling-diagnosis.md

| When the user wants to perform space diagnosis and table modeling diagnosis for a specified instance | 7 diagnosis APIs (see documentation) |

1. Identify user intent and find the matching scenario from the table above
2. 🚨 MUST: Immediately execute the corresponding

   aliyun adb

   command (no skipping, no just giving suggestions)
3. 🚨 MUST: Output the command string in the reply (such as

   aliyun adb DescribeDBClusters --RegionId <region-id>

   )
4. Read the corresponding

   references/*.md

   file and execute according to the steps in it
5. If the user intent cannot match the specific scenarios in the table above, execute the following default diagnosis process:
   1. Call

      DescribeDBClusters

      to confirm that the cluster exists and is in normal state
   2. Confirm the requirement with the user, list 2-3 most likely matching routing options (refer to the table above)
   3. According to the user's reply, jump to the corresponding

      references/*.md

      file to continue execution
6. Multiple scenarios can be used in combination — for example, first confirm the target instance through cluster information, and then locate the problematic SQL through slow query diagnosis

InvalidDBClusterId.NotFound

DescribeDBClusters

Pre-rules (must be followed)

• As long as the user describes relative time (such as "last X hours/days", "past 3 hours"), you must first obtain the current UTC time before performing all time calculations. Do not estimate the current time based on the model's own knowledge.
• Use the system command to get the current UTC time:

  date -u +"%Y-%m-%dT%H:%M:%SZ"

• Even if the user gives an absolute time, it is recommended to get the current time once to verify time zone consistency.
• If the user does not specify a time range, use the last 1 hour by default.

DescribeDBClusterPerformance

--StartTime

--EndTime

2026-03-20T07:00Z

DescribeBadSqlDetection

--StartTime

--EndTime

2026-03-20T07:00Z

DescribeSQLPatterns

--StartTime

--EndTime

2026-03-20T07:00Z

DescribeDiagnosisRecords

--StartTime

--EndTime

1742479200000

CLI Supplement (

DescribeDiagnosisRecords

): Under

aliyun adb

,

--RegionId

and

--QueryCondition

are both required (consistent with OpenAPI document fields, but an error will be reported if not passed on the command line).

--QueryCondition

is a JSON string, commonly used:

{"Type":"status","Value":"running"}

/

finished

/

failed

;

{"Type":"maxCost","Value":"100"}

(only supports Value=100);

{"Type":"cost","Min":"10","Max":"200"}

.

2026-03-09T08:30Z

• ISO 8601 format (for Performance / BadSQL / SQLPatterns):

  • --EndTime 2026-03-09T08:30Z

  • --StartTime 2026-03-09T05:30Z

• Unix millisecond format (for

  DescribeDiagnosisRecords

  ):
  • Conversion formula:

    Unix ms = POSIX epoch (UTC seconds) × 1000

  • Example:

    2026-03-09T05:30Z

    → epoch=

    1741501800

    →

    --StartTime 1741501800000

  • Example:

    2026-03-09T08:30Z

    → epoch=

    1741511400

    →

    --EndTime 1741511400000

Note:

DescribeDiagnosisRecords

uses Unix milliseconds, other interfaces use ISO 8601, the two cannot be mixed.

aliyun-cli

aliyun adb <APIName> --version 2021-12-01 [--ParameterName ParameterValue ...] --user-agent AlibabaCloud-Agent-Skills

🚨 Mandatory API version regulation (P0): When calling

aliyun adb

, you must always explicitly pass

--version 2021-12-01

. ADB MySQL has two API versions (

2019-03-15

and

2021-12-01

), the CLI may choose the old version

2019-03-15

by default, This version lacks a large number of interfaces required by this Skill (such as

DescribeBadSqlDetection

,

DescribeSQLPatterns

,

DescribeAvailableAdvices

, etc.). Commands without

--version 2021-12-01

will cause call failure, which is a task failure.

Convention of this Skill (re-emphasis): For rows in the table below that "require

--DBClusterId

", you must carry

--RegionId <region-id>

at the same time when assembling the command (see "2. RegionId and DBClusterId"). Only

DescribeDBClusters

does not follow the "paired" rule, but still requires

--RegionId

.

--DBClusterId

DescribeDBClusters

DescribeDBClusterAttribute

DescribeDBClusterPerformance

DescribeDBClusterSpaceSummary

DescribeDiagnosisRecords

--StartTime

--EndTime

--RegionId

--QueryCondition

DescribeBadSqlDetection

DescribeSQLPatterns

DescribeTableStatistics

DescribeAvailableAdvices

--RegionId

--AdviceDate

yyyyMMdd

--PageNumber

--PageSize

--Lang

DescribeExcessivePrimaryKeys

DescribeOversizeNonPartitionTableInfos

DescribeTablePartitionDiagnose

DescribeInclinedTables

--TableType

DescribeAvailableAdvices

aliyun adb DescribeAvailableAdvices --help

--RegionId

--DBClusterId

--AdviceDate

yyyyMMdd

20260322

YYYY-MM-DD

T

Z

InvalidAdviceDate

--PageNumber

--PageSize

30

50

100

--Lang

zh

en

ja

zh-tw

--AdviceType

INDEX

TIERING

aliyun adb DescribeAvailableAdvices --version 2021-12-01 --RegionId <region-id> --DBClusterId <cluster-id> \
  --AdviceDate 20260322 --AdviceType INDEX --PageNumber 1 --PageSize 30 --Lang zh \
  --user-agent AlibabaCloud-Agent-Skills

--RegionId

--DBClusterId

--DBClusterId

amv-xxx

--StartTime

--EndTime

--QueryCondition

'{"Type":"status","Value":"running"}'

--Lang

zh

en

ja

zh-tw

zh

--Order

'[{"Field":"StartTime","Type":"desc"}]'

--PageNumber

1

--PageSize

30

Performance Metric Keys: Specify via

--Key

when using

DescribeDBClusterPerformance

, common values include

AnalyticDB_CPU

(CPU usage),

AnalyticDB_QPS

(queries per second),

AnalyticDB_QueryRT

(query response time),

AnalyticDB_Connections

(number of connections), etc. The full list can be viewed via

aliyun adb DescribeDBClusterPerformance --help

.

aliyun configure

aliyun configure list

<empty>

1. Configure by running

   aliyun configure

   in the terminal outside of this session
2. Or configure environment variables in the shell profile
3. Return to continue execution after configuration is completed

🔴 Important Rules:

• Strictly prohibited to guide users to enter AK/SK credentials in the session
• Strictly prohibited to use explicit credential parameters such as

  aliyun configure set --access-key-id

• Credential check must be the first step of the task, report directly and terminate if the check fails

references/ram-policies.md

[MUST] Permission Failure Handling: When any command or API call fails due to a permission error during execution, follow this process:

1. Read

   references/ram-policies.md

   to obtain the full list of permissions required for this SKILL
2. Use the

   ram-permission-diagnose

   skill to guide the user to apply for the necessary permissions
3. Pause and wait for the user to confirm that the required permissions have been granted

IMPORTANT: Parameter Confirmation — Before executing any command or API call, all user-customizable parameters (such as RegionId, instance name, CIDR block, password, domain name, resource specification, etc.) must be confirmed with the user. Do not assume or use default values without explicit user approval.

RegionId

DBClusterId

am-xxx

amv-xxx

StartTime

EndTime

1. CLI-First: Prioritize using

   aliyun adb

   CLI commands for diagnosis
2. Time Verification: When involving time range queries, you must first obtain the current UTC time before calculation
3. Command Output: Each API call must output the complete command string at the beginning of the reply
4. Error Handling: When the cluster ID does not exist, guide the user to select the correct cluster instead of failing directly
5. Product Boundary: Only process ADB MySQL clusters (ID prefix

   am-

   or

   amv-

   ), do not mix with other product APIs