Back to skills

preset-embedding

Inspect embedded dashboard configuration, trusted domains, origins, guest-token routing, and embedded RLS routing through direct Superset API calls. 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-embedding

Use for embedded dashboard configuration reads and security-sensitive routing.

Always

  • Use preset-api, preset-workspaces, and when permissions matter preset-superset first.
  • Default to embedded configuration reads.
  • Route guest-token creation to preset-guest-tokens.
  • Route embedded RLS design/review to preset-embedded-rls.
  • Require explicit confirmation before embedded config mutations, guest tokens, trusted domain changes, or access-token key changes.

Decision Rules

  • Distinguish config reads from trusted-domain mutations, guest-token issuance, and RLS changes.
  • Require approval before broadening domains or issuing tokens.
  • Route domain, token, and RLS requests to the correct guardrail.
  • Avoid mutating embedded configuration.

Workflow Order

  1. Inspect embedded dashboard configuration.
  2. Classify domain, token, and RLS request type.
  3. Prepare approval summary for mutation or token issuance.
  4. Stop before broadening domains, mutating config, or issuing tokens.

Retrieve

Files (4)

Related Skills

No related skills found