preset-supersetlisted

# preset-superset Use before domain-specific workspace API calls when endpoint drift, permissions, or feature availability matter. ## Always - Auth and conventions come from `preset-api` (JWT exchange, base URLs, Rison); resolve the workspace hostname through the Management API when it is not already known. - Send bearer tokens only to workspace hostnames resolved from the Preset Management API. - Prefer the workspace `/api/v1/_openapi` and `/version` over generic Superset docs. - Keep this skill read-only discovery. ## Decision Rules - Use discovered workspace host and API facts. - Classify version, OpenAPI, current-user, permissions, and menu calls as read-only discovery. - Identify follow-up calls that need confirmation. - Avoid assuming endpoints before discovery. ## Workflow Order 1. Resolve workspace hostname. 2. Read version, OpenAPI, current-user, permissions, and menu capabilities. 3. Classify follow-up risk. 4. Redact credentials and tokens. ## Retrieve - Version and OpenAPI: [references/version-and-openapi.md](references/version-and-openapi.md) - Current user and roles: [references/current-user-and-permissions.md](references/current-user-and-permissions.md) - Menu and feature discovery: [references/menu-and-feature-discovery.md](references/menu-and-feature-discovery.md) - Safety classification for data, export, credential, or execution endpoints: [references/workspace-api-safety.md](references/workspace-api-safety.md) ## Do Not - Do not run SQL, fetch ch