/alibabacloud-pai-dlc-job

name: alibabacloud-pai-dlc-job
description: |
  Alibaba Cloud PAI-DLC (Deep Learning Containers) job management skill. Covers: distributed training job CRUD, monitoring (logs and events), and  GPU sanity check. Triggers: "DLC", "PAI-DLC", "create-job", "list-jobs", "get-job", "stop-job", "update-job", "get-pod-logs", "get-job-events", "get-pod-events", "list-job-sanity-check-results".

PAI-DLC Deep Learning Job Management

Manage deep learning training jobs on Alibaba Cloud PAI-DLC (Platform for AI - Deep Learning Containers) service.

Scenario Description

PAI-DLC is a distributed training service provided by Alibaba Cloud's AI Platform PAI, supporting:

• **Job Creation and Execution** — Create distributed training jobs for TensorFlow,

PyTorch, XGBoost, and other frameworks

• **Job Monitoring** — Get job status, logs, events, and monitoring metrics
• **Compute Health Check** — Check health status of GPU and other compute devices
• **Job Management** — Update and stop jobs

**Architecture**: PAI Workspace + DLC Job + Computing Resources (ECS public pay-as-you-go or Lingjun dedicated quota) + AIWorkSpace catalog (images / datasets / code sources / quotas / workspaces).

Installation Requirements

> **Pre-check: Aliyun CLI >= 3.3.1 required** > Run `aliyun version` to verify version >= 3.3.1. If not installed or version is too low, > see [references/cli-installation-guide.md](references/cli-installation-guide.md) for > installation instructions. > Then [Required] run `aliyun configure set --auto-plugin-install true` to enable > automatic plugin installation.

> **Note on `--user-agent`:** Every API-invoking `aliyun` command in this skill MUST > include `--user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-dlc-job/${SESSION_ID}` > (unified User-Agent + session-id template — see [Observability](#observability) for > the generation rules). Client-side helpers (`aliyun version`, > `aliyun configure ...`, `aliyun plugin ...`, `aliyun <product> --help`) do not > invoke remote APIs and therefore do not require the flag.

> **Network timeout & retry (rule `--help` doesn't enforce):** `aliyun` CLI > defaults to 10s connect / 10s read with no retry. For long-running flows > (large list, slow region) explicitly raise via global flags > `--connect-timeout 15 --read-timeout 30 --retry-count 2`. Never rely on the > default for user-confirmed high-risk calls (`stop-job` / `delete-*`).

aliyun version
aliyun configure set --auto-plugin-install true
aliyun pai-dlc --help
aliyun aiworkspace --help >/dev/null 2>&1 || aliyun plugin install --names aliyun-cli-aiworkspace
aliyun plugin update

Observability

> **Why:** every PAI-DLC API call issued by this skill MUST carry a unified > User-Agent so platform-side tracing can attribute the request to this skill > and correlate all calls within a single agent session.

User-Agent template

Every API-invoking `aliyun` command MUST pass:

--user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-dlc-job/{session-id}

• Prefix `AlibabaCloud-Agent-Skills/alibabacloud-pai-dlc-job` is fixed — never alter it.
• `{session-id}` is a per-session identifier generated by the rules below.
• Client-side helpers (`aliyun version`, `aliyun configure ...`,

`aliyun plugin ...`, `aliyun <product> --help`) do NOT invoke remote APIs and therefore do NOT require the flag.

session-id generation rules

1. Generate the session-id **once** at the start of the skill session, before the first API call. 2. Format: lowercase, no spaces, no slashes. Recommended `uuidgen | tr 'A-Z' 'a-z'` or `$(date +%s)-$RANDOM`. 3. **Reuse the same session-id for every command** in the session — never regenerate per call. This lets tracing group all calls of one session. 4. Export it once and reference the shell variable in every API call:

SESSION_ID=$(uuidgen | tr 'A-Z' 'a-z')
export SESSION_ID
# every API-invoking command then appends:
#   --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-dlc-job/${SESSION_ID}
aliyun pai-dlc list-jobs --region <r> \
  --user-agent AlibabaCloud-Agent-Skills/alibabacloud-pai-dlc-job/${SESSION_ID}

> **Do NOT use `aliyun configure ai-mode`** to set the User-Agent. That mode is > deprecated for skills. Always pass `--user-agent` explicitly per command with > the session-id template, so each session is independently traceable.

## Environment Variables

This skill does not require any custom environment variables. Credentials are handled
by the Alibaba Cloud CLI configuration (see Authentication below). Optionally:

| Variable | Required | Purpose |
|----------|----------|---------|
| `ALIBABA_CLOUD_PROFILE` | Optional | Selects a non-default `aliyun configure` profile |
| `ALIBABA_CLOUD_REGION_ID` | Optional | Default region when `--region` is omitted (still recommended to pass `--region` explicitly) |

Do NOT export `ALIBABA_CLOUD_ACCESS_KEY_ID` / `ALIBABA_CLOUD_ACCESS_KEY_SECRET` from
within this session; configure them outside (`aliyun configure` or shell profile).

## Authentication Configuration

> **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 Permissions

> **[MUST] P