build-migrate-chartlisted

# Build: /migrate-chart You are about to generate a `/migrate-chart` skill customised to this company's source tool, target tool and access setup. This builder is **tool-agnostic**: it does not assume Looker, Lightdash or anything else. It grows the skill from what it finds and what you tell it. Complete all three phases first. ## Phase 1 — Inspect (detect before you ask) 1. **Detect the source tool from artefacts in the repo.** Look for: - LookML (`*.model.lkml`, `*.view.lkml`) → Looker - `lightdash.config.yml` / `meta` blocks in dbt `schema.yml` → Lightdash - `.twb`/`.twbx` references, Tableau workbook exports → Tableau - Metabase card/dashboard JSON exports, Power BI deployment pipelines, Superset assets Record what you find. Absence of artefacts is normal — much BI content lives only in the tool, not the repo. 2. **Detect the target.** Same signals. If both source and target configs exist, extract the target's conventions already in use: naming, labels, folder/space structure, what gets hidden. 3. **Map the dbt layer, if present.** Charts backed by dbt models migrate cleanly; charts backed by tool-side SQL (Looker PDTs, Tableau custom SQL, Metabase native questions) are the hard cases. Sample what you can and estimate the split — it defines the migration's difficulty. 4. **Check what access already exists.** MCP server configs (`.mcp.json`, `.claude/settings.json`), API credentials referenced in env files (never read secret values — only note which integ