mode-to-sigma

Mode → Sigma

Phase numbering is local to this skill; the canonical Assess→Discover→Reuse→ Convert→Post-DM→Build→Layout→Parity→Security→Enhance arc and this skill's mapping live in docs/phase-schema.md (full clone only — see repo docs/phase-schema.md).

Assessment is a separate skill and isn't installable yet. Tenant-level inventory, dedup, and a value/cost migration shortlist are mode-assessment's job — it exists in this plugin's skills/ directory but is a scaffold and is not registered in marketplace.json/AGENTS.md for this release (SP1 ships the converter only). Pick the Report to migrate some other way (the Report's URL/token) and run this skill directly.

Run the phases below in order, via the one-command orchestrator — ruby scripts/migrate-mode.rb --report <token> --connection-id <id> --folder-id <id> — which shells out to each phase script and stops at the first hard-gate failure rather than leaving a skipped gate for a human to notice.

Phase 0 — Discover (C2)

ruby scripts/mode-discover.rb --report <token> pulls the Report's Queries, Charts, and Filters, and samples each Query's live output columns by triggering a fresh run (Mode has no static schema endpoint for a query's result set).

Phase 1 — Reuse check (C3)

build-dm.rb builds a mode-signature.json (same shape find-or-pick-dm.rb expects from every converter) and calls it with --auto-pick before building a new Data Model — if a prior Sigma DM already wraps the same warehouse tables, extend it instead of creating a new one.

Phase 2 — Build the Data Model (C4)

Every Mode Query becomes one sql-kind Sigma table element, wrapping its raw SQL verbatim — no formula translation, since the SQL already runs against the target warehouse.

Phase 3 — Post + read back (C5)

post-dm.rb POSTs a new Data Model (or PUTs the existing one Phase 1 chose to extend) and reads back the server-assigned element ids. Hard gate: no workbook-building step runs before this.