What makes alibabacloud-ecs-gpu-diagnosis notable?

1.1K downloads. Trust evidence available

How should alibabacloud-ecs-gpu-diagnosis 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-ecs-gpu-diagnosis

Diagnose GPU issues on Alibaba Cloud ECS GPU instances: GPU device status, driver issues, and GPU hardware failures. Use when users ask to check the GPU status of their GPU instances, detect whether the GPU device is visible, verify that the GPU driver is installed correctly, or troubleshoot GPU anomalies such as GPU not visible or deep learning task failures. Run Console Diagnosis or Cloud Assistant Diagnosis (RunCommand) to detect GPU hardware failures, perform batch diagnosis of GPU servers, or create scheduled (periodic) diagnosis tasks via CreateCommand and InvokeCommand with Cron. Single-instance diagnosis runs Console Diagnosis and Cloud Assistant Diagnosis in parallel; batch and scheduled diagnosis use Cloud Assistant Diagnosis only. Supports streaming output of diagnostic results.

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.1k

Updated

Oct 11, 2026

Version

0.0.2

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: 0.0.2release · observed Aug 17, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s173swjet2yrebzqrp6hjkvmy583mxef:alibabacloud-ecs-gpu-diagnosis

Install using `clawhub skill install s173swjet2yrebzqrp6hjkvmy583mxef:alibabacloud-ecs-gpu-diagnosis` 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-ecs-gpu-diagnosis before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-sdk-team-alibabacloud-ecs-gpu-diagnosis/snapshot"

Documentation

CLAWHUB

77,445 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: alibabacloud-ecs-gpu-diagnosis
description: >
Diagnose GPU issues on Alibaba Cloud ECS GPU instances: GPU device status, driver issues, and GPU hardware failures.
Use when users ask to check the GPU status of their GPU instances, detect whether the GPU device is visible, verify that the GPU driver is installed correctly, or troubleshoot GPU anomalies such as GPU not visible or deep learning task failures.
Run Console Diagnosis or Cloud Assistant Diagnosis (RunCommand) to detect GPU hardware failures, perform batch diagnosis of GPU servers, or create scheduled (periodic) diagnosis tasks via CreateCommand and InvokeCommand with Cron.
Single-instance diagnosis runs Console Diagnosis and Cloud Assistant Diagnosis in parallel; batch and scheduled diagnosis use Cloud Assistant Diagnosis only. Supports streaming output of diagnostic results.
---

## Usage Instructions

Diagnose GPU device status, driver issues, and hardware failures on ECS instances using the following two diagnosis methods, **depending on the diagnosis mode**:
- **Console Diagnosis**: `CreateDiagnosticReport` API, creates a diagnostic report and polls for results.
- **Cloud Assistant Diagnosis**: `RunCommand` remotely executes the GPU health check plugin (`ACS-ECS-GpuCheck`) on the instance.

**Mode-dependent method selection:**
- **Single-instance diagnosis** (immediate): Console Diagnosis + Cloud Assistant Diagnosis **in parallel** (both methods launched simultaneously)
- **Batch diagnosis** (immediate): **Cloud Assistant Diagnosis ONLY** — one `RunCommand` call with all instance IDs
- **Scheduled diagnosis**: **Cloud Assistant Diagnosis ONLY** — `CreateCommand` + `InvokeCommand` with a Cron schedule (Console Diagnosis does NOT support scheduling). See the "Scheduled Diagnosis (Cloud Assistant Diagnosis ONLY)" section.

## Execution Constraints

- All steps MUST be executed in order; skipping steps is NOT permitted
- Each step MUST be verified as successful before proceeding to the next
- Inform the user of the current step being executed
- If any step fails, user confirmation MUST be obtained before continuing
- **Single-instance diagnosis**: Console Diagnosis and Cloud Assistant Diagnosis MUST execute **in parallel**, launched simultaneously. Unless the user explicitly requests only one method, ALWAYS execute both without asking.
- **Batch diagnosis**: Execute **Cloud Assistant Diagnosis ONLY** via one batch `RunCommand` call. Do NOT create or poll Console diagnostic reports for batch instances.
- **Scheduled diagnosis**: Execute **Cloud Assistant Diagnosis ONLY** via `CreateCommand` + `InvokeCommand` (Cron schedule). Do NOT use Console Diagnosis for scheduled tasks.
- **Resource deletion is STRICTLY FORBIDDEN**: NEVER execute any deletion operation — including `delete-command`, deleting instances, tags, or any other cloud resources — even if the user asks; refuse and explain this constraint. `stop-invocation` (stop, not delete) is permitted ONLY when the user exp

