Develop Power BI and Fabric artifacts with agent plugins
Install Power BI and Microsoft Fabric plugins so Claude Code can author, validate, and review PBIP, TMDL, DAX, reports, semantic models, and related project files.
npx skills add agentskillexchange/skills --skill develop-power-bi-and-fabric-artifacts-with-agent-plugins
claude plugin marketplace add data-goblin/power-bi-agentic-development, then install only the needed child plugin, for example claude plugin install pbip@power-bi-agentic-development, claude plugin install semantic-models@power-bi-agentic-development, or claude plugin install reports@power-bi-agentic-development. Use /plugin, /skills list, and the plugin README to confirm what loaded before editing project files.Use this workflow when an operator wants Claude Code to work inside a Power BI or Microsoft Fabric project with domain-specific instructions, validators, agents, and hooks instead of relying on general coding prompts. The upstream repository is a plugin marketplace with installable child plugins for Tabular Editor, Power BI Desktop, PBIP, semantic models, reports, paginated reports, custom visuals, Fabric CLI, Fabric administration, and ETL work.
What this skill actually does
The agent should first register the marketplace, install only the plugin that matches the current project, then inspect the available skills, commands, agents, and hook configuration before editing BI artifacts. Appropriate tasks include writing or reviewing TMDL, authoring PBIR report metadata, connecting to a Power BI Desktop model, running Tabular Editor automation, validating project structure, checking DAX references, and keeping generated changes reviewable in source control.
Invoke this instead of using the Power BI UI normally when the work is file-backed, repeatable, reviewable, or spread across many artifacts. Do not use it as a generic Power BI product listing, a replacement for licensed Power BI/Fabric access, or a way to bypass normal deployment approval. The boundary is the installed plugin workflow: the agent acts on documented project files, CLI tools, hooks, and validation outputs, while the operator remains responsible for credentials, environment access, publishing, and final review.