What makes alibabacloud-cms-manage notable?

1.1K downloads. Trust evidence available

How should alibabacloud-cms-manage be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

alibabacloud-cms-manage

Entry skill for the aliyun CLI distribution of CloudMonitor (CMS). Use when the user mentions aliyun cms2, CloudMonitor, CMS commands, or any CMS module operation such as Integration Policy/Center, APM, RUM, Prometheus Service, Recording rule, alert rule, alert template, alert history, event hub, SLS event, PromQL, cloud resource, service observability, monitoring onboarding, metric query, etc.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.1k

Updated

Oct 11, 2026

Version

1.0.5

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.1K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.1K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.5release · observed Oct 9, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s173swjet2yrebzqrp6hjkvmy583mxef:alibabacloud-cms-manage

Install using `clawhub skill install s173swjet2yrebzqrp6hjkvmy583mxef:alibabacloud-cms-manage` in an isolated environment before connecting it to live workloads.
No published capability contract is available yet, so validate auth and request/response behavior manually.
Review the upstream CLAWHUB listing at https://clawhub.ai/sdk-team/alibabacloud-cms-manage before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-sdk-team-alibabacloud-cms-manage/snapshot"

Documentation

CLAWHUB

148,189 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: alibabacloud-cms-manage
description: |
  Entry skill for the aliyun CLI distribution of CloudMonitor (CMS).
  Use when the user mentions aliyun cms2, CloudMonitor, CMS commands,
  or any CMS module operation such as Integration Policy/Center, APM, RUM,
  Prometheus Service, Recording rule, alert rule, alert template, alert history,
  event hub, SLS event, PromQL, cloud resource, service observability,
  monitoring onboarding, metric query, etc.
license: Apache-2.0
compatibility: aliyun-cli>=3.3.15
metadata:
  domain: aiops
  owner: cms
  contact: [email protected]
---

# CMS CLI — `aliyun cms2`

## Prerequisite Check

> **Once per session**: perform this prerequisite check only on the **first** invocation of this skill in a conversation. If all checks already passed earlier in the same session, skip directly to the relevant module.

1. **Check `aliyun` exists** — `which aliyun` (macOS/Linux) or `where aliyun` (Windows).
    - Not found → ask the user to install the aliyun CLI first: <https://help.aliyun.com/document_detail/121541.html>. Stop and wait.

2. **Check CLI version** — run `aliyun version`. Minimum required: **3.3.15** (see `compatibility` in frontmatter).

   > ⚠️ Compare version segments as **integers** (semver): 3.3.4 < 3.3.15 because 4 < 15.
   > Shell verification: `printf '%s\n' "3.3.15" "$(aliyun version)" | sort -V | head -1`
   > If the output equals the current version, the requirement is NOT met.

    - Version OK → go to step 3.
    - Version too old or unrecognized →
        1. Run `aliyun upgrade --help` to test whether the `upgrade` subcommand exists.
            - Available → run `aliyun upgrade -y` to update to the latest version automatically, then re-check `aliyun version`.
        2. If `upgrade` not available → ask the user to upgrade manually following the official guide: <https://help.aliyun.com/zh/cli/update-cli>. Wait for the user to confirm the upgrade is complete, then re-check `aliyun version`.
        3. If upgrade succeeded → go to step 3.
        4. If upgrade failed → ask the user to upgrade manually: <https://help.aliyun.com/zh/cli/update-cli>. Stop and exit.

3. **Check `cms2` plugin** — run `aliyun cms2 --help`.
    - Help output OK → continue to **Credentials**.
    - `unknown command` / missing → **stop immediately**, output the error report below (append CLI version, OS, and error message), and make **no further CLI calls**.

---

## Credentials

`aliyun cms2` reuses the aliyun CLI credential system (`aliyun configure`).
Use `--profile <name>` to switch profiles.

## Observability

Upon loading this skill, generate a random session ID (32-char lowercase hex string) once per session...

For every aliyun cms2 command, append:
--user-agent "AlibabaCloud-Agent-Skills/alibabacloud-cms-manage/{session-id}"

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

## Global Conventions

**Hard constraint**: fallback to `aliyun cms`, ot

_meta.json

{
  "ownerId": "kn74p5w8ywv6prh40g0s82gmqh83nw54",
  "slug": "alibabacloud-cms-manage",
  "version": "1.0.5",
  "publishedAt": 1791527961028
}

references/ai.md

# AI Observability Module

> Global conventions (credentials, output format, error codes, command prefix, distributions) — see [../SKILL.md](../SKILL.md).
> Run `aliyun cms2 apm <subcommand> --help` for full flag lists and examples.

## Scope

Guided workflow to onboard AI applications (LLM-based services, AI Agents, custom instrumented apps) into CMS Application Monitoring. Uses `aliyun cms2` CLI to initialize APM infrastructure, retrieve access credentials, and generate framework-specific configuration.

**In-Scope**: Initialize APM infra, retrieve LicenseKey/Endpoint, register app services, generate startup configuration for all supported AI frameworks.