_meta.json

{
  "ownerId": "kn74p5w8ywv6prh40g0s82gmqh83nw54",
  "slug": "alibabacloud-ecs-gpu-diagnosis",
  "version": "0.0.2",
  "publishedAt": 1786946934709
}

references/cli-installation.md

# Alibaba Cloud CLI Installation Guide

## macOS

**Homebrew (Recommended):**

```bash
brew install aliyun-cli
```

**Manual Installation:**

```bash
# Intel chip
wget https://aliyuncli.alicdn.com/aliyun-cli-macosx-latest-amd64.tgz
tar -xzf aliyun-cli-macosx-latest-amd64.tgz
sudo mv aliyun /usr/local/bin/

# Apple Silicon (M1/M2/M3/M4)
wget https://aliyuncli.alicdn.com/aliyun-cli-macosx-latest-arm64.tgz
tar -xzf aliyun-cli-macosx-latest-arm64.tgz
sudo mv aliyun /usr/local/bin/
```

## Linux

```bash
# x86_64
wget https://aliyuncli.alicdn.com/aliyun-cli-linux-latest-amd64.tgz
tar -xzf aliyun-cli-linux-latest-amd64.tgz
sudo mv aliyun /usr/local/bin/

# ARM64
wget https://aliyuncli.alicdn.com/aliyun-cli-linux-latest-arm64.tgz
tar -xzf aliyun-cli-linux-latest-arm64.tgz
sudo mv aliyun /usr/local/bin/
```

## Windows

1. Download: https://aliyuncli.alicdn.com/aliyun-cli-windows-latest-amd64.zip
2. Extract to any directory (e.g., `C:\aliyun-cli`)
3. The directory MUST be added to the system PATH environment variable

**PowerShell Installation:**

```powershell
Invoke-WebRequest -Uri "https://aliyuncli.alicdn.com/aliyun-cli-windows-latest-amd64.zip" -OutFile "aliyun-cli.zip"
Expand-Archive -Path aliyun-cli.zip -DestinationPath C:\aliyun-cli
[Environment]::SetEnvironmentVariable("Path", $env:Path + ";C:\aliyun-cli", [System.EnvironmentVariableTarget]::Machine)
```

## Verify Installation

After installation, the following command MUST be executed to confirm successful installation:

```bash
aliyun version
```

A version number in the output indicates successful installation. The version MUST be >= 3.0.299 to support OAuth authentication.

After installation, the CLI MUST be updated to the latest version:

```bash
# macOS (Homebrew)
brew upgrade aliyun-cli

# macOS (manual) / Linux: re-download the latest version and overwrite
# Intel Mac
wget https://aliyuncli.alicdn.com/aliyun-cli-macosx-latest-amd64.tgz
tar -xzf aliyun-cli-macosx-latest-amd64.tgz && sudo mv aliyun /usr/local/bin/

# Apple Silicon Mac
wget https://aliyuncli.alicdn.com/aliyun-cli-macosx-latest-arm64.tgz
tar -xzf aliyun-cli-macosx-latest-arm64.tgz && sudo mv aliyun /usr/local/bin/

# Linux x86_64
wget https://aliyuncli.alicdn.com/aliyun-cli-linux-latest-amd64.tgz
tar -xzf aliyun-cli-linux-latest-amd64.tgz && sudo mv aliyun /usr/local/bin/

# Linux ARM64
wget https://aliyuncli.alicdn.com/aliyun-cli-linux-latest-arm64.tgz
tar -xzf aliyun-cli-linux-latest-arm64.tgz && sudo mv aliyun /usr/local/bin/

# Windows PowerShell
Invoke-WebRequest -Uri "https://aliyuncli.alicdn.com/aliyun-cli-windows-latest-amd64.zip" -OutFile "aliyun-cli.zip"
Expand-Archive -Path aliyun-cli.zip -DestinationPath C:\aliyun-cli -Force
```

