Agent skill · aliyun
alibabacloud-dataworks-semantic
Always use this Skill for any Alibaba Cloud DataWorks semantic analysis job or run request, including read-only and preflight requests that intentionally make no API call, such as checking whether the public DataWorks semantic OpenAPI or dataworks-public plugin commands (for example create-semantic-job) are ready. It also applies when the requested outcome is only a refusal or a user choice with no API call. This includes comparing or disambiguating supplied semantic job candidates, validating or refusing an unsafe, path-traversal, or non-writable semantic result directory before any download, and inspecting artifacts for an exact run. Use it to create, run, stop, monitor, diagnose, or download results for semantic jobs backed by MaxCompute, Hologres, StarRocks, or an already uploaded CSV/XLSX reference. Do not use it for ordinary metadata lookup, lineage analysis, SQL development, workflow scheduling, file upload, published semantic model/version management, or semantic job deletion.
What it needs
About 8k tokens when loaded.
What this skill does
DataWorks Semantic Analysis Use only Alibaba Cloud DataWorks public OpenAPI operations exposed by the aliyun dataworks-public plugin to create a reusable semantic analysis job, submit or stop a run, monitor execution, and retrieve generated result files. Prerequisites Perform these checks once, in this order. Install or update the public DataWorks plugin before probing any product API command; do not first probe every command, discover the plugin is missing, and then repeat the same probes. Never pipe a remote installer into a shell. If the CLI is missing or older than 3.3.3, direct the user to the official Aliyun CLI installation documentation. Check credentials without printing secrets: The only allowed aliyun configure operation in this Skill is configure list. Never run aliyun configure set, including auto-plugin-install variants. Observability Session-id rules Generation: Generate the session-id exactly once at the start of each user or agent session: Format: The session-id must be exactly 32 lowercase hexadecimal characters. Consistency across CLI/SDK/Terraform: Reuse the same session-id for every CLI command, SDK request, and Terraform operation in the session, including retries, polling, and downloads. Never regenerate it per command or when switching tools. Generate a new value only for a new user or agent session. UA template declaration Use this canonical CLI flag template: For this Skill, every Aliyun CLI product API command must explicitly include its concrete form: Do not persist the User-Agent in Aliyun CLI configuration or an environment variable. Local management commands such as aliyun version, aliyun plugin ..., and aliyun configure list do not support the product API User-Agent flag; do not add it to them. Public API readiness gate After the prerequisite plugin install/update, confirm only the commands needed by the selected workflow before collecting parameters; do not probe unrelated operations or repeat a successful readiness check. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aliyun/alibabacloud-dataworks-semantic