/alibabacloud-polardb-ai-assistant

name: alibabacloud-polardb-ai-assistant
description: |
  Alibaba Cloud PolarDB Database AI Assistant. For PolarDB MySQL/PostgreSQL cluster management, instance inspection, performance diagnostics, parameter explanation and change assessment, SQL/log analysis, backup, security audit, HA/DR, event analysis, and other PolarDB O&M operations.
  Use when user questions involve PolarDB, cluster IDs starting with pc-, PolarDB kernel/proxy versions, parameters, primary-standby switchover, IMCI columnar storage, or PolarDB console operations. This Skill is PolarDB-only.

PolarDB Database AI Assistant

This Skill focuses on **Alibaba Cloud PolarDB MySQL/PostgreSQL database** intelligent O&M. It invokes the Yaochi Agent v2 backend through the `get-yao-chi-agent` API and the aliyun CLI DAS plugin.

**Architecture**: `Codex Skill` -> `scripts/call_yaochi_agent.sh` -> `Aliyun CLI` -> `DAS Plugin (Signature V3)` -> `get-yao-chi-agent API` -> `Yaochi Agent v2` -> `PolarDB Skill/MCP/DAS/RAG capabilities`

**Scope**: PolarDB only. Do not use this Skill for non-PolarDB product O&M requests unless the user's request is explicitly about PolarDB integration or comparison.

Supported Capabilities

| Capability | Description | |------------|-------------| | Instance query and filtering | Natural-language filtering for PolarDB clusters by ID, engine, version, status, pay type, zone, architecture, tags, name, creation window, or expiration window | | Instance status inspection | Runtime status, node health, version, lock/migration state, endpoint state, pay type, and expiration checks | | Cluster resource inspection | CPU, memory, connections, IOPS, storage, Serverless PCU behavior, capacity pressure, and trend analysis | | Connection and session inspection | Connection usage, active sessions, idle transaction risk, connection trend, and connection pool suggestions | | Proxy performance inspection | Proxy CPU, QPS, connection stability, response time, endpoint/routing information, and read/write split signal checks | | Backup inspection | Backup policy, backup records, backup task status, log backup/PITR capability, and backup success/failure risk | | Security inspection | Whitelist, public exposure risk, SSL/TDE, account security posture, and SQL audit configuration | | High availability and disaster recovery | Multi-zone/HA posture, hot standby state, GDN/migration signals, HA switch records, and DR readiness | | Log diagnostics | Error log and slow log volume, pattern analysis, and operational recommendations | | Serverless inspection | PCU min/max configuration, scaling behavior, auto-pause posture, and workload-resource fit | | Parameter explanation | PolarDB MySQL/PostgreSQL parameter meaning, defaults, risk, best practices, and restart/effective-scope notes | | Parameter change assessment | Parameter modification log explanation, multi-parameter impact assessment, and change-risk suggestions | | IMCI parameter explanation | PolarDB MySQL IMCI columnar index parameter explanation and usage guidance | | Kernel and proxy version diagnostics | DB kernel/proxy version gap analysis, release-note based risk assessment, high-risk fixed bug checks, and upgrade suggestions | | HA switchover and event analysis | HA switchover root cause, related performance/log evidence, event impact, and follow-up mitigation | | Storage diagnostics | Storage composition, growth trend, abnormal usage, cold data/archive signals, and cleanup or capacity advice | | SQL performance diagnostics | Slow SQL, execution plan, lock/blocking, and index optimization diagnostics when supported by backend and permissions |

Backend Execution Model

The local Skill does not call PolarDB MCP tools directly. It sends a natural-language query to Yaochi Agent v2. The backend is responsible for:

1. Matching a PolarDB scenario Skill first when the request is an O&M, inspection, diagnosis, parameter, or event scenario. 2. Calling PolarDB MCP/OpenAPI tools for real cluster, metric, log, backup, security, or data-plane evidence. 3. Using DAS intelligent diagnosis for performance, slow SQL, lock, index, and auto-increment ID issues when applicable. 4. Falling back to PolarDB documentation/RAG only when structured tools cannot answer the question.

When answering users, treat the backend output as the source of truth. Do not invent cluster status, metrics, logs, risk levels, or document links that are not present in the response.

Observability

**[MUST] User-Agent template** — Every Alibaba Cloud CLI, SDK, or Terraform invocation made by this Skill must use: `AlibabaCloud-Agent-Skills/alibabacloud-polardb-ai-assistant/{session-id}`

**[MUST] Session-id rule** — Generate one observability session ID at the start of each Skill execution session, reuse the same value across all Alibaba Cloud CLI, SDK, and Terraform calls in that session, and do not regenerate it for retries or multi-step workflows. The session ID must be a 32-character lowercase hexadecimal string.

export ALIBABACLOUD_AGENT_SKILL_SESSION_ID="${ALIBABACLOUD_AGENT_SKILL_SESSION_ID:-$(openssl rand -hex 16)}"

**[MUST] CLI User-Agent** — Every `aliyun` CLI command invocation must include: `--user-agent AlibabaCloud-Agent-Skills/alibabacloud-polardb-ai-assistant/${ALIBABACLOUD_AGENT_SKILL_SESSION_ID}`

Installation

> **Pre-check: Aliyun CLI >= 3.3.3 required** > Run `aliyun version` to verify >= 3.3.3. If not installed or version too low, > download the installer, review it, then run it locally to update, > or see [references/cli-installation-guide.md](references/cli-installation-guide.md) for installation instructions. > Then **[MUST]** run `aliyun configure set --auto-plugin-install true` to enable automatic plugin installation. > Then **[MUST]** run `aliyun plugin update` to ensure that any existing plugins on your local machine are always up-to-date.

# Install aliyun CLI after reviewing the downloaded installer
curl -fsSL https://aliyuncli.alicdn.c