preset-datasetslisted

# preset-datasets Use for dataset and database metadata inspection in a resolved Preset workspace. ## Always - Use `preset-api`, `preset-workspaces`, and when drift matters `preset-superset` first. - Default to metadata reads. - Treat samples, distinct values, datasource values, connection configuration, and exports as sensitive reads requiring confirmation. - 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, export, 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 Order 1. Resolve database connection. 2. Inspect schemas, tables, datasets, columns, and metrics metadata. 3. Prepare approval or routing summary for sensitive read, export, mutation, upload, cache, import, validation, or SQL execution. 4. Stop before sensitive reads, exports, mutations, uploads, cache changes, imports, validation, SQL execution, or credential-bearing c