Back to skills

preset-import-export

Inspect and route direct Superset import/export workflows for dashboards, charts, datasets, databases, saved queries, themes, and asset bundles. Use only for direct API workflows; Do not use for MCP-only work.

Richard Fogaca NienkotterRichard Fogaca Nienkotter
Updated 6/5/2026
View source

Documentation

preset-import-export

Use for workspace asset import/export endpoint selection and disclosure review.

Always

  • Use preset-api, preset-workspaces, and preset-superset first.
  • Treat imports as mutations and exports as potential disclosure of SQL, metadata, UUIDs, tags, and credential-bearing fields.
  • Require confirmation naming workspace, endpoint, object IDs or bundle, and expected disclosure or mutation.
  • Route overwrite, sparse-update, all-assets restore, database import, and secret-bearing import to preset-destructive-imports.

Decision Rules

  • Distinguish export disclosure from import mutation.
  • Classify overwrite imports as destructive.
  • Disclose bundle secret handling.
  • Require validation before import.

Workflow Order

  1. Inspect request and bundle metadata.
  2. Choose export or import path.
  3. Prepare disclosure or mutation approval summary.
  4. Stop before export or import execution.

Retrieve

Files (1)

Related Skills

No related skills found