/alibabacloud-flink-workspace-ops

name: alibabacloud-flink-workspace-ops
description: |
  Use when user explicitly asks Flink/Ververica/Realtime Compute Console workspace operations:
  草稿(draft), SQL校验/执行, 部署(deployment), 作业(job), Session Cluster, namespace, 表(table), 成员(member), 变量(variable),
  或 checkpoint timeout 诊断, especially with workspace/deployment/job IDs (w-*, d-*, j-*, sc-*, draft-*).
  Also use when prompt asks to test/verify Flink Console lifecycle flow, safety guardrails, or parameter validation for these operations.
  This includes prompts such as create draft, deploy draft, list deployments, start/stop job, create/list session cluster, get tables, list variables.
  Also use when prompt explicitly asks to run `python scripts/flink_ververica_ops.py` for Flink Console workspace operations.
  Do not trigger for unrelated "workspace" contexts or generic cloud/platform tasks (ECS, OSS, RDS, Kafka, Spark, Kubernetes, billing, weather).
  Do not trigger for Flink instance lifecycle operations (create/scale/delete/renew); those belong to alibabacloud-flink-instance-manage.

license: Apache-2.0
compatibility: Requires Python dependencies in assets/requirements.txt and Alibaba Cloud credentials via default credential chain.
metadata:
  domain: aiops
  owner: flink-team
  allowed-tools: Bash Read Write

Alibaba Cloud Flink Console Ops

Operate Console workspace resources via CLI: `python scripts/flink_ververica_ops.py <command> [args]`

**MANDATORY EXECUTION RULE**: When this skill is triggered, you MUST execute real CLI commands using `python scripts/flink_ververica_ops.py`. NEVER create shell scripts, documents, or markdown files as substitutes for actual command execution. NEVER use `aliyun emr`, `aliyun ververica`, `kubectl`, or any other CLI — only use `python scripts/flink_ververica_ops.py`. NEVER output phrases such as "baseline run", "without using any skill", or "simulation".

AI-Mode Configuration for Alibaba Cloud CLI (`aliyun`)

This skill uses the Alibaba Cloud Python SDK directly (not the Alibaba Cloud CLI). If the user's environment also uses Alibaba Cloud CLI (`aliyun`) for other purposes, ensure plugins are up to date:

# Update plugins to latest version
aliyun plugin update
# Plugin mode examples (lowercase-hyphenated, never PascalCase)
aliyun ram list-policies-for-user --user-name <user_name>
aliyun ram list-access-keys --user-name <user_name>

Observability (MUST follow for every aliyun command)

Upon loading this skill, generate a random session ID (32-char lowercase hex string) once for the entire session. Use it as `{session-id}` below.

**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-flink-workspace-ops/{session-id}

Example (assuming session-id is `a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6`):

aliyun ecs describe-instances --biz-region-id cn-hangzhou --user-agent AlibabaCloud-Agent-Skills/alibabacloud-flink-workspace-ops/a1b2c3d4e5f6a7b8c9d0e1f2a3b4c5d6

Do not skip, alter the format, or omit `--user-agent` on any `aliyun` API command invocation.

**Script / Terraform execution:** When running Python SDK scripts or Terraform commands or bash scripts, inject the session-id via inline environment variable so the code can read it at runtime:

# Python SDK script (this skill's CLI)
SKILL_SESSION_ID={session-id} python scripts/flink_ververica_ops.py <command> [args]

# Terraform
SKILL_SESSION_ID={session-id} terraform apply

Scripts and Terraform configs should read `SKILL_SESSION_ID` from the environment (default to empty string if absent). This skill's `scripts/client.py` reads `SKILL_SESSION_ID` and sets the SDK `user_agent` to `AlibabaCloud-Agent-Skills/alibabacloud-flink-workspace-ops/{session-id}`, keeping the same session-id consistent across CLI, SDK, and Terraform channels.

Scope & Boundaries

**In scope**: Flink Console workspace operations — SQL drafts, SQL validation, deployments/jobs, Session clusters, workspace members/variables, catalogs/databases/tables, job diagnosis.

**Out of scope (do NOT handle)**:

• Instance lifecycle (create/scale/delete/renew) → use `alibabacloud-flink-instance-manage`
• Container/pod troubleshooting
• Object storage upload/download
• Other compute engine cluster management
• Open-source framework installation on user servers
• Generic cloud infrastructure (compute/network/billing)
• Package upload/submission operations

Trigger Conditions (CRITICAL)

Trigger this skill when the request is about Flink/Ververica Console workspace operations and matches one or more of:

1. Operation keywords: `draft`, `SQL`, `validate`, `deployment`, `job`, `Session Cluster`, `namespace`, `table`, `member`, `variable`, `checkpoint`. 2. Resource ID patterns: `w-*`, `d-*`, `j-*`, `sc-*`, `draft-*`. 3. Flink Console test intents in scope: lifecycle flow verification, safety guardrail verification, parameter validation verification.

Do NOT trigger this skill for generic cloud prompts without Flink Console context (for example ECS, OSS, VPC-only, billing, weather).

Boundary Response (IMPORTANT)

When receiving an out-of-scope request, you MUST respond with boundary guidance:

For instance lifecycle requests: > "This request involves instance management, which is NOT handled by this skill (alibabacloud-flink-workspace-ops). Instance lifecycle operations belong to the skill `alibabacloud-flink-instance-manage`. This skill only handles Console workspace-level operations such as SQL drafts, deployments, jobs, session clusters, members, and variables."

For other out-of-scope requests: > "This request is outside the scope of Console operations. This skill only handles Console workspace operations including: SQL drafts/validation, deployments/jobs, session clusters, workspace members/variables, and table managemen