pbip-workflow
Skill2 starsChanged 4 months agoApache-2.0View on GitHub
The git-based workflow for Power BI Project (PBIP) files — saving reports as plain-text TMDL/PBIR, what to commit vs ignore, and the Windows gotchas. Use this whenever someone is putting Power BI under version control: saving a report to git, choosing PBIP vs .pbix, editing TMDL or DAX as text, reviewing a semantic-model change in a PR, or troubleshooting why a .pbi folder, cache, or localSettings is (or isn't) showing up in git. Also use when "Save as PBIP" is missing, when PBIP diffs look noisy (line endings / encoding), or when path-too-long errors appear saving a Power BI project on Windows.
In this repository60 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- approval-consoleSkill
- approval-evidence-packSkill
- business-knowledge-interviewSkill
- capabilitiesSkill
- consumer-data-dictionarySkill
- cross-table-lineageSkill
- dagster-orchestration-adapterSkill
- dashboard-designSkill
- dashboard-intelligenceSkill
- dbt-transformation-adapterSkill
- evidence-pack-generatorSkill
- first-hour-compassSkill
- friendly-pr-reviewerSkill
- grain-confidence-reviewerSkill
- kpi-contract-builderSkill
- pbi-mcp-write-adapterSkill
- pbip-xraySkill
- pbir-authoring-adapterSkill
- portfolio-watchSkill
- powerbi-dashboard-designSkill
- pr-readiness-reviewerSkill
- readiness-viewerSkill
- release-notes-generatorSkill
- report-intent-interviewSkill
- retail-build-warehouseSkill
- retail-control-roomSkill
- retail-discover-portfolioSkill
- retail-governSkill
- retail-initSkill
- retail-onboard-tableSkill
- retail-orchestrateSkill
- retail-scaffoldSkill
- retail-semantic-checkSkill
- retail-validateSkill
- run-next-readinessSkill
- seshat-studioSkill
- showcase-buildSkill
- source-mappingSkill
- speckit-analyzeSkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-git-commitSkill
- speckit-git-featureSkill
- speckit-git-initializeSkill
- speckit-git-remoteSkill
- speckit-git-validateSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- bi-analyst-knowledgeSkill
- bi-bigdata-knowledgeSkill
- bi-dax-knowledgeSkill
- bi-python-knowledgeSkill
- bi-sql-knowledgeSkill
- retail-kpi-knowledgeSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 4 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 41
When the analyst already has a PBIP project, start with the governed, read-only intake rather than treating its report pages or measures as …
- Distinctive: line 70
If "Save as Power BI Project" is missing, it's because the preview feature isn't on:
- Distinctive: line 73
Check Power BI Project (.pbip) save option.
- Distinctive: line 116
Verify behavior rather than trusting the file is right:
- Very specific: line 155
When a table is being driven end-to-end, the retail-orchestrate conductor skill sequences this verb with the others and runs the self-heal …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
PBIP Workflow
Power BI's default .pbix is a binary zip — opaque to git, impossible to diff or
merge, and it bloats history. The Power BI Project (PBIP) format saves the
same work as folders of plain text, so your semantic model and report become
reviewable code. This skill owns Seshat's PBIP version-control and adoption
delta. It is not a native report or semantic-model authoring implementation:
when execution is authorized and discoverable, route report mechanics to
Microsoft's official powerbi-report-authoring skill and semantic-model
mechanics to Microsoft's authoring/Modeling MCP surfaces through
powerbi-workflows.
PBIP is a preview feature (per Microsoft docs as of 2025-12). It can change. Verify specifics against the current docs: https://learn.microsoft.com/power-bi/developer/projects/projects-overview
When this matters
The whole reason to use PBIP is that the semantic model becomes code. Tables,
relationships, and especially DAX measures are saved as TMDL (Tabular Model
Definition Language) text — so "who changed the Gross Margin measure and why" is
answerable from git log, and a teammate can review a measure change in a pull
request the same way they'd review a function. Treat the model with the same care
as source code.
Adopt an existing PBIP into Seshat BI
When the analyst already has a PBIP project, start with the governed, read-only intake rather than treating its report pages or measures as readiness evidence:
seshat adopt-pbip assess --project <PBIP-project-directory> --format textThe assessment inventories only supported PBIP/TMDL/PBIR structure, redacts unsafe literals, reuses existing governance/readiness findings, and returns one next action. It does not create a source map, metric contract, approval, or readiness pass. Review the digest and declared write plan before any mutation.
For a clean, existing Git worktree only, an analyst may explicitly accept the current assessment to create exactly one new evidence seam:
seshat adopt-pbip scaffold --project <PBIP-project-directory> `
--accept-assessment <assessment-digest> --format textThis creates only .seshat/adoption/pbip-adoption.yaml; it never initializes
Git, overwrites a file, or edits PBIP/TMDL/PBIR/DAX/SQL/source artifacts.
Approvals remain empty and readiness must still be proven through the existing
seven-stage gates. For a .pbix, open it in Power BI Desktop and save it as a
PBIP first; the adoption command does not parse or extract PBIX binaries.
Enabling PBIP
If "Save as Power BI Project" is missing, it's because the preview feature isn't on:
- Power BI Desktop → File > Options and settings > Options > Preview features.
- Check Power BI Project (.pbip) save option.
- Save via File > Save as > Power BI Project (.pbip).
A .pbix can be saved as PBIP and back again (via Desktop's Save As), so migrating
an existing report is low-risk.
What a PBIP looks like
Project/
├── MyReport.Report/
│ └── definition/ ← report visuals/layout (PBIR)
│ └── ...
├── MyReport.SemanticModel/
│ └── definition/ ← TMDL: tables, relationships, MEASURES (your DAX)
│ └── ...
├── MyReport.pbip ← pointer file that opens the report+model
└── .gitignoreThe definition/ folders are the valuable part — that's the model and report as
code. The .pbip file is just a shortcut to open them.
Commit vs. ignore — the part that bites people
This is the highest-risk decision. Get it backwards and you either leak local workspace context into git or — worse — drop the actual model definition from version control.
Commit these (this is your reviewable source):
- Everything under
*.SemanticModel/definition/(TMDL — tables, relationships, DAX) - Everything under
*.Report/definition/, plusdefinition.pbir .platform- The
*.pbipfile
Ignore these — Microsoft's official PBIP .gitignore baseline is exactly:
**/.pbi/localSettings.json
**/.pbi/cache.abflocalSettings.jsonholds local workspace settings and can carry connection context.cache.abfis the local data cache — large, machine-specific, not source.
Verify behavior rather than trusting the file is right:
# should print the path (ignored):
git check-ignore "MyReport.SemanticModel/.pbi/cache.abf"
# should print NOTHING (tracked) — if it prints, your model is being dropped from git:
git check-ignore "MyReport.SemanticModel/definition/model.tmdl"Windows & diff gotchas
These come straight from Microsoft's docs and quietly break teams:
| Gotcha | Why | What to do |
| 260-char path limit | PBIP nests folders + files; long table/object names overflow it and saves fail | Keep the repo at a short root path; keep project/table names short |
| CRLF line endings | Power BI Desktop writes CRLF; mixed endings make diffs noisy | git config core.autocrlf true and commit a .gitattributes |
| UTF-8 without BOM | Editing TMDL/JSON externally with a BOM can corrupt the file | Save external edits as UTF-8 without BOM |
| Desktop is unaware of external edits | It serves its in-memory session and restores cached view state from .pbi/localSettings.json — a plain restart or a Recent-list reopen can still show the OLD layout | Follow the full reload protocol in the powerbi-workflows skill: quit Desktop (verify PBIDesktop.exe AND msmdsrv.exe are gone), move .pbi/localSettings.json aside for both .Report and .SemanticModel, reopen via File Explorer (not Recent), choose Don't Save on the stale-session prompt |
Editing the model as text
PBIP makes TMDL reviewable in VS Code and other text tools, but reviewability is not authority to bypass the execution gate. Route native semantic-model edits to the official Microsoft surface when F016 policy permits it, and route native PBIR report edits to the official report-authoring skill after dashboard readiness. Seshat's local PBIR helpers remain valid only for their explicit allow-listed, binding-preserving subset. Undocumented Desktop-owned files can still make a project unloadable when changed externally.
Reviewing a PBIP change in a PR
Because measures are TMDL text, review them like code:
- Does the measure use
DIVIDE()for ratios (not/) so zero/blank denominators are safe? - Is logic duplicated across measures that should share a base measure?
- Did a relationship flip to bidirectional (a common source of wrong totals)?
- Is any connection string or secret accidentally committed instead of parameterized?
Orchestration
When a table is being driven end-to-end, the retail-orchestrate conductor skill
sequences this verb with the others and runs the self-heal loop against the gate
exit code. This skill stays single-purpose: it does its job and STOPS. The loop
(run gate -> classify findings -> auto-fix mechanical / HARD-STOP judgment calls ->
re-run) lives ONLY in retail-orchestrate, never here.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

