# Pbip

> Work safely with Power BI Project files: PBIP, PBIR report folders, TMDL semantic model folders, .platform identity files, and .pbi local state. Use whenever editing Power BI project files.

- Skill: `onlinesourdough/pbip` (Agent Skill)
- Install (CLI): `npx skillmds@latest add onlinesourdough/pbip`
- Raw SKILL.md: https://api.skillmd.com/api/skills/onlinesourdough/pbip/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: onlinesourdough (https://skillmd.com/u/onlinesourdough)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/onlinesourdough/pbip

---


# PBIP / PBIR / TMDL Workflow

PBIP makes Power BI source-control friendly by saving report and model metadata as text files.

## Structure

```text
Project/
├── Report.pbip
├── Report.Report/
│   ├── definition.pbir
│   └── definition/
└── Report.SemanticModel/
    ├── definition.pbism
    └── definition/
```

## Rules

- `.Report/definition.pbir` binds the report to a semantic model.
- `.Report/definition/` contains PBIR report JSON.
- `.SemanticModel/definition/` contains TMDL model files.
- `.pbi/` contains local cache/settings and should normally not be committed.
- `.platform` contains Fabric identity. Do not invent or casually rewrite it.

## Safe edit workflow

Inspect the target structure and binding. Prefer `pbir` for report edits and
Tabular Editor/TOM for model edits when available; direct text edits remain
valid when their structure and references can be checked. Validate affected
PBIP/PBIR/TMDL files with the `validation` skill; missing native tools are
reported as unavailable, not required installations.

```bash
node workspace/engine/validate-pbip.mjs .
pbir validate "Report.Report" --all
```

## Data and semantic-model change boundary

Before changing a source query, schema mapping, relationship, model property,
or security-relevant semantic behavior, follow the
[shared data-change boundary](../../../docs/contract.md#data-change-boundary).
For PBIP, the owning migration mechanism is normally Power Query or model
metadata; do not create a SQL migration or directory unless the approved target
is actually SQL. Source and default fixture evidence is synthetic or reduced.
Never include credentials, private tenant or connection details, or production
extracts outside their exact approved operational scope; retain necessary
nonsecret model and connection metadata. Local source-edit authority does not
authorize source-data, RLS, refresh, access, identity, or service mutation.

## Rename checklist

When renaming tables, columns, measures, pages, or visuals, search across:

- TMDL table files
- relationships
- PBIR visual JSON
- filters and sort definitions
- report metadata / visual calculations
- DAX query files
- diagram layouts

Complete rename cascades within the exact authorized local scope, including
their affected references. Ask only if the cascade expands that scope. Local
rename authority does not cover report rebinding, `.platform` identity, RLS,
service, publish, or access/refresh changes; require explicit authority for those.