/alibabacloud-sysagent

name: alibabacloud-sysagent
description: "SysAgent is a system operations expert for Linux instances on Alibaba Cloud. Covers system diagnostics (CPU, memory, disk I/O, network issues and OOM), kernel crash analysis (vmcore, panic and lockups), health checks (instance inspections and system risks), CPU/GPU profiling (slow training, inference and hotspots), system security (CVE queries and kernel vulnerability assessment), OS distribution customization and delivery (branding and bootable ISO images), and Java runtime diagnostics (GC logs, heap dumps, thread dumps and JFR). Use this skill whenever the user needs to diagnose high CPU, memory pressure, I/O latency or packet loss; investigate a kernel crash; inspect instance health; locate workload performance bottlenecks; assess whether a CVE affects their systems; customize or build an OS image; or investigate Java memory leaks, long GC pauses or thread contention using SysAgent via the Alibaba Cloud CLI."

SysAgent — System Operations Expert

SysAgent provides operating system services for operations engineers, SREs, and developers, from distribution customization and delivery to day-to-day system operations. Through natural-language interaction and multi-agent collaboration, it supports system inspection, fault and crash diagnosis, runtime troubleshooting, performance profiling, and security assessment.

• [Product Overview](https://help.aliyun.com/zh/alinux/sysagent-overview)
• [Starting and Managing Tasks](https://help.aliyun.com/zh/alinux/use-sysagent-to-start-and-manage-tasks)
• [SysAgent Console](https://alinux.console.aliyun.com/sysom-ai/ops-assistant)

The guides and console describe the product and its usage. This Skill uses the Alibaba Cloud CLI: `aliyun sysom sysagent`.

Observability

Before any cloud API invocation, read `references/manifest.json` from this skill's root and use only its top-level non-empty string `version` as `{skill-version}`. If the file is missing, invalid, or the field is absent/empty/not a string, STOP and report the error. Never invent, guess, or reuse a version from another skill.

Bind version and session to the current skill name and skill root. Before this skill's first cloud API invocation in a conversation, generate a fresh random 32-character lowercase hexadecimal session ID. Reuse that session ID for this skill throughout the conversation; each skill MUST use a distinct session ID. NEVER copy one from documentation, examples, another skill, or a previous conversation, and NEVER send the literal `{session-id}` placeholder. When switching skills or returning to this skill, reread this skill's manifest; never cross-skill reuse either value.

This attribution ID is separate from cloud-side session IDs, run IDs, and request IDs. Local help and version checks do not carry this parameter.

**Rule: Every `aliyun` CLI command that calls a cloud API must include the `--user-agent` flag.**

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

--user-agent "AlibabaCloud-Agent-Skills/alibabacloud-sysagent/{session-id} skill-version/{skill-version}"

The entire UA value must be double-quoted because it contains a space. Do not skip, alter, or omit it on any `aliyun` API command. Markdown examples may omit the flag for brevity; append it to every actual execution.

---

Workflow

Step 1: Confirm Intent and Scope

Capture the user's goal, target, relevant resource region and time window, expected outcome, and any read-only or approval constraints. Use values the user already supplied; confirm any missing or ambiguous task parameters before execution. Submit the user's goal in natural language using the default SysAgent entry point. Use the user's language for visible updates and results.

Step 2: Prepare CLI, Plugin, and Identity

Follow [Environment Setup](references/setup.md) on the first SysAgent use in a local Agent conversation. Verify Aliyun CLI 3.4.0 or later and the SysOM plugin, then use `aliyun configure list` to inspect Profile metadata before the service probe. If no usable credential source is available, pause cloud calls while the user configures one outside the Agent conversation. Reuse successful checks while the executable, plugin environment, and identity are unchanged. Recheck only the affected part if one changes or fails.

Step 3: Submit or Resume the Execution

• For new work, save a logical request ID before using `ask`. Report acceptance only after `submissionStatus=accepted`. Keep a task-scoped receipt in the host's durable context: `sessionId`, `runId`, logical request ID, selected Profile if named, last observed status, and consumed `observation.cursor`. If the host cannot retain the receipt, give the user the session and run IDs for later recovery.
• For a progress or result request, use the original execution and identity with `run get`, `run watch`, or `result get`. If a receipt is unavailable, use a read-only lookup or ask the user to identify the run. Never pick the most recent task by default or submit a replacement. Closing the terminal or stopping local observation does not cancel the cloud task.
• Use `run cancel` only if the user explicitly wants to stop the identified cloud execution. Check its status with `run get`; the cancellation receipt alone is not a terminal status.

Step 4: Observe and Report Progress

Use short `run watch` windows so the user can see updates between calls. Continue from the last consumed `observation.cursor`, update the receipt after processing each batch, and read further pages when `observation.hasMore=true`. See [the CLI reference](references/sysagent-cli.md#observe-an-execution) for replay and streaming behavior.

When the user asks you to complete a cloud task, keep observing the same execution until it ends or requires user input.

Use the CLI's JSON or JSONL as input. In the user's language, explain what was checked, what the output shows, or