gooddata-assessment

Estrellas9

Forks9

Actualizado27 de julio de 2026 a las 15:53

Take inventory of a GoodData Cloud / GoodData.CN estate and produce a migration-readiness readout — workspace, dataset, metric, insight, and dashboard counts; a MAQL-complexity histogram (which metrics use BY / WITHIN / BY ALL / FOR time transforms); an insight visualization-type mix; and per- dashboard AUTO / HINT / MANUAL / UNHANDLED tags scored against the gooddata-to-sigma converter's actual coverage. Use when a user wants to scope a GoodData→Sigma migration, audit estate sprawl, or pick which dashboards to convert first. Read-only, all-free pre-scoping over the declarative workspace export. Also assesses the legacy GoodData Platform (classic /gdc, SST/TT auth) and sweeps EVERY project a user can access under one domain in a single run.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

twells89

twells89/sigma-migration-skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

10 archivos

SKILL.md

readonly

name	gooddata-assessment
description	Take inventory of a GoodData Cloud / GoodData.CN estate and produce a migration-readiness readout — workspace, dataset, metric, insight, and dashboard counts; a MAQL-complexity histogram (which metrics use BY / WITHIN / BY ALL / FOR time transforms); an insight visualization-type mix; and per- dashboard AUTO / HINT / MANUAL / UNHANDLED tags scored against the gooddata-to-sigma converter's actual coverage. Use when a user wants to scope a GoodData→Sigma migration, audit estate sprawl, or pick which dashboards to convert first. Read-only, all-free pre-scoping over the declarative workspace export. Also assesses the legacy GoodData Platform (classic /gdc, SST/TT auth) and sweeps EVERY project a user can access under one domain in a single run.
user-invocable	true

GoodData assessment

Read-only migration-readiness readout for a GoodData Cloud / .CN estate. Pulls the declarative layout (no writes) and scores it against what gooddata-to-sigma can actually convert.

Status: working + live-validated. scripts/assess.py reuses the converter's own MAQL translator for honest coverage scoring (no guessing) and tags each dashboard AUTO / HINT / MANUAL / UNHANDLED.

What it reports

Inventory — workspaces, datasets, metrics, insights, dashboards.
MAQL complexity — histogram of metrics by construct (plain agg / WHERE / BY-WITHIN-BY ALL context / FOR time transforms / ranking), since context + time intel are the conversion-risk drivers (maql-mapping.md).
Visualization mix — insight visualizationUrl histogram, with each type tagged against viz-type-mapping.md (auto-mappable vs flagged).
Per-dashboard tag — AUTO (fully mappable), HINT (minor manual), MANUAL (context MAQL / RLS review), UNHANDLED (exotic widgets / compute-only metrics).
Shortlist — value/cost-ranked migration order.

Usage

GoodData Cloud / .CN (Bearer API token, /api/v1):

eval "$(../gooddata-to-sigma/scripts/get-token.sh)"
python3 scripts/assess.py --workspace <id>     # or --all (all workspaces in ONE org)

Legacy GoodData Platform (classic /gdc, SST/TT auth) — different product, detected by a help.gooddata.com/doc/enterprise / /gdc/... footprint rather than <org>.cloud.gooddata.com:

export GOODDATA_PLATFORM_HOST=https://acme.on.gooddata.com
export GOODDATA_PLATFORM_USER=...  GOODDATA_PLATFORM_PASSWORD=...
python3 scripts/assess_platform.py --all       # EVERY project the user can access — one identity, one sweep
python3 scripts/assess_platform.py --project <pid>

Multi-"instance" note. On the Platform, "separate instances" are projects under one domain, so --all sweeps them all from a single login — this is the answer to "can one API pull across instances?" On Cloud, each org is a separate host+token; there you re-point GOODDATA_HOST/GOODDATA_TOKEN and re-run assess.py --all per org, then merge. Platform scoring reuses the same MAQL translator as Cloud (classic refs are normalized first). See ../gooddata-to-sigma/refs/gooddata-platform-api.md.

Usage telemetry (per-dashboard view counts) is the universal weak spot — it is not in the declarative model; note it as a manual input if needed.

Más de este repositorio

mismo repositorio

domo-to-sigma

twells89/sigma-migration-skills

Convert a Domo dashboard (pages + cards + DataSets + Beast Modes) into a Sigma data model and matching workbook. Use when the user has a Domo instance and wants to recreate a dashboard in Sigma. Discovery via Domo's public + private APIs, Beast Mode (MySQL-dialect SQL) → Sigma formula translation, a reuse check before building a new data model, data model + workbook creation via the Sigma REST API, layout generation, Domo PDP → Sigma row-level-security detection, and parity verification against the same warehouse — driven by `scripts/*.rb`.

2026-07-319

hex-to-sigma

twells89/sigma-migration-skills

