---

name: powerbi-report-cli description: "Plan, design, author, preview, publish, and manage Power BI reports across requirements, page design, local PBIR/PBIP edits, validation, screenshots, Fabric upload/download, and rebinding. Use for report lifecycle work; use semantic-model-authoring for model or DAX changes and fabriciq for data questions. Triggers: plan Power BI report, design report page, edit PBIR, preview PBIP, publish report, rebind report" metadata: version: 1.0.4

Telemetry — MANDATORY. Every api.fabric.microsoft.com call must carry x-ms-fabric-skill: powerbi-report-cli (az rest: --headers "x-ms-fabric-skill=powerbi-report-cli"), including every LRO poll, fabric_lro and retry. Snippets omit it — add it anyway.

CRITICAL NOTES

1. To find workspace details, including its ID, from a workspace name: list all workspaces, then use JMESPath filtering.
2. To find item details, including its ID, from a workspace ID, item type, and item name: list all items of that type in that workspace, then use JMESPath filtering.
3. Use powerbi-report-cli for the report artifact: requirements, design, PBIR/PBIP page and visual edits, preview, and publishing. Semantic model, measure, and DAX work belongs to a semantic-model skill. Natural-language questions about report data belong to fabriciq.

Power BI Reports - CLI Skill

This skill owns the Power BI report lifecycle end to end: requirements and scope, visual design, local PBIR/PBIP authoring and preview, and report-item transport to and from Microsoft Fabric.

It is a mode dispatcher and intentionally contains no detailed procedures. Select the mode that matches the request, then read the matching mode reference end to end before acting. The mode file holds the required workflow, commands, payloads, templates, and failure rules.

Mode Selection

| Mode | Use when the request... | Existing route examples | Read first | |---|---|---|---| | planning | creates a new report/dashboard and needs requirements, model/dependency inspection, scope, a page plan, and approval before implementation | create a report, build a dashboard, create from a semantic model, plan then implement, walk me through creating a report | references/planning.md, then references/planning-part-02.md | | design | decides what a report should look like: tone, signature, page archetype, chart type, layout, color, typography, theme direction, accessibility, brand application, redesign, or critique | design a Power BI report, make the dashboard professional, choose a chart, apply a brand, redesign the report, create a design brief | references/design.md | | authoring | reads or edits local PBIR/PBIP files, validates them, previews the report, or captures screenshots | edit PBIR, create/add a report page or visual, format a visual, add filters/slicers/bookmarks/themes, validate PBIR, preview/reload/screenshot in Desktop or service | references/authoring.md | | management | moves a report definition to or from Fabric or manages the workspace report item | publish/upload/download PBIR or PBIP, list reports, get/update/delete a report, rebind a report | references/management.md |

Mode Boundary Rules

• Classify by intent, not by which file or tool is already open.
• design decides what the report should look like; authoring writes the PBIR that realizes it. Choosing a chart type is design; encoding it into visual.json is authoring.
• Restyling or reformatting an existing local report is authoring, even when the request uses design language. Use design when the user wants advice or a design contract rather than a file change.
• authoring changes local files and performs preview/validation. It does not publish to Fabric.
• management transports definitions and manages Fabric report items. It does not invent or directly author PBIR content.
• planning owns the guided requirements-to-approval flow for a new report. A focused edit to an existing report goes directly to authoring.

A greenfield request can span modes in this order:

planning -> design -> authoring -> management

Handle one mode at a time. Announce each switch and read the new mode reference before starting that part. The planning approval gate is a turn boundary: never build or publish until the user explicitly approves the locked spec in a later reply.

Required Deliverable by Mode

| Mode | Completion requirement | |---|---| | planning | Persist _brief/report-spec.md or the user-named equivalent, ask for explicit approval, and stop before implementation. | | design | Produce the complete Design Brief: contract, including design_identity and a page archetype/layout contract for every page. Do not edit PBIR or call Fabric APIs. | | authoring | Persist the requested PBIR/PBIP changes, validate each logical batch, then complete the selected preview and screenshot-review workflow required by the authoring reference. Do not publish. | | management | Complete the requested Fabric report operation, including LRO polling and documented readback verification. |

Rules

MUST

• Select the narrowest mode that fully covers the current request.
• Read references/<mode>.md end to end before the first command or file edit in that mode.
• In planning mode, also read references/planning-part-02.md before producing _brief/report-spec.md; it contains the required canonical design contract and approval checks.
• Preserve every argument and safety boundary documented by the selected mode.
• Announce and perform an explicit mode switch when the request crosses a boundary.
• Use the powerbi-report-author CLI metadata and validation surfaces instead of guessing PBIR schemas, roles, formatting properties, selectors, or enum values.
• Keep local edits local unless the user explicitly requests publishing.
• Resolve Fabric workspace and item IDs by listing and filtering rather than guessing identifiers.
• Produce the artifact the user requested; reading or summarizing a reference is not task completion.

PREFER

• Infer facts already present in the prompt, semantic model, existing PBIP, or prior approved spec instead of asking again.
• Load only the selected mode and its directly relevant topic references.
• Preserve the user's existing project structure, schemas, host, operation, binding, and delivery target unless the selected mode explicitly requires a change.

AVOID

• Acting from this dispatcher without reading the selected mode reference.
• Loading a retired sibling skill name; planning, design, authoring, and management are modes of this skill.
• Editing PBIR or calling Fabric APIs in planning or design.
• Publishing from authoring, or authoring PBIR content from management.
• Bypassing the planning approval gate because the original request also asked to build or publish.

<!-- BEGIN GENERATED REFERENCE INDEX -->

Complete Reference Index

Open every relevant reference directly from this index. Files named part-XX continue the named topic.

Authoring

• authoring/authoring-workflows
• authoring/bookmark
• authoring/button-part-02
• authoring/button-part-03
• authoring/button
• authoring/card-part-02
• authoring/card-part-03
• authoring/card
• authoring/cartesian-part-02
• authoring/cartesian-part-03
• authoring/cartesian-part-04
• authoring/cartesian
• authoring/color-strategy
• authoring/conditional-formatting-part-02
• authoring/conditional-formatting-part-03
• authoring/conditional-formatting-part-04
• authoring/conditional-formatting-part-05
• authoring/conditional-formatting-part-06
• authoring/conditional-formatting-part-07
• authoring/conditional-formatting
• authoring/custom-visuals
• authoring/expressions
• authoring/field-parameters
• authoring/filter-pane
• authoring/filters
• authoring/formatting-overview
• authoring/formatting-part-02
• authoring/formatting
• authoring/image
• authoring/kpi
• authoring/map
• authoring/model-binding
• authoring/page-formatting
• authoring/powerbi-desktop
• authoring/powerbi-report-author-cli-part-02
• authoring/powerbi-report-author-cli
• authoring/preview-part-02
• authoring/preview-part-03
• authoring/preview-part-04
• authoring/preview
• authoring/re-theming-part-02
• authoring/re-theming-part-03
• authoring/re-theming
• authoring/screenshot-review
• authoring/shape
• authoring/slicers-part-02
• authoring/slicers
• authoring/table
• authoring/textbox
• authoring/theming-part-02
• authoring/theming
• authoring/version-control

Design

• design/accessibility
• design/anti-patterns
• design/archetype-composition
• design/archetypes/analytical-canvas
• design/archetypes/comparative-benchmark-part-02
• design/archetypes/comparative-benchmark
• design/archetypes/executive-summary
• design/archetypes/narrative-story
• design/archetypes/operational-monitor
• design/brownfield
• [design/chart-selection](references/design/chart-