What problem does it solve?
Power BI Project (PBIP) folders contain many interdependent files (.pbip, .pbir, .pbism, .platform, TMDL, PBIR JSON) where renames, forks, or manual edits silently break references, orphan pages, or cause Power BI Desktop to ignore content without errors. This Skill provides the structural knowledge and validation tooling to keep PBIP projects consistent.
Core Features & Use Cases
- Project Structure Guidance: Explains thick vs thin reports, byPath vs byConnection dataset references, page folder naming rules, and SharedResources path resolution.
- Automated Validation: The validate_pbip.py script checks .platform identity, TMDL vs TMSL format conflicts, orphan page folders, invalid page names, missing theme resources, and M expression/table name collisions, delegating deep report checks to pbir validate.
- Rename & Fork Workflows: Detailed cascade references show every location (visual JSON, bookmarks, filters, DAX queries, culture files) that must update when renaming tables, measures, or columns, plus step-by-step project forking.
- Use Case: After renaming a table from Customers to Customer, run the validator and grep checks to confirm no stale Entity references remain in sparkline metadata, conditional formatting, or bookmark filters.
Quick Start
Ask the agent to validate my PBIP project at the current folder and report any broken references or structural errors.