tableau-to-hex-skill

---
name: tableau-to-hex-migration
description: Migrate a Tableau, Looker, or Power BI dashboard to a Hex app that matches it exactly — same queries, results, filters, colors, layout, and tooltips. Use when the user pastes a Tableau dashboard/view link, a Looker dashboard link, or a Power BI report link and asks to migrate, replicate, copy, or rebuild it in Hex, or mentions "Tableau to Hex" / "Looker to Hex" / "Power BI to Hex".
---

# Tableau/Looker/Power BI → Hex Dashboard Migration

Given a Tableau, Looker, or Power BI dashboard URL, produce a Hex app that is a faithful copy: same underlying queries and numbers, same filters, same colors/layout/labels, same tooltips. The build is driven by the **Hex agent** (`hex thread` CLI); source logic is extracted from the **ground truth** — Tableau's workbook file (.twbx), Looker's dashboard + query APIs, or Power BI's report definition (PBIR) + semantic model (TMDL/DAX) — and validated against the **same warehouse Hex queries** before it is handed to Hex.

All command snippets referenced below live in [reference.md](reference.md) — read it before starting Phase 1.

**Adaptivity rule**: the procedure is environment-agnostic; only the leaf commands vary. Phase 0 pins four environment choices — **source BI** (Tableau / Looker / Power BI), warehouse engine (Snowflake / BigQuery / Databricks / Postgres-Redshift), source hosting (Tableau Cloud vs self-hosted Server; Looker-hosted vs customer-hosted; Power BI capacity/licensing tier), and OS (macOS vs Linux) — and every snippet in reference.md is either shared or labeled per branch. Follow your branch exactly; don't mix branches mid-run. (The Tableau + Snowflake + macOS branch is the most battle-tested; the others are documented equivalents.) Phases 2–5 are source-agnostic: Phase 1 is the **source adapter**, and whatever the source, it must produce the same artifact — a written spec with ground-truth queries, calc definitions, parameters/filters, colors, layout, and a rendered PNG.

## Preconditions and non-goals

Confirm these before Phase 1, and tell the user about anything that applies:

- **Works for**: dashboards of charts, tables, and heatmaps whose datasources are reachable from a Hex warehouse connection (Tableau custom SQL or published sources; Looker explores/Looks on a warehouse connection Hex can also reach; Power BI DirectQuery/composite models over such a warehouse, or import models whose upstream source tables live in one), with quick filters and parameters (Looker: dashboard filters and listen-mapped tiles; Power BI: slicers and report/page/visual-level filters).
- **Power BI hard blockers — check before promising anything**: (a) an **import-mode model with no reachable upstream warehouse** (data lives only inside the pbix/semantic model) has nothing for Hex to query — stop and tell the user; (b) measures are **DAX, not SQL** — every measure must be *translated* to warehouse SQL and proven equivalent, which makes Phase 2 the dominant cost and complex DAX (nested `CALCULATE` context transitions, heavy time intelligence) a per-measure judgment call; (c) licensing walls — XMLA read and export-to-file need Fabric capacity or Premium-Per-User, and the `executeQueries` REST API needs its tenant setting enabled. Budget roughly 2× the Tableau/Looker correction rounds.
- **Hex workspace requirements**: the CLI must be enabled for the workspace, and Phase 3 depends on the **Hex agent (threads)** feature, which consumes the workspace's AI credits and may be disabled or exhausted on some plans. Verify early — `hex thread create` failing with a credits/feature error means the whole build path is blocked until the workspace admin enables it (there is no free fallback with comparable quality).
- **No clean Hex equivalent — agree a fallback with the user up front**: Tableau Stories; dashboard actions (filter/highlight/URL/set actions); row-level security and user filters; user-specific data blending.
- **Out of scope**: refresh schedules, permission migration, publishing/embedding, alert subscriptions. The deliverable is a draft Hex app at visual/numeric parity (Phase 5 evidence pack).
- A container usually holds **several dashboards** (a Tableau workbook, a Power BI report's pages, a Looker folder). After Phase 1 lists them, **ask the user two scope questions** and record the answers in the spec:
  1. **Which to migrate** — all of them, only the linked one, or a subset. Default to only the linked one if they don't care.
  2. **One app or one app with tabs** — if the selected dashboards are **tabs of the same logical report** (a Tableau workbook published with tabs, a Power BI report's pages), the default is **one Hex Generative app with a tab per dashboard** (generative apps support tab navigation; say so in the build prompt and keep each tab's SQL cells scoped to its own dashboard). Only genuinely unrelated dashboards get separate apps (one thread each).

  Whatever the grouping, never mix panels from a dashboard that isn't in scope into another dashboard's tab.

## Progress checklist

```
- [ ] Phase 0: Setup + ground rules (tooling, fidelity policy, run manifest)
- [ ] Phase 1: Extract the source spec (Tableau: twbx + XML; Looker: dashboard/query APIs; Power BI: PBIR + TMDL/DAX; + rendered PNGs)
- [ ] Phase 2: Validate every query against the warehouse (the source's numbers as truth)
- [ ] Phase 3: Build the Hex app with `hex thread create --new-project`
- [ ] Phase 4: Self-check loop (screenshot diff, YAML, numbers) until parity
- [ ] Phase 5: Deliver the parity evidence pack, get user sign-off
```

## Phase 0 — Setup and ground rules

Check what's installed; install only what's missing.

1. **Hex CLI** (required — this drives the whole build; macOS/Linux, Windows via WSL):
   ```bash