preset-datasetslisted

# preset-datasets Use for dataset and database metadata inspection in a resolved Preset workspace. ## 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. Consult `preset-superset` only when version drift matters. - Run schema, table, dataset, column, and metric metadata reads directly. - Run samples, distinct values, and datasource values directly when the user asked in their own message with an explicit table/column target: row/value limit as a request parameter (default 100, hard cap 1000 without explicit confirmation), output summarized — no raw row dumps. - Connection configuration stays confirmation-gated; route credential-bearing database connection work to `preset-database-connections`. - Require confirmation before dataset/database mutations, uploads, cache changes, imports, exports, validation, or SQL execution. - Do not create, update, delete, duplicate, import, refresh schemas, upload files, test databases, validate SQL, or run SQL Lab queries from this skill without confirmation and focused routing. ## Decision Rules - Treat schema, table, dataset, column, and metric inspection as read-only metadata. - Distinguish metadata inspection from data-returning reads. - Use database identity from discovered environment facts or API results. - Avoid credential-bearing connection fields; route those to `preset-database-connections`. ## Workflow Or