What makes Alibabacloud Pai Rec Diagnosis notable?

1.2K downloads. Trust evidence available

How should Alibabacloud Pai Rec 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 Pai Rec Diagnosis

Alibaba Cloud PAI-Rec Engine Diagnostic and Configuration Validation Skill. Use for diagnosing PAI-Rec engine interface issues and validating engine configur... Skill: Alibabacloud Pai Rec Diagnosis Owner: sdk-team Summary: Alibaba Cloud PAI-Rec Engine Diagnostic and Configuration Validation Skill. Use for diagnosing PAI-Rec engine interface issues and validating engine configur... Tags: latest:0.0.3 Version history: v0.0.3 | 2026-06-17T07:23:50.720Z | auto alibabacloud-pai-rec-diagnosis 0.0.3 - Enforces that every aliyun API command must include a unique session-based --use

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.2k

Updated

Oct 11, 2026

Version

0.0.3

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.2K 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.2K downloadsadoption · observed Oct 11, 2026
Latest release: 0.0.3release · observed Jun 17, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: medium.

clawhub skill install s173swjet2yrebzqrp6hjkvmy583mxef:alibabacloud-pai-rec-diagnosis

Setup complexity is MEDIUM. Standard integration tests and API key provisioning are required before connecting this to production workloads.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

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

Documentation

CLAWHUB

143,821 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: alibabacloud-pai-rec-diagnosis
description: |
  Alibaba Cloud PAI-Rec Engine Diagnostic and Configuration Validation Skill.
  Use for diagnosing PAI-Rec engine interface issues and validating engine configurations.
  Triggers: "PAI-Rec", "engine diagnosis", "engine config validation", "pairec", "recommendation engine".
---

# PAI-Rec Engine Diagnosis and Configuration Validation

This skill provides comprehensive diagnostic and validation capabilities for Alibaba Cloud PAI-Rec (Programmable Recommendation System) engines, including interface troubleshooting and configuration analysis.

## Scenario Description

PAI-Rec is Alibaba Cloud's programmable recommendation system that provides intelligent recommendation capabilities. This skill helps users:

1. **Diagnose PAI-Rec Engine Interface Issues**: When engine API returns errors or unexpected results, trace the request through EAS service logs and engine configurations to identify root causes.

2. **Validate Engine Configurations**: Analyze engine configuration files for potential issues, inconsistencies, or misconfigurations before deployment.

**Architecture**: PAI-EAS Service + PAI-Rec Engine + Engine Configuration Management

### Key Components
- **PAI-EAS Service**: Elastic Algorithm Service hosting the recommendation engine
- **PAI-Rec Engine**: The recommendation engine processing requests
- **Engine Configuration**: Configuration files defining engine behavior
- **Service Logs**: EAS service logs containing request traces

---

## Installation

**Pre-check: Aliyun CLI >= 3.3.3 required**
> Run `aliyun version` to verify >= 3.3.3. If not installed or version too low,
> run `curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash` to install/update,
> or see `references/cli-installation-guide.md` for installation instructions.

**Pre-check: Aliyun CLI plugin update required**
> [MUST] run `aliyun configure set --auto-plugin-install true` to enable automatic plugin installation.
> [MUST] run `aliyun plugin update` to ensure that any existing plugins are always up-to-date.

---

## Authentication

