pbip
Guidance for Power BI Project (PBIP) structure, thick and thin reports, project renames, forks, and validation. Use for .pbip, .pbism, .platform, definition.pbir, PBIP vs PBIX, or cross-cutting project operations.
npx skills add data-goblin/power-bi-agentic-development --skill pbip --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# PBIP Project Format PBIP (Power BI Project) is the developer-mode file format for Power BI. It decomposes a `.pbix` binary into human-readable text files organized in folders, enabling source control, external editing, and multi-author collaboration. ## General, critical guidance - **This skill covers project structure, not report editing.** Use `te` for the semantic model and `pbir` for every report mutation. Never hand-edit PBIR JSON. - **PBIX is a black box; PBIP is transparent.** PBIX is a single binary that cannot be diffed or edited externally. PBIP splits the same content into text files. Convert between them with File > Save As in PBI Desktop. - **Thick vs thin reports:** A thick report bundles `.Report/` + `.SemanticModel/` in the same project (`definition.pbir` uses `byPath`). A thin report has `.Report/` only, connecting to a remote model via `byConnection`. Thin reports are preferred for managed/shared BI. - **A project can contain multiple items.** Multiple `.Report/` and `.SemanticModel/` folders can coexist. The `.pbip` file is optional -- open `definition.pbir` directly. - **UTF-8 without BOM.** All files must be saved as UTF-8 without BOM. A BOM prefix causes par
- General, critical guidance
- Working with PBIX Files
- PBIX vs PBIP
- Project Structure
- Page folder naming
- SharedResources path resolution
- What to Read for Common Tasks
- Forking a PBIP Project
- Verification
- Related Skills
- References
python3 scripts/validate_pbip.py <path-to-.pbip-or-project> # validate python3 scripts/validate_pbip.py <path> --fix # scaffold .gitignore python3 scripts/validate_pbip.py <path> --json # machine-readable python3 scripts/validate_pbip.py <path> --no-pbir-cli # skip delegation Search for old name across all project files grep -r "Old Name" "Project.Report/" "Project.SemanticModel/" --include="*.json" --include="*.tmdl" --include="*.dax" Search with word boundaries to avoid partial matches grep -rP "\bOld Name\b" "Project.Report/" "Project.SemanticModel/" Look for old name in single-quoted DAX references grep -r "'Old Name'" --include="*.tmdl" --include="*.dax"
What does the pbip skill do?
Guidance for Power BI Project (PBIP) structure, thick and thin reports, project renames, forks, and validation. Use for .pbip, .pbism, .platform, definition.pbir, PBIP vs PBIX, or cross-cutting project operations.
How do I install it?
Run `npx skills add data-goblin/power-bi-agentic-development --skill pbip --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From data-goblin/power-bi-agentic-development, a repository with 833 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.