pbip - SKILL.md Agent Skill

name: pbip description: Use when working with Power BI Project files, PBIP structure, PBIR report JSON, TMDL semantic model files, definition.pbir bindings, report folders, model folders, or validation after Power BI file edits. license: Personal use argument-hint: "[pbip-task] [path]" metadata: author: data-visualization-kit version: "1.0.0" source_inspiration: "data-goblin/power-bi-agentic-development@67627c270241f282ad98754194ad58212b0fa886"

PBIP Skill

PBIP is the source-control-friendly Power BI project format. Use this skill to reason about file layout, direct file changes, rename cascades, bindings, and validation.

When To Use

The project contains .pbip, .Report, .SemanticModel, .Dataset, .tmdl, definition.pbir, visual.json, page.json, or report.json.
The user asks to validate a Power BI project or diagnose a report that will not open.
The user asks to rename a table, measure, column, page, visual, report, or model.
The user asks about thick vs thin reports, by-path vs by-connection binding, or PBIP/PBIX conversion.

Core Concepts

.Report/ contains PBIR report metadata.
.SemanticModel/ or .Dataset/ contains model metadata, often TMDL.
definition.pbir tells a report which semantic model it binds to.
A thick project usually has report and semantic model folders together.
A thin report usually binds to a remote semantic model.

Direct Edit Rules

Prefer official tools or pbir CLI when available.
If editing JSON directly, parse it before and after changes.
Do not add comments to PBIR JSON.
Keep file names and object names stable unless the user asked for a rename.
For renames, search across report JSON, TMDL, DAX queries, culture files, and report extensions.
After edits, run scripts/hooks/power-bi-output-gate.cjs or equivalent validation before publishing.

Validation Focus

JSON syntax for PBIR files.
Required PBIR files and fields for touched report objects.
Folder names without problematic spaces for new human-authored pages or visuals.
definition.pbir binding shape and local by-path targets.
TMDL syntax via available tools when present.
No Power BI files written outside the intended project workspace.

Output Notes

Record validation status in:

projects/<slug>/docs/visualization.md
projects/<slug>/docs/publish.md

Store exports or screenshots in:

projects/<slug>/docs/assets/exports/
projects/<slug>/docs/assets/screenshots/

Escalation

Ask the user before:

Converting PBIX to PBIP.
Publishing to Fabric or Power BI Service.
Editing a shared semantic model.
Renaming model objects that can break downstream reports.
Storing or using tenant/workspace credentials.