> **Pre-check: Alibaba Cloud Credentials Required**
>
> **Security Rules:**
> - **NEVER** read, echo, or print AK/SK values (e.g., `echo $ALIBABA_CLOUD_ACCESS_KEY_ID` is FORBIDDEN)
> - **NEVER** ask the user to input AK/SK directly in the conversation or command line
> - **NEVER** use `aliyun configure set` with literal credential values
> - **ONLY** use `aliyun configure list` to check credential status
>
> ```bash
> aliyun configure list
> ```
> Check the output for a valid profile (AK, STS, or OAuth identity).
>
> **If no valid profile exists, STOP here.**
> 1. Obtain credentials from [Alibaba Cloud Console](https://ram.console.aliyun.com/manage/ak)
> 2. Configure credentials **outside of this session** (via `aliyun configure` in terminal or environment variables in shell profile)
> 3. Return and re-run after `aliyun configure list` shows a valid profile

---

## RAM Policy

> **[MUST] P

_meta.json

{
  "ownerId": "kn74p5w8ywv6prh40g0s82gmqh83nw54",
  "slug": "alibabacloud-pai-rec-diagnosis",
  "version": "0.0.3",
  "publishedAt": 1781681030720
}

references/acceptance-criteria.md

# Acceptance Criteria: alibabacloud-pai-rec-diagnosis

**Scenario**: PAI-Rec Engine Diagnosis and Configuration Validation
**Purpose**: Skill testing acceptance criteria

This document defines correct and incorrect patterns for the PAI-Rec diagnosis skill to ensure proper implementation and usage.

---

## Correct CLI Command Patterns

### 1. Product Names — Verify product name exists

#### ✅ CORRECT

```bash
# EAS product commands
aliyun eas describe-service --cluster-id cn-hangzhou --service-name test
aliyun eas describe-service-log --cluster-id cn-hangzhou --service-name test

# PAI-RecService product commands
aliyun pairecservice list-engine-configs --instance-id pairec-cn-xxxxx
aliyun pairecservice get-engine-config --instance-id pairec-cn-xxxxx --engine-config-id config-123
```

**Why correct:** Uses valid product names `eas` and `pairecservice` that exist in Aliyun CLI.

#### ❌ INCORRECT

```bash
# Wrong product names
aliyun pai-eas describe-service ...        # Product is 'eas', not 'pai-eas'
aliyun rec describe-service ...            # Product is 'pairecservice', not 'rec'
aliyun pairec list-engine-configs ...      # Product is 'pairecservice', not 'pairec'
aliyun pai list-engine-configs ...         # Product is 'pairecservice', not 'pai'
```

**Why incorrect:** These product names don't exist in the Aliyun CLI.

---

### 2. Command Names — Verify action exists under the product

#### ✅ CORRECT

```bash
# EAS commands
aliyun eas describe-service
aliyun eas describe-service-log

# PAI-RecService commands
aliyun pairecservice list-engine-configs
aliyun pairecservice get-engine-config
aliyun pairecservice apply-engine-config
aliyun pairecservice create-engine-config
aliyun pairecservice get-experiment-group
aliyun pairecservice get-experiment
```

**Why correct:** All commands use lowercase words connected with hyphens (plugin mode format).

#### ❌ INCORRECT

```bash
# Traditional API format (not plugin mode)
aliyun eas DescribeService                  # Use describe-service
aliyun eas DescribeServiceLog               # Use describe-service-log
aliyun pairecservice ListEngineConfigs      # Use list-engine-configs
aliyun pairecservice GetEngineConfig        # Use get-engine-config

# Wrong command names
aliyun eas get-service                      # Command is describe-service
aliyun eas list-logs                        # Command is describe-service-log
aliyun pairecservice get-configs            # Command is list-engine-configs
aliyun pairecservice describe-config        # Command is get-engine-config
```

**Why incorrect:** Must use plugin mode format (lowercase with hyphens), and exact command names.

---

### 3. Parameter Names — Verify each parameter exists for the command

#### ✅ CORRECT - EAS describe-service

```bash
aliyun eas describe-service \
  --cluster-id cn-hangzhou \
  --service-name embedding_recall \
  --region cn-hangzhou
```

**Parameters:**
- `--cluster-id`: Required, the cluster ID
- `--service-name`: Required, the servi

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

### 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 is the recommended approach —
it works in scripts, CI/CD pipelines, and agent-driven automation without hanging on stdin prompts.

**Where to Get Access Keys**

1. Log in to Aliyun Console: https://ram.console.aliyun.com/
2. Navigate to: AccessKey Management
3. Create a new AccessKey pair
4. Save the secret immediately — it's only shown once

### Configuration Modes

Aliyun CLI supports 6 authentication modes. All examples below use non-interactive flags.

#### 1. AK Mode (Access Key)

Most common mode for personal accounts and scripts.

```bash
aliyun configure set \
  --mode AK \
  --access-key-id LTAI5tXXXXXXX

references/config-validation.md

# PAI-Rec Engine Configuration Validation

Reference for `scripts/validate.py` — the JSON Schema + rule-based validator used by
Workflow 2 (Engine Configuration Validation) in `SKILL.md`.

---

## 1. Files

| Path | Purpose |
|------|---------|
| `scripts/validate.py` | Validator entry point (CLI + library). Loads a bundled JSON Schema (Draft-7) that describes the top-level engine-config structure. |

All files live inside this skill — no external skill dependency.

---

## 2. Dependencies

- Python 3.8+
- `jsonschema` >=4.0,<5.0 (optional but recommended):
  ```bash
  pip install "jsonschema>=4.0,<5.0"
  ```
  If `jsonschema` is not installed the script **still runs** but skips Schema checks
  and relies on the built-in rule validator only. A single warning-equivalent note
  is NOT emitted in this case, so install `jsonschema` for full coverage.

---

## 3. CLI Usage

```bash
# From a saved JSON file
python3 scripts/validate.py /tmp/engine-config.json

# Inline JSON string
python3 scripts/validate.py '{"RunMode":"product","RecallConfs":[...]}'

# From stdin (recommended when ConfigValue is already in a shell variable)
printf '%s' "$CONFIG_VALUE" | python3 scripts/validate.py --stdin

# Validate with experiment configs (reference-existence check)
python3 scripts/validate.py /tmp/raw_engine_config.json \
  --experiment-config /tmp/experiment_group_21.json \
  --experiment-config /tmp/experiment_44.json
```

### Exit codes

| Code | Meaning |
|------|---------|
| `0`  | Validation passed (no errors; warnings may still be printed). |
| `1`  | Validation failed (at least one `error`-severity finding). |
| `2`  | Input error — argument is not a readable file, not valid JSON, or stdin decode failed. |

### Output format

```
Validation finished: <E> error(s), <W> warning(s)

  [ERROR]   <json.path>: <message>
  [WARNING] <json.path>: <message>
  ...
```

`<json.path>` uses dotted / bracketed notation, e.g.
`RecallConfs[3]`, `SceneConfs.default.default.RecallNames[1]`,
`FilterConfs[0].DaoConf`.

### Fragment auto-wrapping

If the input is a single fragment (object containing `RecallType`, `FilterType`, or
`SortType` at the top level) and the corresponding `*Confs` array is missing, the
script automatically wraps it into `{ "<Conf>s": [ <fragment> ] }` before
validation. This lets you validate one recall / filter / sort entry in isolation.

---

## 4. Library Usage

```python
from scripts.validate import validate_config, ValidationError

errors: list[ValidationError] = validate_config(config_dict, use_schema=True)
for e in errors:
    print(e.severity, e.path, e.message)
```

`ValidationError` fields: `path`, `message`, `severity` (`"error"` | `"warning"`).

---

## 5. Rule Catalogue

### 5.1 Structural / Type checks (JSON Schema)

Enforced by the bundled JSON Schema (Draft-7) via `jsonschema.Draft7Validator`. Covers:

- Top-level keys: `RunMode`, `ListenConf`, `RecallConfs`, `FilterConfs`,
  `SortConfs`, `AlgoConfs`, `SceneConfs`, `FilterNames`, `SortNa

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.