Convert a Hex project (SQL cells, single-value/METRIC cells, EXPLORE charts, app layout) into a Sigma data model and matching workbook. Discovery via a Hex project export file (Hex's REST API does not expose cell content), calc translation, DM + workbook creation via REST, layout, and warehouse parity verification.

2026-07-319

looker-to-sigma

twells89/sigma-migration-skills

Convert a Looker instance (LookML semantic model + dashboards) into a Sigma data model and matching workbook(s). Use when the user has Looker content — LookML projects, explores, or dashboards (user-defined OR LookML-defined) — and wants to recreate it in Sigma. Discovery via the Looker REST API 4.0 / Looker MCP server (or LookML files offline), model conversion via the local vendored LookML converter (convert_lookml_to_sigma MCP tool as a manual fallback), dashboard → workbook conversion from the Looker Dashboard API JSON, build via the Sigma REST API, and 3-way parity verification against the source warehouse — driven by `scripts/*`.

2026-07-319

powerbi-to-sigma

twells89/sigma-migration-skills

Convert a Power BI report + semantic model into a Sigma data model and matching dashboard. Use when the user has a Power BI report (in Power BI Service / Fabric, or a .pbix/.pbit file) and wants to recreate it in Sigma. Covers connecting to Power BI with no Entra app, extracting the model (TMSL) + report layout (PBIR/Report-Layout), converting via the sigma-data-model MCP, posting the data model + workbook via REST, and parity verification. Can also author dashboards back INTO Power BI via the Fabric write API.

2026-07-319

qlik-to-sigma

twells89/sigma-migration-skills

Convert a Qlik Sense / Qlik Cloud app into a Sigma data model and matching workbook. Use when the user has a Qlik Cloud tenant/app and wants to recreate it in Sigma. Discovery via qlik-cli (Engine + REST), Qlik-expression → Sigma-formula translation via the local vendored convert_qlik_to_sigma converter (MCP tool only as a manual fallback), data model + workbook creation via the Sigma REST API, and parity verification against the source warehouse. Requires qlik-cli + a Sigma SIGMA_API_TOKEN.

2026-07-319

quicksight-to-sigma

twells89/sigma-migration-skills

Convert an Amazon QuickSight analysis or dashboard into a Sigma data model and matching dashboard. Use when the user has a QuickSight analysis/dashboard and wants to recreate it in Sigma. Covers AWS-CLI extraction of the analysis definition + datasets + data sources, calc-field / data-prep translation via the local vendored converter (the convert_quicksight_to_sigma MCP tool is a manual fallback only), posting the data model + workbook via the Sigma REST API, layout, and parity verification against the same warehouse.

2026-07-319

name	gooddata-assessment
description	Take inventory of a GoodData Cloud / GoodData.CN estate and produce a migration-readiness readout — workspace, dataset, metric, insight, and dashboard counts; a MAQL-complexity histogram (which metrics use BY / WITHIN / BY ALL / FOR time transforms); an insight visualization-type mix; and per- dashboard AUTO / HINT / MANUAL / UNHANDLED tags scored against the gooddata-to-sigma converter's actual coverage. Use when a user wants to scope a GoodData→Sigma migration, audit estate sprawl, or pick which dashboards to convert first. Read-only, all-free pre-scoping over the declarative workspace export. Also assesses the legacy GoodData Platform (classic /gdc, SST/TT auth) and sweeps EVERY project a user can access under one domain in a single run.
user-invocable	true

GoodData assessment

Read-only migration-readiness readout for a GoodData Cloud / .CN estate. Pulls the declarative layout (no writes) and scores it against what gooddata-to-sigma can actually convert.

Status: working + live-validated. scripts/assess.py reuses the converter's own MAQL translator for honest coverage scoring (no guessing) and tags each dashboard AUTO / HINT / MANUAL / UNHANDLED.

What it reports

Inventory — workspaces, datasets, metrics, insights, dashboards.
MAQL complexity — histogram of metrics by construct (plain agg / WHERE / BY-WITHIN-BY ALL context / FOR time transforms / ranking), since context + time intel are the conversion-risk drivers (maql-mapping.md).
Visualization mix — insight visualizationUrl histogram, with each type tagged against viz-type-mapping.md (auto-mappable vs flagged).
Per-dashboard tag — AUTO (fully mappable), HINT (minor manual), MANUAL (context MAQL / RLS review), UNHANDLED (exotic widgets / compute-only metrics).
Shortlist — value/cost-ranked migration order.

Usage

GoodData Cloud / .CN (Bearer API token, /api/v1):

eval "$(../gooddata-to-sigma/scripts/get-token.sh)"
python3 scripts/assess.py --workspace <id>     # or --all (all workspaces in ONE org)

Legacy GoodData Platform (classic /gdc, SST/TT auth) — different product, detected by a help.gooddata.com/doc/enterprise / /gdc/... footprint rather than <org>.cloud.gooddata.com:

export GOODDATA_PLATFORM_HOST=https://acme.on.gooddata.com
export GOODDATA_PLATFORM_USER=...  GOODDATA_PLATFORM_PASSWORD=...
python3 scripts/assess_platform.py --all       # EVERY project the user can access — one identity, one sweep
python3 scripts/assess_platform.py --project <pid>

Multi-"instance" note. On the Platform, "separate instances" are projects under one domain, so --all sweeps them all from a single login — this is the answer to "can one API pull across instances?" On Cloud, each org is a separate host+token; there you re-point GOODDATA_HOST/GOODDATA_TOKEN and re-run assess.py --all per org, then merge. Platform scoring reuses the same MAQL translator as Cloud (classic refs are normalized first). See ../gooddata-to-sigma/refs/gooddata-platform-api.md.

Usage telemetry (per-dashboard view counts) is the universal weak spot — it is not in the declarative model; note it as a manual input if needed.