dashboard-designlisted

Design a Power BI dashboard FROM approved metric contracts in the Seshat BI repo. Use when someone asks to design a report/page, bind visuals to metrics, or produce a dashboard layout for a subject area whose semantic model is ready. This skill is HARD-GATED on semantic_model_ready: pass (no approved metric contracts -> no design); it authors reviewable design guidance only -- a layout plan, a visual list, and a visual->contract binding map where every visual binds to exactly one approved contract. It NEVER invents a metric, NEVER publishes, NEVER opens Power BI Desktop or a DB connection, and NEVER calls the Power BI execution adapter (official Power BI MCP / connection; `pbi-cli` no longer preferred) -- that is feature F016. It authors, runs static seshat check, records dashboard_ready at most as warning, and STOPS.
Kemetra/Seshat-BI · ★ 2 · Web & Frontend · score 68

Install: claude install-skill Kemetra/Seshat-BI

# dashboard-design Stage 6 of the Tower BI Readiness System, **Dashboard Ready** ([`docs/readiness/dashboard-ready.md`](../../../docs/readiness/dashboard-ready.md)): a report is designed AGAINST approved metric contracts -- never before them. This skill is the agent VERB that runs that stage. It reads the approved metric contracts (F009) and the governed PBIP model (F010), then authors a layout plan, a visual list, and a visual->contract binding map so every visual traces to a contract that already exists and is approved. It is the agent expression of roadmap hard rule 5 ("no dashboard design before metric contracts") and hard rule 6 ("no Power BI execution before semantic-model readiness"). This verb is the gated, contract-binding design step that the broader `powerbi-dashboard-design` router (F011A, the visual-design FOUNDATION) hands the "design a dashboard from approved contracts" intent to. The router carries the design vocabulary (four surfaces, tokens, theme, blueprints, QA); this verb enforces the gate and produces the binding map a human signs off. ## Scope boundary (read first) This skill AUTHORS design guidance and STOPS. Authoring is in-scope: a layout plan, a visual list, a visual->contract binding map, and (optionally) a blank PBIR scaffold a human fills -- no side effects, no DB/Desktop connection, the same category as `source-mapping` authoring `mappings/` and `retail-build-warehouse` authoring `warehouse/migrations/*.sql`. EXECUTING the design -- generati