pbi-desktop
NewConnect to Power BI Desktop's local Analysis Services instance to enumerate models, query with DAX, refresh data, and modify metadata via TOM. No MCP server required.
Summary
This skill enables Claude Code to connect directly to Power BI Desktop's local Analysis Services instance, allowing you to enumerate models, execute DAX queries, refresh data, and modify metadata via TOM without needing an MCP server.
- It streamlines Power BI development by integrating semantic model management into your AI-assisted workflow.
Overview
<p align="center"> <img src="media/bg42-11-4.png" alt="" width="800"> </p>
<h1 align="center">power-bi-agentic-development</h1>
<p align="center"> The best source for Power BI AI skills and agentic development resources in one marketplace <br></br> <i> Teach AI agents like Claude Code or GitHub Copilot Power BI and Microsoft Fabric </i> </p>
<p align="center"> <img src="https://img.shields.io/badge/version-26.24.10-blue" alt="Version"> <img src="https://img.shields.io/badge/Power_BI-F2C811?logo=powerbi&logoColor=000" alt="Power BI"> <img src="https://img.shields.io/badge/Microsoft_Fabric-008272" alt="Microsoft Fabric"> <img src="https://img.shields.io/badge/Tabular_Editor-2E7D32" alt="Tabular Editor"> <img src="https://img.shields.io/badge/license-GPL--3.0-green" alt="License"> </p>
[!WARNING]
Under active development with a weekly release cadence; regular renaming or restructuring.
What is agentic development?
- •Agentic development is when you use agents to help you build, manage, and optimize artifacts and software. This includes semantic models, reports, and the things around them, like workspaces, deployment pipelines, and also processes.
- •A marketplace hosts plugins that you can install. Plugins are a collection of resources that help coding agents perform better. They are typically special instruction files and scripts. Plugins can contain skills, subagents, hooks, and MCP servers focused on special topics or tasks.
- •This marketplace is focused on everything to help your agent work well with Power BI and Fabric: Power BI skills, Fabric skills, subagents, and hooks for coding agents. Read further for more information.
Installation
Here's how you get started in Claude Code; run this in the terminal to get the marketplace:
claude plugin marketplace add data-goblin/power-bi-agentic-developmentExample: Using the pbir-cli with the skills
Click here for a YouTube walkthrough

