What problem does it solve? Power BI Project files decompose reports and semantic models into many interlinked text files, and operations like renaming a table or forking a project silently break references scattered across TMDL, visual JSON, bookmarks, and DAX query files. This Skill provides the structural knowledge and validation tooling to navigate, convert, and safely modify PBIP projects without corrupting them. ## Core Features & Use Cases - Project Structure Guidance: Explains every PBIP file type (.pbip, .pbir, .pbism, .platform, .pbi/ runtime state), thick vs thin reports, and PBIX vs PBIP trade-offs. - PBIX Extraction and Conversion: Extracts PBIX ZIP archives with correct per-file encoding handling and assembles a PBIP from an extracted thin PBIX. - Rename Cascade Reference: Documents every location that must be updated when renaming tables, measures, or columns, including sparkline metadata, bookmark filters, and culture files. - Automated Validation: Ships a validate_pbip.py script that checks .platform identity, datasetReference resolution, orphan page folders, page-name regex rules, and theme resource resolution, delegating deep report checks to pbir validate. - Use Case: After renaming a table from Customers to Customer, run the validator and the provided grep patterns to confirm no stale references remain in visual JSONs, filters, or DAX queries before reopening Power BI Desktop. ## Quick Start Ask the agent to validate your PBIP project folder and explain its structure, for example by requesting a check of all cross-file references after renaming a table in your Power BI project.
