Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →data-goblin/pbip
Guidance for Power BI Project (PBIP) structure, thick and thin reports, project renames, forks, and validation.
Passed 18 of 22 test cases with the skill, and 11 of 22 without it.
and 10 more in the full report
7 fixed11 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/20/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Running pbir validate against a local PBIP project returns SCHEMA_UNSUPPORTED because localSettings.json uses a newer schema version. Which CLI flag resolves this issue?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends passing --allow-download-schemas to pbir validate | Missed | Passed |
The instructions your model reads when the skill loads.
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.
te for the semantic model and
pbir for every report mutation. Never hand-edit PBIR JSON..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..Report/ and .SemanticModel/ folders can coexist. The .pbip file is optional -- open definition.pbir directly.core.autocrlf or * text=auto in .gitattributes to normalize.pbir desktop refresh for supported report/model changes;
close and reopen Desktop for theme changes.te mv --save, then update each
report with pbir fields replace or replace-table and validate both sides.SourceRef.Entity JSON structure. Easy to miss.<Name>.SemanticModel/DAXQueries/ and <Name>.Report/DAXQueries/. Always check both during renames.Treat PBIX as an opaque Desktop artifact. Do not unzip it, patch its internals, reconstruct PBIR from its contents, or invoke an unapproved extraction engine. Microsoft licensing/EULA questions around third-party engine redistribution are unresolved for this project.
Use Power BI Desktop File > Save As > Power BI Project (.pbip), then work on the resulting
.Report folder with pbir and on the semantic model with te. If Desktop conversion is not
available, stop and ask for a PBIP/PBIR source artifact rather than inventing a conversion path.
| Aspect | PBIX | PBIP |
|---|---|---|
| Format | Single binary file | Folder of text files |
| Source control | Not diff-friendly | Git-ready, human-readable diffs |
| Collaboration | Single author at a time | Multiple authors, merge-friendly |
| External editing | Not supported | VS Code, Tabular Editor, scripts |
| Deployment | File > Publish | Git integration, Fabric APIs, fabric-cicd |
| Data | Contains cached data | cache.abf is gitignored; metadata only in Git |
test cases passed, vs 11 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.