القائمة
Guide the user through creating and validating their credentials.local file for connecting to Alation. Covers local development, Cowork, and container environments.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when the user wants to discover, find, or browse data assets in the Alation catalog, data products, or marketplaces. Triggers: search catalog, find tables, list data sources, browse schemas, show columns, what data do we have, what tables exist, explore database, describe table, what's in this data source, show me the schema, list schemas, list columns, what databases do we have, show table structure, describe this data source, find data products, list data products, what data products do we have, search products, show available products, what products are in the marketplace, browse marketplace, which product has sales data. Use this skill when the user wants to know what data exists, understand table/column structure, or find data products — not when they want actual query results or numbers. Not for answering data questions or running queries — use ask instead. Not for creating or managing data products — use curate instead.
Use when the user asks a data question, wants to run a query against a data product, chat with an AI agent, or invoke a tool. Triggers: run SQL, run a query against a data product, ask agent, chat with agent, execute query, invoke tool, call tool, get answer, analyze data, how many, what is the total, count of, sum of, average, compare, trend, show me orders, pull revenue, what were sales, run this SELECT. A data product ID should be known before using this skill. If the user asks a vague data question and no product is identified, route through explore first to find the right product. Not for finding or browsing data products — use explore instead. Not for browsing catalog structure — use explore instead. Not for recurring/scheduled queries — use automate instead.
Use when the user wants to create, run, schedule, or debug automated workflows and recurring jobs. Triggers: create workflow, schedule report, automate query, run flow, send me a daily/weekly email, cron schedule, recurring report, debug workflow, flow not running, execution stuck, schedule not triggering, execute workflow, run this every day/week/month, set up recurring, automate this. Key signal: any mention of recurring, scheduled, daily, weekly, or automated execution means this skill, not ask. Not for one-time queries — use ask. Not for creating agents or tools — use configure.
Use when the user wants to create, modify, or manage AI agents, custom tools, LLM configurations, or data source connections. Triggers: create agent, configure agent, clone agent, publish agent as tool, create HTTP tool, create SMTP tool, add tool, configure LLM, bring your own model, BYOM, add data source, create connection, parameter bindings, tool authentication, set up agent, set up tool, manage LLM credentials. Key signal: if "set up" refers to infrastructure (agents, tools, LLMs, connections), use this skill. If "set up" refers to scheduling or automation, use automate. Not for scheduling or workflows — use automate. Not for creating data products — use curate.
Use when the user wants to create, update, or manage data products, publish or unpublish data products to a marketplace, manage marketplaces, enrich catalog metadata, add descriptions to tables or columns, set tags, set custom field values, check data product standards, manage product versions, or mark a version as ready. Also use for: product spec, product schema, delivery systems, record sets, marketplace badges, minimum standards, set up a new data product, define a product, annotate tables, enrich metadata. Use this skill any time the user mentions data products in a creation or management context, or wants to add/edit metadata on catalog objects. Not for querying data products — use ask. Not for browsing catalog — use explore. Not for creating data source connections — use configure.
Injected at session start. Provides overview of the Alation plugin, skill routing, and guidance on working with users.
| name | setup |
| description | Guide the user through creating and validating their credentials.local file for connecting to Alation. Covers local development, Cowork, and container environments. |
Guide the user through creating and validating their credentials.local file.
setup check first and after any change.| Task | CLI Command |
|---|---|
| Check if setup is complete | scripts/run-cli setup check |
| Save credentials to file | scripts/run-cli setup credentials --base_url <URL> ... |
| Log in via OAuth (local) | scripts/run-cli setup login |
| Log in via OAuth (Cowork/container) | scripts/run-cli setup login --cowork |
| Complete Cowork OAuth with redirect URL | scripts/run-cli setup login --cowork --code "<URL>" |
setup checkscripts/run-cli setup check
This returns JSON with five sections: credentials_file, token, api, environment, and ready.
Evaluate in this order (first match wins):
ready: true -> setup is complete, go to step 6.credentials_file.found: false -> go to step 2.credentials_file.auth_method is null → go to step 3credentials_file.auth_method: "oauth" and token.found: false -> go to step 4.credentials_file.auth_method: "oauth" and token.expired: true -> go to step 4.api.authenticated: false -> go to step 5.Ask the user which authentication method to use once:
http://127.0.0.1:18722/callback.Ask the user for their values in a single message. Do not present options, guesses, or prefilled URLs — just ask directly for what's needed.
OAuth — ask for: base_url, client_id, and client_secret (note client_secret is optional for public clients).
Username/password — ask for: base_url, username, and password.
Run the credentials command with the values provided:
OAuth:
scripts/run-cli setup credentials --base_url <URL> --client_id <ID> --client_secret <SECRET>
Or, if there's no client secret:
scripts/run-cli setup credentials --base_url <URL> --client_id <ID>
Username/password:
scripts/run-cli setup credentials --base_url <URL> --username <USER> --password <PASS>
If you ever notice SSL errors or a self-signed certificate, with user approval, add --disable_ssl_verification. You must get user approval for this.
The command outputs JSON with {"status": "ok", "path": "..."} on success. If there's a base_url_mismatch error, then request approval from the user to re-run with --force which will overwrite the existing credentials.
On success, return to step 1 to check the setup again.
Use this step only for OAuth-based setup when token is missing/expired.
Check environment.container from the step 1 setup check output to determine which flow to use.
Local environment (not in Cowork/container):
scripts/run-cli setup login
This opens a browser window for the user to log in. On success, prints the check result as JSON.
Cowork/container environment — use the --cowork flag for a two-step manual flow:
Step 1 — start the flow:
scripts/run-cli setup login --cowork
This returns JSON with status: "pending" and an auth_url field. Show the auth_url to the user and ask them to complete login in browser. Clearly and concisely explain that the user will need to copy the redirect URL from their browser back into the chat.
Step 2 — the user visits the URL in their browser, authorizes, and gets redirected to a page that fails to load. They paste the full redirect URL into chat. Complete the flow:
scripts/run-cli setup login --cowork --code "<REDIRECT_URL>"
The --code flag accepts either a bare authorization code or a full redirect URL (e.g., http://127.0.0.1:18722/callback?code=ABC&state=XYZ).
On success, return to step 1 to check the setup again.
Note: An Alation admin must register http://127.0.0.1:18722/callback as an allowed redirect URI for the OAuth client.
If api.authenticated: false, check the api.error field and:
setup login (step 4)api.reachable: false): Ask the user to verify base_url, VPN, or network connectivity--disable_ssl_verification after explicit user approval.When ready: true, tell the user setup is complete. If the user has no clear intent beyond setup, then suggest 2-3 things they could try, drawn from the examples below. Pick what's most relevant to anything the user has mentioned so far. If you have no signal, default to the first two.
Example suggestions (adapt, don't recite):
configureconfigureexploreaskMistake: Running setup login before credentials exist.
Why it seems reasonable: the user said "log me in."
Instead: Always run setup check first. If no credentials file exists, go to step 2.
Mistake: Using --cowork in a local environment, or omitting it in a container.
Why it seems reasonable: the user didn't specify their environment.
Instead: Check environment.container from setup check. Use --cowork only when container: true.
Mistake: Guessing or prefilling the user's base URL, client ID, or credentials. Why it seems reasonable: you might infer the URL from context. Instead: Always ask. Credentials must come directly from the user.
Mistake: Re-prompting for all credentials when only one value is wrong.
Why it seems reasonable: starting fresh feels safer.
Instead: Ask for just the corrected value and re-run setup credentials with all values.
configure, not setup.