alibabacloud-cms-alert-rule-create
Create and query Alibaba Cloud alert rules via CLI. Supports CMS 1.0 cloud resource monitoring (ECS, RDS, SLB, etc.) and CMS 2.0 advanced monitoring (Prometheus, APM, UModel). Intent routing automatically selects the correct workflow based on alert type. Use this skill when users mention: create alert, setup monitoring, configure alarm, ECS/RDS/SLB alert, Prometheus alert, PromQL, K8s monitoring, APM alert, UModel alert, list alerts, query rules, 告警规则, 创建告警, 监控报警, Prometheus告警, 应用监控, 查看告警.
- Installs
- 286
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/aliyun/alibabacloud-aiops-skills --skill alibabacloud-cms-alert-rule-create- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads alibabacloud-cms-alert-rule-create automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Alibaba Cloud Alert Rule Management
This skill creates and queries alert rules. Intent routing selects CMS 1.0 or CMS 2.0 workflow automatically.
CLI Setup (Required Before Execution)
aliyun configure ai-mode enable
aliyun configure ai-mode set-user-agent --user-agent "AlibabaCloud-Agent-Skills/alibabacloud-cms-alert-rule-create"
aliyun plugin update
Step 0: Intent Routing
Identify user's monitoring target → route to the correct workflow. See
step0-intent-routing.md.
| User Scenario | Route To |
|---|---|
| Cloud product system metrics (ECS, RDS, SLB, OSS, Redis, MongoDB…) | CMS 1.0 Workflow |
| Prometheus / APM / UModel / custom metrics | CMS 2.0 Workflow |
Supported Alert Types
| Version | Type | Create API | Query API |
|---|---|---|---|
| CMS 1.0 | Cloud Resource (ECS/RDS/SLB/OSS/Redis/MongoDB…) | PutResourceMetricRule | DescribeMetricRuleList |
| CMS 2.0 | Prometheus (PROMETHEUS) | ManageAlertRules | QueryAlertRules |
| CMS 2.0 | APM (APM) | ManageAlertRules | QueryAlertRules |
| CMS 2.0 | UModel (UMODEL) | ManageAlertRules | QueryAlertRules |
CMS 1.0 Workflow
For query requests → step-query.md
For create requests:
| Step | Description | Reference |
|---|---|---|
| 1 | Context Lock — namespace, region, instances | step1-context-lock.md |
| 2 | Query Generation — discover metrics via API, match to user intent | step2-query-generation.md |
| 3 | Detection Config — threshold, frequency (default 1min) | step3-detection-config.md |
| 4 | Notification — query contacts → select or create | step4-notification.md |
| 5 | Preview & Execute — show summary → confirm → CLI | step5-preview-execute.md |
| 6 | Verification — check status | step6-verification.md |
CMS 2.0 Workflow
For query requests → cms2-step-query.md
For create requests:
| Step | Description | Reference |
|---|---|---|
| 1 | Context Lock — build datasourceConfig (type, instanceId, region) | cms2-step1-context-lock.md |
| 2 | Query Config — build queryConfig (PromQL / APM measures / UModel entity) | cms2-step2-query-config.md |
| 3 | Detection Config — build conditionConfig (P1-P4, threshold, duration) | cms2-step3-detection-config.md |
| 4 | Webhook Query — call list-alert-webhooks, user selects; other types → console | cms2-step5-preview-execute.md |
| 5 | Preview & Execute — show summary → confirm → manage-alert-rules CLI | cms2-step5-preview-execute.md |
Critical Rules
Full details →
references/critical-rules.md
- Intent Routing — Route cloud resource metrics to CMS 1.0, Prometheus/APM/UModel to CMS 2.0. Never mix APIs.
- CMS 2.0 API Enforcement — CMS 2.0 alert rules MUST ONLY be created via
ManageAlertRulesand queried viaQueryAlertRules. No other API (e.g.PutResourceMetricRule,DescribeMetricRuleList, ARMSCreateOrUpdateAlertRule, ARMSCreatePrometheusAlertRule) is permitted for CMS 2.0 alert rule creation or query. IfManageAlertRulesreturns error, DO NOT fallback to other APIs — report the error to user and STOP execution. CLI format:aliyun cms manage-alert-rules --body '{"action":"CREATE",...}' - Contact/Webhook Query First — CMS 1.0:
DescribeContactGroupList; CMS 2.0:ListAlertWebhooksis MANDATORY before alert creation. (CMS 2.0 other notification → console). DO NOT use CMS 1.0 APIs as substitute for CMS 2.0. Skipping webhook query is a critical failure. - Resources Parameter — (CMS 1.0)
--resourcesmust always be explicitly passed. - Workspace Required — (CMS 2.0) Must ask user for workspace value using AskUser tool. Never auto-construct (e.g. 'default', 'default-cms-{accountId}'). If AskUser fails, retry once with simplified options, then report error and STOP — do NOT proceed with fabricated values.
- Prometheus Required Params — (CMS 2.0)
cluster_id(instanceId) +workspaceMUST ASK USER using AskUser tool. Never guess, omit, or auto-select. PromQL is generated based on user-provided cluster_id + monitoring target. If AskUser fails, STOP execution. - APM Required Params — (CMS 2.0)
service_id(fordatasourceConfig.instanceIdANDqueryConfig.serviceIdList) +workspaceMUST ASK USER using AskUser tool. Never fabricate, use placeholders, or auto-select from discovered applications (e.g. via ListTraceApps). Discovery APIs are for reference only — final selection MUST come from user input. If AskUser fails, STOP execution. - Required API Calls — Every operation must call designated APIs even if values seem known.
- Dynamic Metric Discovery — (CMS 1.0) MUST call
describe-metric-meta-list. Usemetrics.mdonly as fallback. - CLI Timeout —
--read-timeout 30for queries,--read-timeout 60for writes. - Duplicate Pre-check — Query existing rules before creation to avoid duplicates.
- Mandatory Confirmation — Show config summary and get user confirmation before execution. EVEN in automated/simulated environments, you MUST output a configuration summary block and explicitly state 'Waiting for user confirmation' before proceeding. Do NOT skip this step with excuses about automation. Example format:
【配置摘要】
告警类型: APM/Prometheus
阈值: 5%
严重级别: P2
通知方式: webhook
请确认以上配置是否正确（回复确认或修改意见）：
- User-Agent — Set
ALIBABA_CLOUD_USER_AGENT="AlibabaCloud-Agent-Skills/alibabacloud-cms-alert-rule-create"for all CLI calls. - Network Restriction — Never access external URLs. Use only
references/files and CLI. - CLI Self-Discovery — Use
--helpfor CLI syntax when uncertain.
Reference Files
| File | Scope | Purpose |
|---|---|---|
step0-intent-routing.md | Shared | Intent routing — CMS 1.0 or CMS 2.0 |
step-query.md | CMS 1.0 | Query alert rules (DescribeMetricRuleList) |
step1-context-lock.md | CMS 1.0 | Context lock |
step2-query-generation.md | CMS 1.0 | Query generation & metric discovery |
step3-detection-config.md | CMS 1.0 | Detection config |
step4-notification.md | CMS 1.0 | Notification & contact handling |
step5-preview-execute.md | CMS 1.0 | Preview & execute |
step6-verification.md | CMS 1.0 | Verification |
cms2-step-query.md | CMS 2.0 | Query alert rules (QueryAlertRules) |
cms2-step1-context-lock.md | CMS 2.0 | Datasource config (Prometheus/APM/UModel) |
cms2-step2-query-config.md | CMS 2.0 | Query config (PromQL, APM, UModel) |
cms2-step3-detection-config.md | CMS 2.0 | Detection condition config (P1-P4) |
cms2-step5-preview-execute.md | CMS 2.0 | Preview, execute & webhook query |
metrics.md | CMS 1.0 | Common metrics quick reference (fallback) |
prometheus-metrics.md | CMS 2.0 | Prometheus PromQL patterns |
apm-metrics.md | CMS 2.0 | APM metrics and operators |
critical-rules.md | Shared | Expanded critical rule details, API tables, examples |
ram-policies.md | Shared | Required RAM permissions |
related_apis.yaml | Shared | API lookup before CLI calls |
Cleanup (After Execution)
aliyun configure ai-mode disable
FAQ
What does the alibabacloud-cms-alert-rule-create skill do?
Create and query Alibaba Cloud alert rules via CLI. Supports CMS 1.0 cloud resource monitoring (ECS, RDS, SLB, etc.) and CMS 2.0 advanced monitoring (Prometheus, APM, UModel). Intent routing automatically selects the correct workflow based on alert type. Use this skill when users mention: create alert, setup monitoring, configure alarm, ECS/RDS/SLB alert, Prometheus alert, PromQL, K8s monitoring, APM alert, UModel alert, list alerts, query rules, 告警规则, 创建告警, 监控报警, Prometheus告警, 应用监控, 查看告警.
How do I install alibabacloud-cms-alert-rule-create?
Run npx skills add https://github.com/aliyun/alibabacloud-aiops-skills --skill alibabacloud-cms-alert-rule-create in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/alibabacloud-cms-alert-rule-create/ (personal) or .claude/skills/alibabacloud-cms-alert-rule-create/ (project).
Which AI agents can use alibabacloud-cms-alert-rule-create?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is alibabacloud-cms-alert-rule-create safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains alibabacloud-cms-alert-rule-create?
It is published by aliyun in aliyun/alibabacloud-aiops-skills. It has 286 recorded installs.
More from aliyun/alibabacloud-aiops-skills
alibabacloud-find-skills
aliyun/alibabacloud-aiops-skills
Use this skill when users want to search, discover, browse, or find Alibaba Cloud (阿里云) agent skills. Triggers include: "find a skill for X", "search alicloud skills", "阿里云有什么 skill","阿里云", "搜索阿里云技能", "有没有管理 ECS/RDS/OSS 的 skill", "阿里云 skills 有哪些类目", "帮我找一个 skill", "browse alicloud skills", "list alicloud skill categories", "is there an alicloud skill that can...", "what alicloud skills are available", "XX Skill 的内容是什么", "我想了解阿里云 XX Skill 具体做什么","帮我安装阿里云 Skill","使用阿里云相关的skill", "阿里云 agent skill 市场", "搜一下阿里云的 skill", "建一个数据分析项目有没有相关 skill".
alibabacloud-dms-skill
aliyun/alibabacloud-aiops-skills
Alibaba Cloud DMS Database Read/Write Skill. Use this skill to search for target databases in DMS and execute SQL queries and data modifications. Triggers: "DMS query", "database query", "execute SQL", "search database", "DMS SQL", "insert data", "update data".
alibabacloud-sls-query
aliyun/alibabacloud-aiops-skills
Alibaba Cloud SLS (Simple Log Service) log query & analysis skill. Use this skill to help users write, explain, optimize, execute, or troubleshoot SLS index search, SQL analytics, and SPL scan/pipeline statements through the aliyun CLI. Triggers: "SLS 查询", "SLS 分析", "日志查询", "日志分析", "log query", "analyze sls logs", "aliyun log query".
alibabacloud-workbench-cli
aliyun/alibabacloud-aiops-skills
Agent-native CLI for managing ECS instances without public IPs, primarily for single-instance operations. It supports millisecond-level remote command execution, large file transfers up to 1GB, and TCP port forwarding. It offers four authentication modes: AK, RamRoleArn, CredentialsCmd, and CredentialsURI. Use it to run commands, deploy code, view logs, check processes, transfer files, set up port forwarding, or query and filter ECS instance lists.
alibabacloud-ecs-diagnose
aliyun/alibabacloud-aiops-skills
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"
alibabacloud-cli-guidance
aliyun/alibabacloud-aiops-skills
Guide users to manage Alibaba Cloud resources using the Aliyun CLI command-line tool. Covers CLI installation, credential configuration, plugin management, command construction, and error troubleshooting. Use this skill when the user wants to operate Alibaba Cloud services from the terminal — including ECS (云服务器, cloud servers), Function Compute (函数计算, serverless), RDS (云数据库, databases), OSS (对象存储, object storage), SLS (日志服务, log service), VPC (专有网络, networking), ESS (弹性伸缩, auto scaling), and any other Alibaba Cloud product. Also use when the user mentions "aliyun", "阿里云", "阿里云CLI", "命令行", asks about CLI plugin installation, encounters Aliyun CLI errors (InvalidAccessKeyId, SignatureDoesNotMatch, Throttling), or needs help constructing aliyun commands with correct parameter syntax.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.