What problem does it solve? Hand-editing Power BI Enhanced Report (PBIR) JSON files is brittle: schema-valid edits can still break rendering, corrupt reports, or silently do nothing. This Skill provides the format reference, validation rules, and failure patterns needed to safely read, create, and modify PBIR report metadata. ## Core Features & Use Cases - PBIR structure and schema guidance: Covers report.json, page.json, visual.json, themes, filters, bookmarks, extension measures, and definition.pbir connection modes (byPath vs byConnection). - Failure diagnosis: Documents symptoms of broken hand-authored PBIR, such as UTF-8 BOM corruption, empty visuals, Missing_References after publishing, and formatting changes that do nothing. - Legacy conversion script: Includes a Python script that converts monolithic legacy report.json into the PBIR directory structure with per-page and per-visual files. - Use Case: A developer needs to add a conditional formatting rule and a new slicer to a thin report connected to a remote semantic model. The Skill directs them to the correct visual.json and theme references, warns about the no-BOM rule, and explains how to validate the result. ## Quick Start Ask the agent to add a conditional formatting rule to the revenue column of the table visual in your PBIR report and validate the change.