Claude Code
Add the marketplace, then install plugins via /plugin and navigating to the installed marketplace.
<table> <tr> <td align="center"><img src="media/marketplace-ui.png" alt="Marketplace UI" width="400"></td> <td align="center"><img src="media/marketplace-auto-update.png" alt="Marketplace auto-update" width="400"></td> </tr> <tr> <td align="center"><em>Install plugins from the marketplace</em></td> <td align="center"><em>Enable marketplace auto-update</em></td> </tr> </table>
Alternative; add plugins via command line:
claude plugin install tabular-editor@power-bi-agentic-development
claude plugin install pbi-desktop@power-bi-agentic-development
claude plugin install semantic-models@power-bi-agentic-development
claude plugin install reports@power-bi-agentic-development
claude plugin install pbip@power-bi-agentic-development
claude plugin install fabric-cli@power-bi-agentic-developmentCopilot CLI
The standalone Copilot CLI supports plugin installation from GitHub repos. Copilot CLI reads the same .claude-plugin/marketplace.json manifest this repo uses, so the marketplace and child-plugin layout works without modification.
<details> <summary><strong>Windows long paths</strong></summary>
TMDL files have a problem with repository-relative paths over 260 characters. Windows' legacy MAX_PATH blocks git clone from writing them unless long path support is enabled at both the OS and git level. Without this, copilot plugin install aborts with Filename too long.
Check `useful-stuff/agent-scripts/enable-windows-longpaths.ps1` as an example of a script you can run from an elevated ps environment to enable long paths; there are other routes to do this that you can find online, too... just ask Copilot. A reboot is recommended after the registry change. This is a Windows OS limitation, documented at Maximum Path Length Limitation.
See also the below git config command:
git config --system core.longpaths true</details>
<details> <summary><strong>Additional installation instructions</strong></summary>
This repository is an Anthropic-format plugin marketplace (a set of plugins), not a single distributable plugin, so the root .claude-plugin/ contains only marketplace.json. Two documented install paths work:
1. Register the marketplace once, then install named child plugins. Example:
copilot plugin marketplace add data-goblin/power-bi-agentic-development
copilot plugin install tabular-editor@power-bi-agentic-development2. Or install a single plugin directly from its subdirectory, no marketplace registration needed. Example:
copilot plugin install data-goblin/power-bi-agentic-development:plugins/pbipBoth forms are documented in the Copilot CLI plugin reference and the plugins how-to. Inside an interactive Copilot session, /plugin install PLUGIN-NAME@MARKETPLACE-NAME is the equivalent of (1). The bare copilot plugin install data-goblin/power-bi-agentic-development (no qualifier) will not install anything useful, because the root is a marketplace catalog, not a plugin.
</details>
<details> <summary><strong>Verify installation in Copilot CLI</strong></summary>
Inside Copilot CLI:
/env # Loaded instructions, MCP servers, skills, agents, plugins, LSPs, extensions
/plugin list # Installed plugins
/skills list # Available skills
/skills info pbip # Details for a specific skill
/agent # Browse installed agents</details>
<details> <summary><strong>Compatibility notes</strong></summary>
- •Skills load identically; Copilot CLI reads
skills/<name>/SKILL.md. - •Agents use the
*.agent.mdextension required by Copilot CLI's documented convention. Claude Code matches any*.mdfile inagents/, so the dual extension works in both tools. - •MCP servers load from
.mcp.json(plugin root) or.github/mcp.json. The plugins in this repo do not currently ship MCP servers. - •Hooks are registered via
hooks.jsonand reference scripts using${CLAUDE_PLUGIN_ROOT}. Copilot CLI ≥ 1.0.26 (2026-04-14) setsCLAUDE_PLUGIN_ROOTfor plugin hooks (changelog); older builds do not, which causes hook commands to resolve to broken paths. Runcopilot updateif hooks fail to fire. Native Windows bash users may also hit a separate path-format bug tracked upstream at claude-code#11984.
</details>
Overview
The repo contains skills, agents, and hooks.
- •Skills teach agents domain knowledge and workflows. They activate automatically based on task context, or can be invoked manually with
/skill-name. In Claude Code, skills and commands have coalesced; commands are simply more prescriptive skill workflows. - •Agents are autonomous subprocesses that handle complex, multi-step tasks independently; typically used for review and validation.
- •Hooks run automatically after tool use to validate files and catch errors early. They are deterministic; they fire when a specific pattern is matched, not by LLM judgment.
Hook checks can be individually toggled via config files. Set any check to false to disable it:
- •
plugins/pbip/hooks/config.yaml-- PBIR, TMDL, and report binding validation - •
plugins/pbi-desktop/hooks/config.yaml-- DAX references, measure metadata, referential integrity, metadata cache
Power BI and Fabric skills, agents, and hooks: available plugins
<details> <summary><img src="media/icons/tabular-editor.svg" alt="" height="20"> <strong>tabular-editor</strong>   BPA rules, C# scripting, and CLI automation for Tabular Editor</summary>
| Type | Name | Description |
|---|---|---|
| Skill | `bpa-rules` | Create and improve Best Practice Analyzer rules for models |
| Skill | `c-sharp-scripting` | C# scripting and macros for TE |
| Skill | `te-cli` | Cross-platform Tabular Editor CLI (te, preview) for semantic models from the terminal |
| Skill | `te2-cli` | Tabular Editor 2 CLI usage and automation (not TE3) |
| Skill | `te-docs` | Tabular Editor documentation search, TE3 config files. Uses `pbi-search` CLI |
| Command | `/suggest-rule` | Generate BPA rules from descriptions |
| Agent | `bpa-expression-helper` | Debug and improve BPA rule expressions |
</details>
<details> <summary><img src="media/icons/pbi-desktop.svg" alt="" height="20"> <strong>pbi-desktop</strong>   Connect to, query, and modify models in Power BI Desktop</summary>
| Type | Name | Description |
|---|---|---|
| Skill | `connect-pbid` | Explore, query, and modify a model in Power BI Desktop, and reload/screenshot the report canvas via the Desktop Bridge |
| Agent | `query-listener` | Capture DAX queries from Power BI Desktop visuals in real time |
| Hook | DAX reference validation | Validates table, column, and measure references against the connected model; suggests corrections |
| Hook | Measure metadata enforcement | Blocks adding measures without DisplayFolder, Description, and FormatString |
| Hook | Referential integrity check | Reports unmatched many-side keys after relationship or column changes |
| Hook | Metadata cache refresh | Auto-snapshots model metadata on TOM connect or model modification |
| Hook | Compatibility level check | Reports features available by upgrading; optional auto-upgrade |
</details>
<details> <summary><img src="media/icons/pbip.svg" alt="" height="20"> <strong>pbip</strong>   Author and validate TMDL, PBIR, and PBIP project files</summary>
| Type | Name | Description |
|---|---|---|
| Skill | `pbip` | Power BI Project (PBIP) format, structure, and file types |
| Skill | `tmdl` | Author and edit TMDL files directly |
| Skill | `pbir-format` | Author and edit PBIR metadata files directly (visual.json, report.json, themes, filters, report extensions, visual calculations) |
| Agent | `pbip-validator` | Validate PBIP project structure, TMDL syntax, and PBIR schemas |
| Hook | PBIR validation | Validates PBIR structure, required fields, naming conventions, and schema URLs |
| Hook | Report binding validation | Validates semantic model binding (byPath directory exists; byConnection model exists via fab exists) |
| Hook | TMDL validation | Validates TMDL structural syntax |
</details>
<details> <summary><img src="media/icons/reports.svg" alt="" height="20"> <strong>reports</strong>   Deneb, R, Python, SVG visuals; themes; report design and review</summary>
| Type | Name | Description |
|---|---|---|
| Skill | `pbi-report-design` (Very WIP) | Power BI report best practices, design and style |
| Skill | `modifying-theme-json` (WIP) | Working with theme files |
| Skill | `deneb-visuals` | Deneb visuals with Vega and Vega-Lite specs |
| Skill | `r-visuals` | Custom R visuals in Power BI reports |
| Skill | `python-visuals` | Custom Python visuals in Power BI reports |
| Skill | `svg-visuals` | SVG visuals via DAX measures in Power BI reports |
| Skill | `review-report` (WIP) | Review Power BI reports for usage metrics and best practices |
| Skill | `pbir-cli` | Programmatic report manipulation via the `pbir` CLI, including live Power BI Desktop refresh and page screenshots |
| Agent | `deneb-reviewer` | Review Deneb visual specs for Vega/Vega-Lite syntax and conventions |
| Agent | `svg-reviewer` | Review SVG DAX measures for syntax and design quality |
| Agent | `r-reviewer` | Review R visual scripts (ggplot2) for Power BI conventions |
| Agent | `python-reviewer` | Review Python visual scripts (matplotlib/seaborn) for Power BI conventions |
</details>
<details> <summary><img src="media/icons/semantic-models.svg" alt="" height="20"> <strong>semantic-models</strong>   DAX, Power Query, naming, lineage, refresh, and model auditing</summary>
| Type | Name | Description |
|---|---|---|
| Skill | `semantic-model` | Design, build, refresh, and review semantic models through a te-first tool cascade |
| Skill | `standardize-naming-conventions` | Audit and standardize naming conventions in semantic models |
| Skill | `refresh-semantic-model` | Trigger or troubleshoot refreshes |
| Skill | `lineage-analysis` | Trace downstream reports from a semantic model across workspaces |
| Skill | `power-query` | Write M expressions, debug query folding, execute M locally or via Fabric API |
| Skill | `dax` | Write, debug, and optimize DAX in semantic models. Contributed by Justin Martin |
| Agent | `semantic-model-auditor` | Audit semantic models for quality, memory, DAX, and design issues |
</details>
<details> <summary><img src="media/icons/fabric-cli.svg" alt="" height="20"> <strong>fabric-cli</strong>   Remote operations via Fabric CLI; works on Pro, PPU, or Fabric</summary>
| Type | Name | Description |
|---|---|---|
| Skill | `fabric-cli` | Fabric CLI (fab) for any remote operation in Power BI or Fabric (works fully on Pro, PPU; Fabric not required) |
| Command | `/audit-context` | Review project context files (CLAUDE.md, agents.md, memory files) |
| Command | `/migrating-fabric-trial-capacities` | Migrate workspaces from trial to production capacity |
</details>
<details> <summary><img src="media/icons/fabric-cli.svg" alt="" height="20"> <strong>fabric-admin</strong>   Tenant settings audits, governance, delegated overrides; requires fabric-cli</summary>
| Type | Name | Description |
|---|---|---|
| Skill | `audit-tenant-settings` | Audit Fabric and Power BI tenant settings, delegated overrides, and Entra security group membership |
</details>
Useful stuff
General-purpose agent resources that don't fit into a plugin: defensive hooks, patterns, and tools. See `useful-stuff/`.
Use or re-use of these skills
These plugins are intended for free community use.
You do not have the license to copy and incorporate them into your own products, trainings, courses, or tools. If you copy these skills - manually or by using an agent to rewrite them - you must include attribution and a link to this original project. That includes you, Microsoft.
<br>
<p align="center"> <img src="media/bg22-06-2.png" alt="" width="800"> </p>
<p align="center"> <em>Built with assistance from <a href="https://claude.ai/claude-code">Claude Code</a>. AI-generated code has been reviewed but may contain errors. Use at your own risk.</em> </p>
<p align="center"> <em>Context files are human-written and revised by Claude Code after iterative use.</em> </p>
<p align="center"> <a href="https://github.com/data-goblin">Kurt Buhler</a> · <a href="https://data-goblins.com">Data Goblins</a> · part of <a href="https://tabulareditor.com">Tabular Editor</a> </p>
Install & Usage
~/.claude.jsonAdd the configuration to "mcpServers": { "pbi-desktop": { "command": "...", "args": [] } }
/mcpUse Cases
Usage Examples
/pbi-desktop list models
/pbi-desktop query "EVALUATE SUMMARIZE(Sales, Product[Name], "Total Sales", SUM(Sales[Amount]))"
/pbi-desktop refresh model
Security Audits
Frequently Asked Questions
What is pbi-desktop?
This skill enables Claude Code to connect directly to Power BI Desktop's local Analysis Services instance, allowing you to enumerate models, execute DAX queries, refresh data, and modify metadata via TOM without needing an MCP server. It streamlines Power BI development by integrating semantic model management into your AI-assisted workflow.
How to install pbi-desktop?
To install pbi-desktop: open your mcp config (~/.claude.json), then add the config to "mcpServers": { "pbi-desktop": { "command": "...", "args": [] } }. Finally, /mcp in Claude Code.
What is pbi-desktop best for?
pbi-desktop is a mcp categorized under General. It is designed for: mcp. Created by Kurt Buhler.
What can I use pbi-desktop for?
pbi-desktop is useful for: Enumerate all tables and measures in a Power BI Desktop model to understand its structure.; Execute a DAX query to retrieve specific data from a Power BI Desktop model for analysis.; Refresh data in a Power BI Desktop model programmatically to ensure up-to-date reports.; Modify metadata such as table descriptions or measure formats using TOM commands.; Automate model documentation by extracting schema and measure definitions from Power BI Desktop.; Debug DAX expressions by running them against the local model and inspecting results..