CRITICAL: Use only the Python SDK script provided by this Skill. All operations go through the DLF Python SDK (

alibabacloud-dlfnext20250310

) via

scripts/dlf_metadata_query.py

. This Skill does not invoke any shell-based command-line client and does not require AI-Mode configuration.

• DO NOT attempt access via any shell-based command-line client — DLF is not exposed through one in this Skill
• DO NOT use curl, wget, or other HTTP clients to call the DLF API directly
• MUST use the

  scripts/dlf_metadata_query.py

  script provided by this Skill, which wraps the DLF Python SDK
• All query operations are executed via

  python3 scripts/dlf_metadata_query.py <action> [options]

pip install -r requirements.txt

requirements.txt

alibabacloud-dlfnext20250310==3.0.0

Pre-check: Python SDK dependency

bash

python3 -c "from alibabacloud_dlfnext20250310.client import Client; print('SDK OK')"

If not installed, run

pip install -r requirements.txt

.

Pre-check: Alibaba Cloud Credentials Required

Use the default credential chain (CredentialClient) to obtain credentials automatically. Supported sources (in priority order):

1. Environment variables (ALIBABA_CLOUD_ACCESS_KEY_ID / ALIBABA_CLOUD_ACCESS_KEY_SECRET)
2. Configuration file (~/.alibabacloud/credentials)
3. ECS Instance RAM Role
4. OIDC Role ARN

Security Rules:

• NEVER read, echo, or print AK/SK values
• NEVER ask the user to input AK/SK directly in the conversation or command line
• NEVER explicitly handle or pass AK/SK in code — rely on the default credential chain

See https://help.aliyun.com/document_detail/378659.html for credential configuration details.

[MUST] Permission Failure Handling: When any command or API call fails due to permission errors at any point during execution, follow this process:

1. Read

   references/ram-policies.md

   to get the full list of permissions required by this SKILL
2. Pause and wait until the user confirms that the required permissions have been granted

IMPORTANT: Parameter Confirmation — Before invoking the API, the following user-specific parameters must be confirmed with the user; do not assume them. Region defaults to cn-hangzhou; if the user does not specify one, use the default without asking.

region

catalog_name

--catalog

catalog_id

--catalog-id

database

--database

table

--table

The script automatically reads AK/SK from environment variables and reports a clear error if they are missing. Region defaults to cn-hangzhou; use the default if the user does not specify one.

scripts/dlf_metadata_query.py

CRITICAL — list vs. list-*-details: pick the lightest action that satisfies the request.

• For listing names / IDs (including fuzzy search): use

  list-databases

  /

  list-tables

  . These call the

  ListDatabases

  /

  ListTables

  API.
• For full attributes / Schema / properties: use

  list-database-details

  /

  list-table-details

  /

  get-database

  /

  get-table

  . These call the heavier

  *-details

  /

  Get*

  APIs.
• Default to the lightweight

  list-*

  action unless the user explicitly asks for full configuration, Schema, or properties. Calling

  list-*-details

  when only names are needed is incorrect.

1. list-catalogs          → get catalog_name and catalog_id (names only)
2. list-databases         → use catalog_id to view available database names
3. list-tables            → use catalog_id + database to view available table names
4. get-table              → use catalog_id + database + table to view ONE table's Schema

Only step 4 (

get-table

) is a "details" call, because Schema is what the user actually asked for. Steps 1–3 stay on the lightweight

list-*

actions.

• List operations:

  {"count": N, "items": [...]}

• Get operations: a single JSON object
• Errors:

  {"error": "...", "hint": "..."}

1. Prefer the lightweight

   list-*

   action over

   list-*-details

   /

   get-*

   . When the task only requires listing resource names, IDs, or fuzzy matching, you MUST use

   list-catalogs

   /

   list-databases

   /

   list-tables

   (which call

   ListCatalogs

   /

   ListDatabases

   /

   ListTables

   ). Only use

   list-*-details

   or

   get-*

   when the user explicitly asks for full configuration, Schema, columns, properties, owner, or location. Reaching for the heavier API when the lighter one suffices is incorrect.
2. List before Get: use list-catalogs to obtain catalog_id first, then use catalog_id to query databases and tables.
3. Use fuzzy search with the lightweight action: the

   --pattern

   argument supports fuzzy matching; use it on

   list-tables

   (not

   list-table-details

   ) unless full Schema is also requested.
4. Pagination: use

   --max-results

   and

   --page-token

   for paginated queries when there is a lot of data.
5. Catalog ID vs Name: when querying Database/Table, use

   catalog_id

   (e.g. clg-paimon-xxxx), not the catalog name.