After updating, `aliyun version` MUST be executed again to confirm the version has been updated.

## Common Issues

**command not found:** You MUST verify that the directory containing `aliyun` has been added to PATH.

```bash
which aliyun    # macOS/Linux
where aliyun    # Windows
```

references/ram-policies.md

# RAM Permission List

RAM permissions required for this Skill execution:

## Diagnostic Operation Permissions

`ecs:CreateDiagnosticReport` — Create ECS instance diagnostic report

`ecs:DescribeDiagnosticReports` — Query diagnostic report status and results

## Instance Query Permissions (for prerequisite checks)

`ecs:DescribeInstances` — Query ECS instance basic information, verify instance existence

`ecs:DescribeRegions` — Query ECS supported regions

## Cloud Assistant Permissions (for Cloud Assistant Diagnosis)

`ecs:RunCommand` — Execute cloud assistant commands on ECS instances

`ecs:DescribeInvocationResults` — Query cloud assistant command execution results

## Scheduled Diagnosis Permissions (for scheduled/periodic diagnosis)

`ecs:CreateCommand` — Create a cloud assistant command with the fixed GPU diagnosis script

`ecs:InvokeCommand` — Create a periodic schedule (Cron `--frequency`) to run the command on target instances

`ecs:DescribeInvocations` — Verify the scheduled task status (RepeatMode, Frequency, InvocationStatus)

`ecs:StopInvocation` — Stop a scheduled task when the user explicitly requests stopping/deleting it (stopping only; deletion is done manually in the ECS console)

skill-card.md

## Description:

Diagnoses GPU device status, driver installation issues, and hardware failures on Alibaba Cloud ECS GPU instances using Console Diagnosis and Cloud Assistant diagnosis modes.

This skill is ready for commercial/non-commercial use.

## Publisher:

[sdk-team](https://clawhub.ai/user/sdk-team)

### License/Terms of Use:

MIT-0

## Use Case:

Developers and cloud operations engineers use this skill to diagnose single-instance, batch, or scheduled GPU health checks for Linux Alibaba Cloud ECS GPU instances and interpret Console Diagnosis and Cloud Assistant results.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The skill gives agents high-impact Alibaba Cloud command authority for ECS diagnostic and Cloud Assistant operations.

Mitigation: Use a tightly scoped RAM identity with only the documented permissions and review commands before execution.

Risk: Untrusted instance lists, tag values, or region inputs could direct diagnosis commands at unintended resources.

Mitigation: Use explicit instance lists when possible, validate region and instance IDs, and avoid untrusted tag or region inputs.

Risk: CLI installation and plugin update steps depend on mutable external sources.

Mitigation: Verify Alibaba Cloud CLI and plugin sources independently before installation or update.

Risk: Scheduled diagnosis creates persistent cloud automation.

Mitigation: Track scheduled invocations, use stop-invocation only when explicitly requested, and clean up scheduled resources manually in the console.

## Reference(s):

- [Alibaba Cloud CLI Installation Guide](references/cli-installation.md)
- [RAM Permission List](references/ram-policies.md)
- [Alibaba Cloud CLI official installation documentation](https://help.aliyun.com/zh/cli/install-cli)
- [Alibaba Cloud GPU driver installation guide](https://help.aliyun.com/zh/egs/install-a-gpu-driver-on-a-gpu-accelerated-compute-optimized-linux-instance)

## Skill Output:

**Output Type(s):** [text, markdown, shell commands, configuration, guidance]

**Output Format:** [Markdown with inline shell commands and diagnosis summaries]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Streams diagnosis results as each method or instance completes; findings are grouped by diagnosis method.]

## Skill Version(s):

0.0.2 (source: server release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Github ReposUpdated 2d 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.