pbip-validator — Claude Code subagent: validate Power BI projects
pbip-validator — a subagent that diagnoses structural errors, JSON schema violations, and TMDL syntax issues in Power BI projects. Runs when you need to verify project integrity before opening in Desktop or after renaming tables.
GPL-3.0 ★ 1,104 updated 2026-10-28
.github/agents/pbip-validator.agent.mdWhat pbip-validator does
pbip-validator automates Power BI Project (PBIP) validation. It runs deterministic tools in sequence: first checks project structure (root .pbip files, .platform identities, dataset reference resolution, theme resource files on disk), then delegates report validation to pbir validate for each .Report/ folder (JSON syntax, Microsoft schemas, visual and page naming rules, field references). For TMDL, the subagent validates syntax manually: table names matching filenames, proper indentation (tabs only), correct references in relationships and cultures. It also detects collisions between M-expression names and table names — a common silent blocker that causes Desktop to reject the project.
After a table rename, pbip-validator scans the entire project for remaining references to the old name across TMDL, JSON, DAX, and embedded selectors. Findings are reported with exact file paths and specific remediation steps.
What it helps with
- Find why a PBIP project won't open in Power BI Desktop
- Verify project integrity after renaming a table or column
- Check TMDL syntax in the semantic model
- Validate JSON in visuals against the PBIR schema
- Locate missing theme resource files
Example prompts for the agent
- Validate my PBIP project for errors
- Did the table rename cascade through all references?
- Check this Report folder — it won't open in Desktop
How to install pbip-validator
Manually: put the files in place
.github/agents/pbip-validator.agent.md1Plugin marketplace
/plugin marketplace add data-goblin/power-bi-agentic-development/plugin install pbip@power-bi-agentic-development2Manually: put the files in place
.claude/agents/pbip-validator.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention. Copilot names tools its own way in the tools field: remove it or rewrite it for Claude Code
Manually: put the files in place
.codex/agents/pbip-validator.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/pbip-validator.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about pbip-validator
How do I install pbip-validator in Claude Code?
Run these commands in order: /plugin marketplace add data-goblin/power-bi-agentic-development, then /plugin install pbip@power-bi-agentic-development. The subagent will then be available in Claude Code.
What does pbip-validator do?
It checks PBIP structure (files, folders, JSON validity), validates TMDL syntax in your semantic model, finds schema violations in visuals, and scans for dangling references after renames. It prioritizes deterministic validators to catch errors reliably.
When should I use pbip-validator?
Use it when a PBIP fails to open in Desktop with an unclear error, after renaming tables to verify all references updated, or before committing to catch TMDL and JSON syntax errors early.