Alibabacloud Pai Eas Service Diagnose
PAI-EAS service diagnosis and troubleshooting. Diagnose startup failures, error logs, slow responses, instance restarts, OOMKilled, ImagePullBackOff, CrashLo...
Rank
62
Safety
84
Downloads
1.1k
Updated
Oct 11, 2026
Version
0.0.1
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.1release · observed Jul 13, 2026
- Handshake status
- UNKNOWNsecurity
Install and run
Setup complexity: low.
clawhub skill install s173swjet2yrebzqrp6hjkvmy583mxef:alibabacloud-pai-eas-service-diagnose- Install using `clawhub skill install s173swjet2yrebzqrp6hjkvmy583mxef:alibabacloud-pai-eas-service-diagnose` 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-pai-eas-service-diagnose before using production credentials.
Contract: missing
curl -s "https://www.xpersona.co/api/v1/agents/clawhub-sdk-team-alibabacloud-pai-eas-service-diagnose/snapshot"
Documentation
CLAWHUB
143,504 characters of source documentation, loaded on request.
Extracted files
5 files captured from the source.
SKILL.md
--- name: alibabacloud-pai-eas-service-diagnose description: | PAI-EAS service diagnosis and troubleshooting. Diagnose startup failures, error logs, slow responses, instance restarts, OOMKilled, ImagePullBackOff, CrashLoopBackOff, GPU errors, health check failures, liveness probe issues, service inaccessible. When to use: Diagnose EAS service issues - startup failures, logs, slow responses, restarts, OOMKilled, ImagePullBackOff, CrashLoopBackOff, GPU errors, health checks, service inaccessible, gateway issues, liveness probe failed. Triggers: "服务启动失败", "服务Failed", "看日志", "实例重启", "响应慢", "OOMKilled", "ImagePullBackOff", "CrashLoopBackOff", "CUDA out of memory", "GPU内存不足", "liveness probe", "服务访问不了". Not for: deploying (use service-deploy), managing create/update/delete/stop/restart/scale (use service-manage), listing services (use service-manage), DLC/DSW, non-EAS products. license: Apache-2.0 metadata: version: "1.0.0" domain: aiops owner: pai-eas-team contact: [email protected] tags: - pai-eas - diagnosis - troubleshooting - log-analysis - service-health required_tools: - aliyun - jq required_permissions: - "eas:DescribeService" - "eas:DescribeServiceLog" - "eas:DescribeServiceEvent" - "eas:DescribeServiceDiagnosis" - "eas:DescribeServiceInstanceDiagnosis" - "eas:ListServiceInstances" - "eas:ListServiceContainers" - "eas:ListServices" - "eas:DescribeResource" - "eas:DescribeGateway" --- # PAI-EAS Service Operations Diagnosis Helps users diagnose issues with running PAI-EAS services. > **🔴🔴 [MUST — READ BEFORE ANYTHING ELSE] Two failure modes that cause task failure:** > > 1. **Listing is NOT diagnosing.** After `ListServices`/`list-services` returns > the target service, you MUST immediately continue and run the FULL diagnostic > workflow (`DescribeService` → `DescribeServiceEvent` → `DescribeServiceLog` > multi-keyword → `ListServiceInstances` → `ListServiceContainers` → > `DescribeServiceDiagnosis`) on a chosen service. NEVER stop after listing. > 2. **Always finish with an analysis section.** Every diagnosis MUST end with a > written health-analysis + recommendation section. If the user described a > symptom (e.g. "CUDA out of memory") that the live data does NOT show, you > MUST still add a secondary section explaining common causes and fixes for > that described symptom. Never end the turn with only raw command output. --- ## Installation Install the Aliyun CLI (>= 3.3.3, required baseline for plugin ecosystem compatibility) using a trusted package manager. On macOS, use Homebrew: ```bash brew install aliyun-cli aliyun version ``` On other platforms, download the versioned release tarball directly from `https://aliyuncli.alicdn.com/`, verify its checksum, and extract it manually before use (see the [CLI Installation Guide](references/cli-installation-guide.md)). Do not pipe remote scripts
_meta.json
{
"ownerId": "kn74p5w8ywv6prh40g0s82gmqh83nw54",
"slug": "alibabacloud-pai-eas-service-diagnose",
"version": "0.0.1",
"publishedAt": 1783930700514
}references/acceptance-criteria.md
# Acceptance Criteria: alibabacloud-pai-eas-service-diagnose **Scenario**: PAI-EAS Service Diagnosis **Purpose**: Skill test acceptance criteria --- # Correct CLI Command Patterns ## 1. EAS Service Diagnostic Operations ### Correct: Query service status ```bash aliyun eas describe-service --cluster-id cn-hangzhou --service-name my-service --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose ``` ### Incorrect: Missing --user-agent ```bash aliyun eas describe-service --cluster-id cn-hangzhou --service-name my-service ``` ### Incorrect: Using API format instead of plugin mode ```bash aliyun eas DescribeService --region cn-hangzhou --ServiceName my-service ``` ## 2. Log Query ### Correct: Keyword filtering ```bash aliyun eas describe-service-log --cluster-id cn-hangzhou --service-name my-service --keyword "error" --limit 20 --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose ``` ### Incorrect: Missing --service-name ```bash aliyun eas describe-service-log --cluster-id cn-hangzhou --keyword "error" --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose ``` ## 3. Event Query ### Correct: Query service events ```bash aliyun eas describe-service-event --cluster-id cn-hangzhou --service-name my-service --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose ``` ### Correct: Filter Warning events ```bash aliyun eas describe-service-event --cluster-id cn-hangzhou --service-name my-service --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose | jq '.Events[] | select(.Type == "Warning")' ``` ## 4. Instance Query ### Correct: List instances ```bash aliyun eas list-service-instances --cluster-id cn-hangzhou --service-name my-service --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose ``` ### Correct: List containers (requires --instance-name) ```bash # First get instance name aliyun eas list-service-instances --cluster-id cn-hangzhou --service-name my-service --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose | jq -r '.Instances[0].InstanceName' # Then list containers with instance-name aliyun eas list-service-containers --cluster-id cn-hangzhou --service-name my-service --instance-name my-service-xxxxx-yyyyy --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose ``` ## 5. Gateway Query ### Correct: Query gateway details ```bash aliyun eas describe-gateway --cluster-id cn-hangzhou --gateway-id gw-xxx --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose ``` ### Incorrect: Missing cluster-id ```bash aliyun eas describe-gateway --gateway-id gw-xxx --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose ``` --- # Diagnosis Flow Verification ## 1. Service Startup Failure Diagnosis ### Correct flow ```bash # 1. Check service status aliyun eas describe-service --cluster-id cn-hangzhou --service-name my-
references/api-reference.md
# Diagnostic API Quick Reference **Table of Contents** - [Service Status API](#service-status-api) - [Log API](#log-api) - [Event API](#event-api) - [Instance API](#instance-api) - [Diagnosis API](#diagnosis-api) - [Resource Group API](#resource-group-api) - [Gateway API](#gateway-api) - [Quick Diagnostic Command Summary](#quick-diagnostic-command-summary) ## Service Status API ### describe-service (Service Details) ```bash aliyun eas describe-service --cluster-id $CLUSTER_ID --service-name $SERVICE --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose ``` **Key fields**: | Field | Description | jq Path | |-------|-------------|---------| | Service name | Unique service identifier | `.ServiceName` | | Status | Current status | `.Status` | | Running instances | Normally running instances | `.RunningInstance` | | Total instances | Total instance count | `.TotalInstance` | | CPU | CPU cores | `.Cpu` | | Memory | Memory size | `.Memory` | | GPU | GPU count | `.GPU` | | Image | Container image | `.Image` | | Error message | Failure reason | `.Message` | **Status descriptions**: | Status | Description | |--------|-------------| | Creating | Being created | | Starting | Starting up | | Running | Running | | Updating | Being updated | | Stopping | Stopping | | Stopped | Stopped | | Failed | Failed | --- ### list-services (Service List) ```bash aliyun eas list-services --cluster-id $CLUSTER_ID --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose ``` **Common filters**: ```bash # Filter failed services aliyun eas list-services --cluster-id $CLUSTER_ID --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose | \ jq '.Services[] | select(.Status == "Failed")' # Filter services by resource group aliyun eas list-services --cluster-id $CLUSTER_ID --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose | \ jq '.Services[] | select(.ResourceId == "eas-r-xxx")' ``` --- ### describe-service-endpoints (Service Endpoints) ```bash aliyun eas describe-service-endpoints --cluster-id $CLUSTER_ID --service-name $SERVICE --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose ``` **Response fields**: | Field | Description | |-------|-------------| | `.InternetEndpoint` | Public endpoint | | `.IntranetEndpoint` | Internal endpoint | | `.Token` | Access Token | --- ## Log API ### describe-service-log (Service Logs) ```bash # Basic query aliyun eas describe-service-log --cluster-id $CLUSTER_ID --service-name $SERVICE --limit 100 --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose # Keyword filtering aliyun eas describe-service-log --cluster-id $CLUSTER_ID --service-name $SERVICE \ --keyword "error" --limit 50 --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-eas-service-diagnose # Time range aliyun eas describe-service-log --cluster-id $CLUSTER_ID --service-name $SERVICE \ --start-time "2026-03-19T00:00:0
references/cli-installation-guide.md
# Aliyun CLI Installation & Configuration Guide
Complete guide for installing and configuring Aliyun CLI.
> **Aliyun CLI 3.3.3+**: Supports installing and using all published Alibaba Cloud product plugins. Make sure to upgrade to 3.3.3 or later for full plugin ecosystem coverage.
## Installation
> **Note on `sudo mv ... /usr/local/bin/`**: The binary-install steps below use
> `sudo` only to place the `aliyun` executable into the system-wide `/usr/local/bin`
> directory, which requires administrator privileges. This is the standard,
> well-understood way to make a CLI available on `PATH` for all users. If you
> prefer NOT to use elevated privileges, install into a user-local directory
> instead and add it to your `PATH` — no `sudo` required:
>
> ```bash
> mkdir -p "$HOME/.local/bin"
> mv aliyun "$HOME/.local/bin/"
> export PATH="$HOME/.local/bin:$PATH" # add to ~/.bashrc or ~/.zshrc to persist
> ```
### macOS
**Using Homebrew (Recommended)**
```bash
brew install aliyun-cli
# Upgrade to latest
brew upgrade aliyun-cli
# Verify version (>= 3.3.3)
aliyun version
```
**Using Binary**
```bash
# Download
wget https://aliyuncli.alicdn.com/aliyun-cli-macosx-latest-amd64.tgz
# Extract
tar -xzf aliyun-cli-macosx-latest-amd64.tgz
# Move to PATH
sudo mv aliyun /usr/local/bin/
# Verify
aliyun version
```
### Linux
**Debian/Ubuntu**
```bash
# Download
wget https://aliyuncli.alicdn.com/aliyun-cli-linux-latest-amd64.tgz
# Extract and install
tar -xzf aliyun-cli-linux-latest-amd64.tgz
sudo mv aliyun /usr/local/bin/
# Verify
aliyun version
```
**CentOS/RHEL**
```bash
# Download
wget https://aliyuncli.alicdn.com/aliyun-cli-linux-latest-amd64.tgz
# Extract and install
tar -xzf aliyun-cli-linux-latest-amd64.tgz
sudo mv aliyun /usr/local/bin/
# Verify
aliyun version
```
**ARM64 Architecture**
```bash
# Download ARM64 version
wget https://aliyuncli.alicdn.com/aliyun-cli-linux-latest-arm64.tgz
# Extract and install
tar -xzf aliyun-cli-linux-latest-arm64.tgz
sudo mv aliyun /usr/local/bin/
```
### Windows
**Using Binary**
1. Download from: https://aliyuncli.alicdn.com/aliyun-cli-windows-latest-amd64.zip
2. Extract the ZIP file
3. Add the directory to your PATH environment variable
4. Open new Command Prompt or PowerShell
5. Verify: `aliyun version`
**Using PowerShell**
```powershell
# Download
Invoke-WebRequest -Uri "https://aliyuncli.alicdn.com/aliyun-cli-windows-latest-amd64.zip" -OutFile "aliyun-cli.zip"
# Extract
Expand-Archive -Path aliyun-cli.zip -DestinationPath C:\aliyun-cli
# Add to PATH (requires admin privileges)
$env:Path += ";C:\aliyun-cli"
[Environment]::SetEnvironmentVariable("Path", $env:Path, [System.EnvironmentVariableTarget]::Machine)
# Verify
aliyun version
```
## Configuration
### Quick Start
```bash
aliyun configure set \
--mode AK \
--access-key-id <your-access-key-id> \
--access-key-secret <your-access-key-secret> \
--region cn-hangzhou
```
All `aliyun configure` commands support non-interactive flags, which isAionUi
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!
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
cherry-studio
AI productivity studio with smart chat, autonomous agents, and 300+ assistants.
CopilotKit
The Frontend for Agents & Generative UI. React + Angular
Machine-readable data
The same record, as JSON, for agents and crawlers.
{
"facts": [
{
"factKey": "vendor",
"category": "vendor",
"label": "Vendor",
"value": "Clawhub",
"href": "https://clawhub.ai/sdk-team/skills/alibabacloud-pai-eas-service-diagnose",
"sourceUrl": "https://clawhub.ai/sdk-team/skills/alibabacloud-pai-eas-service-diagnose",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-11T05:56:37.011Z",
"isPublic": true
},
{
"factKey": "protocols",
"category": "compatibility",
"label": "Protocol compatibility",
"value": "OpenClaw",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-sdk-team-alibabacloud-pai-eas-service-diagnose/contract",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-sdk-team-alibabacloud-pai-eas-service-diagnose/contract",
"sourceType": "contract",
"confidence": "medium",
"observedAt": "2026-10-11T05:56:37.011Z",
"isPublic": true
},
{
"factKey": "traction",
"category": "adoption",
"label": "Adoption signal",
"value": "1.1K downloads",
"href": "https://clawhub.ai/sdk-team/alibabacloud-pai-eas-service-diagnose",
"sourceUrl": "https://clawhub.ai/sdk-team/alibabacloud-pai-eas-service-diagnose",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-11T05:56:37.011Z",
"isPublic": true
},
{
"factKey": "latest_release",
"category": "release",
"label": "Latest release",
"value": "0.0.1",
"href": "https://clawhub.ai/sdk-team/alibabacloud-pai-eas-service-diagnose",
"sourceUrl": "https://clawhub.ai/sdk-team/alibabacloud-pai-eas-service-diagnose",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-07-13T08:18:20.514Z",
"isPublic": true
},
{
"factKey": "handshake_status",
"category": "security",
"label": "Handshake status",
"value": "UNKNOWN",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-sdk-team-alibabacloud-pai-eas-service-diagnose/trust",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-sdk-team-alibabacloud-pai-eas-service-diagnose/trust",
"sourceType": "trust",
"confidence": "medium",
"observedAt": null,
"isPublic": true
}
],
"events": [
{
"eventType": "release",
"title": "Release 0.0.1",
"description": "alibabacloud-pai-eas-service-diagnose v0.0.1 – Initial Release - Provides autonomous diagnosis and troubleshooting for Alibaba Cloud PAI-EAS service issues, including startup failures, error logs, OOMKilled, and service inaccessibility. - Adds strict workflow requirements: always proceed beyond service listing to full diagnosis; ensure every diagnosis ends with a health analysis and recommendations section. - Details installation steps with secure Aliyun CLI installation, plugin setup, and per-session user-agent tracing for observability. - Enforces RAM permission and authentication pre-checks before running diagnostics. - Removes the obsolete skill-card.md file; fully reworks documentation for procedural accuracy and compliance.",
"href": "https://clawhub.ai/sdk-team/alibabacloud-pai-eas-service-diagnose",
"sourceUrl": "https://clawhub.ai/sdk-team/alibabacloud-pai-eas-service-diagnose",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-07-13T08:18:20.514Z",
"isPublic": true
}
]
}Record generated Oct 11, 2026.
