tachyon-clilisted

# Tachyon CLI Use this skill when inspecting Tachyon Platform state through the local `tachyon` CLI. ## Core Rules - Run the real CLI command when the user asks to check logs or build status. - Treat tokens, API keys, auth headers, Cloudflare tokens, and generated secrets in logs as secrets. - Do not echo secret values back to the user. Redact them in summaries. - Prefer exact app IDs, build IDs, tenant IDs, PR URLs, and Linear/GitHub issue context already provided by the user. - If the user provides a Cloud App URL or GitHub check URL, extract the app ID / tenant ID from it and start there. - Do not assume the active profile tenant is correct. Use the explicit tenant from the issue, URL, or app metadata when available. - If a command refreshes the token, do not mention the token value; it is fine to say the CLI refreshed auth successfully. ## Initial Setup (First-Time Use) Before running any `compute`/`ops`/`org` command, make sure an auth profile exists: ```bash tachyon auth list ``` If no profile is listed (or the list is empty), log in to create one. With no `--profile` given, the CLI creates/uses a profile named `default`: ```bash tachyon auth login ``` This opens a browser-based OAuth flow and saves tokens under the `default` profile. Once logged in, resolve which tenants that profile can act on instead of guessing an ID: ```bash tachyon org operators list --json ``` Pass `--tenant-id <tenant_id_or_alias>` explicitly on subsequent commands rather than relying