← ClaudeAtlas

pbir-authoring-adapterlisted

The Power BI report-AUTHORING adapter (F034 completion). Use when someone asks to apply a generated theme to a committed PBIR report, or (later increments) to set visual formatting or a page background by writing the report's PBIR JSON directly -- the settings a human sets by hand in the Power BI UI. This is a COMPANION execution/authoring adapter (the F029-dbt / F030-Dagster pattern), NOT part of the static DEFINE/CHECK core. It writes committed PBIR JSON within a tight allow-list, deterministically and validated; it uses NO pbi-cli, NO live Power BI, NO external dependency, and NO network. It grants no readiness pass and emits no score.
Kemetra/Seshat-BI · ★ 2 · API & Backend · score 68
Install: claude install-skill Kemetra/Seshat-BI
# pbir-authoring-adapter The adapter that completes F034: it writes the committed PBIR report the kit previously left for a human to build in Power BI Desktop. Authorized by **ADR 0015** (owner-ratified 2026-07-05), which lifts spec-001 FR-008/FR-009 *for this bounded adapter only* -- the static core stays forbidden from writing PBIR. ## What it is (and is NOT) - It **is** a companion authoring adapter: reads a generated theme (Slice 1 `retail theme-gen`) + committed PBIR, WRITES committed PBIR JSON within an allow-list, and validates every write. - It is **NOT** the brain: it defines no metric, mapping, or semantic logic; it writes formatting/wiring, never business meaning. - It is **NOT** publish-capable: it stops at the committed on-disk PBIR. Publishing to a live workspace is the parked F016 adapter (separate, gated). - It does **NOT** build a dashboard from nothing: it restyles/positions visuals a human authored. "Great professional dashboards" is a design-intelligence layer that would ride on top -- this adapter is the mechanism, not that layer. ## The boundary (carry into every increment) 1. **Allow-list only.** Write ONLY the declared formatting/wiring properties (see `templates/pbir-adapter-contract.md`). Increment A's allow-list: the report's `themeCollection.baseTheme` + its `resourcePackages` item + the BaseTheme resource file. Nothing else -- no `visual.json`, no `page.json` geometry, no semantic-model file. 2. **No external dependenc