**Out-of-Scope**: Model fine-tuning or training observability; GPU monitoring (see `cloud-acs-ecs-gpu` addon).

---

## Execution Safety Rules

Follow the same Two-Phase Execution Protocol as [apm.md — Execution Safety Rules](apm.md#execution-safety-rules).

**Operations that do NOT require confirmation** (execute directly):
- Read-only commands: `get`, `list`, `--help`
- CMS backend resource creation: `apm configuration create`, `apm service create`
- Retrieving credentials: `apm configuration get`
- Fetching addon templates: `integration addon get`

**Operations that REQUIRE confirmation** (must use Two-Phase Protocol):
- Deleting service records: `apm service delete`
- Modifying user application startup scripts or Dockerfiles

---

## Supported Frameworks

| Framework | Addon Name | Protocols | Underlying Agent |
|-----------|-----------|-----------|-----------------|
| **Dify** | `ai-dify` | opentelemetry | Dify 控制台内置 OTel 配置 |
| **LangChain/LangGraph** | `ai-langchain-langgraph` | arms, arms4cs, opentelemetry | Python aliyun-bootstrap |
| **DashScope** | `ai-dashscope` | arms, arms4cs, opentelemetry | Python aliyun-bootstrap |
| **AgentScope** | `ai-agentscope` | arms, arms4cs, opentelemetry | Python aliyun-bootstrap |
| **OpenAI** | `ai-openai` | arms, arms4cs, opentelemetry | Python aliyun-bootstrap |
| **Coze** | `ai-coze` | arms-ecs, arms-ack, opentelemetry | Golang（arms-ecs: instgo, arms-ack: ack-onepilot） |
| **OpenClaw** | `ai-openclaw` | opentelemetry | 专用 installer 脚本 |
| **CoPaw** | `ai-copaw` | opentelemetry | 专用 installer 脚本 |
| **Hermes** | `ai-hermes` | opentelemetry | 专用 installer 脚本 |
| **自定义埋点** | `ai-custom-instrumentation` | agent-extension, manual | ARMS 探针扩展 / 手动 OTel SDK |

**Protocol legend**:
- `arms` — 自研 Python Agent (通用环境), serviceType = `TRACE`
- `arms4cs` — 自研 Python Agent (容器环境), serviceType = `TRACE`
- `arms-ecs` / `arms-ack` — 自研探针 (按部署环境区分), serviceType = `TRACE`
- `opentelemetry` — OpenTelemetry 协议, serviceType = `XTRACE`
- `agent-extension` / `manual` — 自定义埋点, serviceType = `TRACE`

---

## CLI Commands Reference

| Command | Purpose | Key Flags |
|---------|---------|-----------|
| `apm configuration create` | Initialize APM infrastructure (idempotent) | `--workspace`, `--region` |
| `apm configuration get` | Get LicenseKey, Endpoint, project | `--works

references/alerting.md

# Alerting Module

> Global conventions (credentials, output, error codes) — see [../SKILL.md](../SKILL.md).
> Run `aliyun cms2 alert <subcommand> --help` for full flag lists; this doc focuses on **business knowledge** not in `--help`.
> Notification targets (contacts / robots / webhooks) are now under the top-level `notification-channel` command — not under `alert`.
> APM metric catalog → [apm-metrics.md](apm-metrics.md). UModel metric catalog → [umodel-metrics.md](umodel-metrics.md).

## Command Tree (sub-resource layout)

```
aliyun cms2 alert
├── rule          create | update | patch | delete | enable | disable | list | get
├── template      list | get | create | update | delete | apply
└── history       list
```

> ⚠️ **Hard rules (user preference)**:
> 1. To modify an existing rule, **always prefer** `alert rule patch --use-patch-api`. **Avoid `update`** (it requires the full body and risks accidental overwrites).
> 2. After a successful `alert rule create`, you **must** immediately run `alert rule get --alert-rule-id <id>` and show the full rule to the user. Do not skip.

### Query Alert Rule

```bash
aliyun cms2 alert rule get  --alert-rule-id <uuid>
aliyun cms2 alert rule list --workspace <ws>
```

#### Client-side Guards (alert rule get / list / delete)

These are **client-side fail-fast checks** added after the v0.9.2-6 QA pass
(CMS-CLI-NEW-1 / CMS-CLI-NEW-7 / silent-filter-acceptance). Treat them as
hard constraints when generating commands; the server would otherwise
silently return surprising rows or success-with-zero-effect envelopes.

| Command | Guard | Why |
|---------|-------|-----|
| `alert rule get` | `--alert-rule-id` rejects empty / whitespace-only values (`InvalidArgument`). | Was a P0 information-disclosure: empty ID degraded into a `Uuid.Eq=""` filter and dumped the entire account's rules. |
| `alert rule delete` | When `deletedCount == 0` (no UUID matched), the envelope is `{success:false, error:{code:"ResourceNotFound"}}`. | Earlier behaviour was `success=true, deletedCount=0` + a stderr warning, which masks typos in scripted teardown. |
| `alert rule list` | `--alert-rule-id`, when explicitly set, must not be empty / whitespace-only. | Otherwise the UUID filter was silently dropped and the query degraded to a workspace-wide list-all. |
| `alert rule list` | `--page-size`, `--page-number`, `--max-results` must be `>= 1` when explicitly set. | `--page-size 0` used to be silently forwarded and the server returned 0 rows. |
| `alert rule list` | `--page-size` and `--max-results` are capped at **1000** client-side. | The backend echoes any size into the envelope but truncates the actual rows; large values look like "0 rows returned". |

> If you need a true list-all, omit the filter flag entirely. Do **not**
> pass `--alert-rule-id ""` thinking it means "any".

### Alert Rule Template Filter Guards

| Command | Guard | Why |
|---------|-------|-----|
| `alert template list` | `--alert-type` is whitelisted to `PROMETHEUS_SI

references/apm-metrics.md

# APM Metric Catalog

> Companion to [alerting.md](alerting.md). All `aliyun cms2 alert rule` APM commands consume these tables.

## Group → Filter / GroupBy Mapping

When constructing `queryConfig.filterList` / `groupBy`, look up the metric's `group` first.

| Group | displayNameCn | Default Filters (dim → type) | groupBy |
|-------|---------------|-------------------------------|--------|
| `apm.host` | 主机监控 (Host) | `rootIp` → ALL | `["rootIp"]` |
| `apm.jvm` | JVM监控 (JVM) | `rootIp` → ALL | `["rootIp"]` |
| `apm.txn` | 应用提供服务统计 (Inbound RPC) | `rpc` → ALL, `rpcType` → ALL | `["rpc","rpcType"]` |
| `apm.txn_type` | 应用依赖服务统计 (Outbound RPC) | `rpcType` → ALL, `destId` → ALL | `["rpcType","destId"]` |
| `apm.pod` | 容器监控 (Pod) | `rootIp` → ALL | `["rootIp"]` |
| `apm.exception` | 异常监控 (Exception) | `rpc` → ALL, `excepName` → ALL | `["rpc","excepName"]` |
| `apm.httpcode` | HTTP状态码 (HTTP status) | `rpc` → ALL, `status` → ALL | `["rpc","status"]` |
| `apm.db` | 数据库指标 (Database) | `endpoint` → ALL | `["endpoint"]` |
| `apm.threadpool` | 线程池监控 (Thread pool) | `ThreadPoolType` → ALL, `ThreadPoolName` → ALL, `rootIp` → ALL | `["ThreadPoolType","ThreadPoolName","rootIp"]` |
| `apm.threadpoolv2` | 新版线程池 (Thread pool v2) | `thread_pool_usage` → ALL, `thread_name_pattern` → ALL, `rootIp` → ALL | `["thread_pool_usage","thread_name_pattern","rootIp"]` |
| `apm.connectionpool` | 连接池监控 (Connection pool) | `pool_type` → ALL, `rootIp` → ALL | `["pool_type","rootIp"]` |
| `apm.scheduler` | 定时任务 (Scheduled task) | `rpc` → ALL | `["rpc"]` |
| `apm.httpclient` | Web依赖 (HTTP client) | `destId` → ALL, `endpoint` → DISABLED | `["destId"]` |

> **Default rule**: All dims default to `ALL` (traverse) unless user specifies a concrete filter value (then use `EQ`).
> **filterList[].type**: `EQ` | `NE` | `ALL` | `DISABLED` | `CONTAIN` | `EXCLUDES` | `=~` | `!~`

---

## User Intent → Metric Quick Reference

Match user intent first; only fall back to the full registry if not listed here.

| User Intent (zh-CN) | measureCode | Group | Unit |
|---------------------|-------------|-------|------|
| CPU 使用率 / CPU usage | `appstat.jvm.SystemCpuUsage` | apm.host | % |
| 内存使用率 / Memory usage | `appstat.jvm.SystemMemUsage` | apm.host | % |
| JVM 堆内存使用率 / Heap usage | `appstat.jvm.HeapUsedRatio` | apm.jvm | % |
| FullGC 次数 / Full GC count | `appstat.jvm.gc.OldGcCountInstant` | apm.jvm | count |
| 线程总数 / Thread count | `appstat.jvm.ThreadCount` | apm.jvm | number |
| 调用次数 / QPS | `appstat.transaction.count` | apm.txn | count |
| 响应时间 / RT | `appstat.transaction.rt` | apm.txn | ms |
| 错误率 / Error rate | `appstat.transaction.errorrate` | apm.txn | % |
| 慢调用 / Slow calls | `appstat.transaction.slowcount` | apm.txn | count |
| Pod CPU 使用量 / Pod CPU | `appstat.pod.SystemCpuTotal` | apm.pod | core |
| Pod 内存使用量 / Pod memory | `appstat.pod.SystemMemUsage` | apm.pod | MB |
| 数据库 RT / DB RT | `appstat.database.rt` | apm.db | ms |
| 异常次数 / Exception count | `appstat.exception.count` | apm.exception

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.