Powerbi Report Authoring
Create and modify Power BI report files in PBIR/PBIP format using the `powerbi-report-author` and `powerbi-desktop` CLIs. Use when the user wants to: (1) implement an approved report spec or design brief, (2) add or edit pages, visuals, filters, slicers, bookmarks, themes, or formatting, (3) validate PBIR and verify rendering in Power BI Desktop. For open-ended visual design, use `powerbi-report-design` first. For end-to-end requirements and approval workflow, use `powerbi-report-planning` first. Triggers: "edit PBIR", "create Power BI report page", "add visual to PBIP", "format report visual", "validate Power BI report", "reload Desktop screenshot", "implement an approved PBIP report spec", "edit PBIR pages/visuals".
30-Second Summary
Powerbi Report Authoring is an agent-readable workflow from microsoft/skills-for-fabric for powerbi report authoring.
It gives the agent a trigger, ordered guidance, and source-backed checks instead of treating powerbi report authoring as a generic tool.
Use it as a brief only while the linked SKILL.md remains available and the risk boundary is still accurate.
1-Minute Read
What it is
Powerbi Report Authoring packages instructions from microsoft/skills-for-fabric into a reusable agent skill brief. The original source is a public SKILL.md file, so the brief can point readers back to the executable workflow instead of a product landing page.
When to use it
Use it when a user asks for help around powerbi report authoring and the agent needs a repeatable workflow, checklist, or review path rather than broad background information.
How to test it first
Open the linked SKILL.md, confirm the trigger and procedure still match powerbi report authoring, list the risk boundary, then ask the agent to apply the smallest read-only step to a sample task.
Watch out
Do not present this as a generic app or platform. Keep the scope tied to microsoft/skills-for-fabric. Risk boundary: git state, commit, branch, PR, or push actions require explicit repo-owner approval before mutation; CI/CD, deploy, release, rollback, and migration steps must start with read-only inspection and an approval gate; database, Fabric workspace, notebook, lakehouse, warehouse, or Power BI changes need credential and production-data approval; cloud resources, RBAC, credentials, tokens, and private keys must not be changed or exposed without a separate approval; Microsoft Fabric-specific workflow; do not describe it as a generic data engineering skill.