Powerbi Report CLI

MicrosoftOfficialPublished by Microsoft

Skill
Tool integration
Data and AI
MIT
Low risk

From the author

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

— the description by Microsoft

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The powerbi-report-cli skill provides a structured, mode-based framework for managing the entire Power BI report lifecycle. It acts as a dispatcher across four distinct phases: planning (requirements and scope), design (visual and layout strategy), authoring (local PBIR/PBIP file manipulation and validation), and management (Fabric item transport and rebinding). The skill enforces strict boundaries between these modes to ensure quality, requiring explicit approval for new reports and utilizing a dedicated CLI for metadata-driven validation and authoring tasks.

What it does

Guides users through report requirements, scope, and page planning.
Provides design contracts for visual archetypes, layouts, and branding.
Enables local editing, validation, and previewing of PBIR and PBIP files.
Handles report item transport to and from Microsoft Fabric.
Supports re-theming, conditional formatting, and visual configuration.
Enforces a mandatory approval gate for greenfield report development.

When to use it

When planning a new Power BI report from a semantic model.
When you need to define a professional design brief or layout strategy.
When editing local PBIR/PBIP files, including visuals, filters, and themes.
When validating report structure and formatting before deployment.
When publishing or managing report items within a Fabric workspace.

Advantages

Ensures consistent report quality through a structured, multi-mode workflow.
Prevents premature publishing by enforcing a mandatory approval barrier.
Uses a dedicated CLI to eliminate guesswork in PBIR schema and property editing.
Maintains clear separation between design intent and technical implementation.
Provides robust validation tools to catch errors before Fabric deployment.

Usage examples

“Create a new executive report from this semantic model.”: The agent enters planning mode, inspects the model, generates a report spec, and requests user approval before proceeding.
“Design an operational page and choose the right charts.”: The agent enters design mode, produces a design brief with page archetypes and chart recommendations.
“Add a KPI page to this PBIP, validate it, and take screenshots.”: The agent enters authoring mode, modifies the local PBIP files, runs validation, and captures screenshots for review.
“Publish this local PBIP to my Fabric workspace and rebind it.”: The agent enters management mode, performs the upload to Fabric, and completes the rebind operation.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/microsoft/powerbi-report-cli/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip powerbi-report-cli.zip -d .agents/skills

Documentation by Microsoft

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
To find workspace details, including its ID, from a workspace name: list all workspaces, then use JMESPath filtering.
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.
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.

GREENFIELD APPROVAL BARRIER — MANDATORY. When a new-report request asks to plan, build, and/or publish but the user has not approved a locked spec in a prior reply, set the current phase to approval_pending and keep planning as the only active mode. In this phase, do not load authoring or management, edit/scaffold PBIR or semantic-model files, generate synthetic data, call Fabric write APIs, or publish. Persist _brief/report-spec.md, ask for explicit approval, and end the turn. The build/publish wording in the original request is desired future scope, not approval to cross this barrier.

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. When an already-loaded mode explicitly routes one narrow cross-mode operation to a named topic reference, treat that topic reference as the complete handoff; do not load the target mode's umbrella file unless the work expands beyond that operation.
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.
Across a multi-turn task, retain a compact working state containing resolved workspace/item/model IDs, local and downloaded paths, and references already read. Reuse it in later turns unless the user explicitly requests a fresh query or the preceding operation invalidated a value.
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.
Reuse reference guidance already loaded in the current task. Open a new reference only when the requested operation or an observed mismatch requires it.
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.
Reloading this dispatcher, a mode file, or a topic reference already read in the current task solely because the conversation advanced to a later turn.
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.

Complete Reference Index

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

Authoring

Design

Mode Guides

Examples

User request	Mode
"Create a new executive report from this semantic model."	`planning`
"Design an operational page and choose the right charts."	`design`
"Add a KPI page to this PBIP, validate it, and take screenshots."	`authoring`
"Publish this local PBIP to my Fabric workspace and rebind it."	`management`

Route Compatibility

The merged skill preserves the four previous route surfaces. Treat the following phrases as explicit aliases for the corresponding mode:

Mode	Preserved route phrases
`planning`	create a report; build a report; create a dashboard; create a new report from scratch; create a report from a semantic model or dataset link; build a report for this model; make me a dashboard; plan then implement; walk me through creating a report
`design`	design Power BI report; make dashboard look professional; choose chart type; apply brand to report; redesign report; create design brief; Power BI report design archetype
`authoring`	edit PBIR; create Power BI report page; add visual to PBIP; format report visual; validate Power BI report; preview Power BI report; Power BI Desktop preview status; preview report in service; preview report in browser; screenshot report page; screenshot all report pages; list preview hosts; implement dashboard in PBIP; add dashboard visuals to report; implement an approved PBIP report spec; edit PBIR pages/visuals; edit a Power BI report
`management`	upload PBIR report definition; upload Power BI report; download PBIR definition; publish PBIR definition; publish Power BI report to Fabric; manage Power BI reports; list workspace reports

Files

ATTRIBUTION.mdAdded by AutoGineer881 B
LICENSELicence file added by AutoGineer1.1 KiB
SKILL.md16.1 KiB
apm.yml642 B
references/authoring-part-02.md14.6 KiB
references/authoring-part-03.md16.0 KiB
references/authoring-part-04.md15.9 KiB
references/authoring.md16.8 KiB
references/authoring/authoring-workflows.md11.7 KiB
references/authoring/bookmark.md14.3 KiB
references/authoring/button-part-02.md16.1 KiB
references/authoring/button-part-03.md7.7 KiB
references/authoring/button.md15.7 KiB
references/authoring/card-part-02.md16.1 KiB
references/authoring/card-part-03.md8.6 KiB
references/authoring/card.md6.4 KiB
references/authoring/cartesian-part-02.md17.7 KiB
references/authoring/cartesian-part-03.md12.3 KiB
references/authoring/cartesian-part-04.md15.8 KiB
references/authoring/cartesian.md18.0 KiB
references/authoring/color-strategy.md8.4 KiB
references/authoring/conditional-formatting-part-02.md13.5 KiB
references/authoring/conditional-formatting-part-03.md16.0 KiB
references/authoring/conditional-formatting-part-04.md14.0 KiB
references/authoring/conditional-formatting-part-05.md16.9 KiB
references/authoring/conditional-formatting-part-06.md14.7 KiB
references/authoring/conditional-formatting-part-07.md14.5 KiB
references/authoring/conditional-formatting.md18.2 KiB
references/authoring/custom-visuals.md13.9 KiB
references/authoring/expressions.md11.9 KiB
references/authoring/field-parameters.md5.1 KiB
references/authoring/filter-pane.md5.0 KiB
references/authoring/filters.md9.3 KiB
references/authoring/formatting-overview.md4.8 KiB
references/authoring/formatting-part-02.md3.3 KiB
references/authoring/formatting.md17.0 KiB
references/authoring/image.md12.6 KiB
references/authoring/kpi.md2.5 KiB
references/authoring/map.md13.4 KiB
references/authoring/model-binding.md7.7 KiB
references/authoring/page-formatting.md4.5 KiB
references/authoring/powerbi-desktop.md2.4 KiB
references/authoring/powerbi-report-author-cli-part-02.md3.2 KiB
references/authoring/powerbi-report-author-cli.md17.7 KiB
references/authoring/preview-part-02.md16.9 KiB
references/authoring/preview-part-03.md4.0 KiB
references/authoring/preview-part-04.md2.5 KiB
references/authoring/preview.md16.1 KiB
references/authoring/re-theming-part-02.md16.8 KiB
references/authoring/re-theming-part-03.md4.9 KiB
references/authoring/re-theming.md1.5 KiB
references/authoring/screenshot-review.md5.0 KiB
references/authoring/shape.md13.6 KiB
references/authoring/slicers-part-02.md16.3 KiB
references/authoring/slicers.md15.6 KiB
references/authoring/table.md17.5 KiB
references/authoring/textbox.md5.6 KiB
references/authoring/theming-part-02.md6.7 KiB
references/authoring/theming.md16.4 KiB
references/authoring/version-control.md6.6 KiB
references/design.md17.3 KiB
references/design/accessibility.md11.4 KiB
references/design/anti-patterns.md18.5 KiB
references/design/archetype-composition.md3.4 KiB
references/design/archetypes/analytical-canvas.md17.7 KiB
references/design/archetypes/comparative-benchmark-part-02.md5.7 KiB
references/design/archetypes/comparative-benchmark.md15.8 KiB
references/design/archetypes/executive-summary.md14.7 KiB
references/design/archetypes/narrative-story.md18.1 KiB
references/design/archetypes/operational-monitor.md17.0 KiB
references/design/assets/base.json7.5 KiB
references/design/brownfield.md5.7 KiB
references/design/chart-selection.md9.8 KiB
references/design/color.md10.5 KiB
references/design/design-brief-part-02.md13.7 KiB
references/design/design-brief.md8.8 KiB
references/design/interactivity.md9.2 KiB
references/design/layout.md11.3 KiB
references/design/pre-flight-checklist.md10.8 KiB
references/design/signatures.md12.3 KiB
references/design/tone-catalog.md14.4 KiB
references/design/typography.md9.2 KiB
references/design/visual-cookbook-part-02.md11.0 KiB
references/design/visual-cookbook.md16.7 KiB
references/management-part-02.md17.2 KiB
references/management-part-03.md7.5 KiB
references/management-part-04.md16.7 KiB
references/management.md10.1 KiB
references/planning-part-02.md11.2 KiB
references/planning.md19.5 KiB

references/authoring-part-04.md

powerbi-report-cli authoring mode -- Power BI Report Authoring (PBIR/PBIP) - Part 4

Continuation of authoring.md. Open this file directly from the skill reference index.

Anti-Patterns and Pitfalls

Pitfall	Consequence	Fix
Using `"Entity"` inside filter `Where` conditions	Filter silently fails	Use `"Source"` with the alias from `From`
Omitting `nativeQueryRef`	Visual calculations may break	Always include `nativeQueryRef`
Reusing visual/filter names	Unpredictable behavior	Generate unique IDs
Setting `visualType` to invalid string	Visual renders as error box	Run `powerbi-report-author catalog describe <type>` or `powerbi-report-author catalog list`
Adding a private `.pbiviz` by only unpacking it into `CustomVisuals/`	Visual renders "To see this custom visual, add it to this report first"; `validate` flags it with a `PBIR_VISUAL_TYPE_UNKNOWN` warning because the GUID isn't registered	Also register it in `report.json` → `resourcePackages` with `type: "CustomVisual"` — see custom-visuals.md (see `authoring/custom-visuals.md`)
Wrong role name for visual type	Field is ignored; visual blank	Match role names from `powerbi-report-author catalog describe <type>`
Mixing `Column` and `Measure` types	Query fails; visual error	Columns use `Column`, measures use `Measure`
Forgetting to add page to `pages.json`	Page invisible	Add to `pageOrder` array
Creating a bookmark file without updating `bookmarks.json`, or leaving stale page/visual/filter IDs in saved state	Bookmark is absent, disabled, or silently applies incomplete state	Follow `bookmark.md` (see `authoring/bookmark.md`); validate every bookmark and action target before Desktop reload
Booleans without correct format	Wrong type	`"true"` / `"false"` (no suffix, unquoted in Value)
Numbers without type suffix	Type mismatch	`D` for decimals, `L` for integers
Editing `$schema` version	PBI Desktop may reject	Preserve existing version
Stringified JSON in `paragraphs`	Textbox shows nothing	`paragraphs` is a native JSON array
Using textbox as a thin line/divider	Renders ~24px tall regardless of `height`	Use a `shape` visual (rectangle) instead — shapes respect small dimensions
`visualContainerObjects` as sibling of `visual`	Schema validation error in PBI Desktop	Must be inside `visual` object, as sibling of `objects`
Using `tableEx` with dimension columns and measures all in `Values`	Headers render but no data rows even when DAX confirms data exists	Use `pivotTable`; put dimensions in `Rows` and measures in `Values`
Using PowerShell `ConvertTo-Json` to edit visual JSON	Property reordering, nesting depth truncation (`-Depth` default is 2)	Use Node.js for JSON manipulation, or always pass `-Depth 20` and verify structure
Using regex or string replacement to modify JSON files	Corrupts nesting structure — properties end up inside sibling values, braces misalign	Read file → `JSON.parse` → modify object → `JSON.stringify` → write back. Or use the `edit` tool with exact old/new string matching
`dataPoint.fill` without a selector on single-series charts	Bars/columns invisible despite data in tooltips	Use `dataPoint.defaultColor` for a base color without a selector; `fill` requires a `metadata` selector
Using `dataPoint.defaultColor` on multi-series charts	All series/categories get the same color — no visual differentiation	Use theme `dataColors` for consistent palette across visuals, or `dataPoint.fill` with `metadata` selectors for per-series overrides — see color-strategy.md § Color Strategy Quick Reference (see `authoring/color-strategy.md`, section `color-strategy-quick-reference`)
Clustered bar/column chart colors collapse into one legend color	The visual has a Series role but all bars and legend markers share the same hue	Use per-series `dataPoint.fill` selectors or a theme `dataColors` palette; do not use `defaultColor` on clustered charts
Relying on theme `dataColors` alone for cross-visual measure consistency	Same measure gets different colors on different visuals (index-based assignment varies with projection order)	Maintain a measure→color mapping and apply explicit `dataPoint.fill`/`defaultColor` per visual — see color-strategy.md § Cross-Visual Measure-Color Consistency (see `authoring/color-strategy.md`, section `pattern-cross-visual-measure-color-consistency`)
Using `ThemeDataColor` for explicit per-measure `dataPoint.fill` with metadata selectors	Colors silently resolve to white or black instead of expected palette color	Use `Literal` hex values for explicit color assignments with metadata selectors — `ThemeDataColor` is unreliable in this context
Choosing bar/series colors without checking background contrast	Bars or lines invisible against page/card background (e.g., white bars on white canvas)	Always pick saturated, mid-to-dark hues that contrast with the page and VCO background colors
`show` property on page-level `background`	Schema error — page `background` only supports `color`, `image`, `transparency`	Only VCO `background` (on visuals) has `show`; page background is always visible
Copying property names from doc examples without verifying	Warnings or silent failures — property names vary by visual type	Always run `powerbi-report-author formatting describe-object <type> <object>` for exact property names
Guessing which object a property belongs to	Wasted calls checking wrong objects one by one	Run `powerbi-report-author formatting search <type> <regex>` to grep across all objects at once
Formatting property has no effect (no error)	Setting `show: false` on cardVisual outline without an id selector — validates but renders unchanged	Check `powerbi-report-author formatting describe-object <type> <object>` for `_selectorHint`; use the dual-entry pattern (static + id selector entries)
Using `cardCalloutArea` on a single-value card	Properties validate but have no visible effect — `cardCalloutArea` only renders on multi-value cards (2+ measures in Data)	Use `outline`/`accentBar`/`fillCustom` with `{ id: "default" }` selector for single-value cards. For multi-value cards, `cardCalloutArea` controls per-callout tile styling — see card.md § Multi-Value Formatting (see `authoring/card-part-03.md`, section `multi-value-formatting`)
Using `"Fields"` as the `queryState` role for `cardVisual`	Cards render empty — PBI Desktop cannot resolve the binding. Validator reports `Unknown role "Fields"` and `Required role "Data" missing`	`cardVisual`'s only data role is `"Data"`. `"Fields"` is the legacy `card` visual's role name — never carry it over. Always verify role names with `powerbi-report-author catalog describe cardVisual` — see card.md § Single-Value Template (see `authoring/card.md`, section `single-value-template`)
Creating separate single-value `cardVisual` instances for multiple related KPIs	Wastes canvas space and misuses the visual type — `cardVisual` natively supports multiple projections in one tile	Default to one multi-value `cardVisual` with all measures as `Data` projections when ≥2 related KPIs are requested. Only use separate cards when per-card styling differences are required — see card.md § When to Consolidate vs. Keep Separate (see `authoring/card-part-03.md`, section `when-to-consolidate-vs-keep-separate`)
Adding multiple fields to button slicer Values or Label roles	Slicer breaks or shows unexpected results — each role accepts only 1 field	Put one field in Values, one in Label; additional fields go to Tooltips
Looking at `filterConfig` on other visuals to understand slicer selections	Slicer selections live only inside the slicer's own `visual.json` via `expansionStates` + `objects.general.filter`. Always read `references/authoring/slicers.md` first when modifying slicers
Creating an image visual without prompting for the source type	Wrong visual structure — URL vs local file vs data field each have different schemas and expression types	Always ask the user for the image source (local file / URL / data field) before creating the visual — see image.md § Source Types Overview (see `authoring/image.md`, section `source-types-overview`)
KPI `Indicator` bound to a column instead of a measure	Visual goes blank with no error	`Indicator` role requires `kind: Measure` — use a DAX measure or an `Aggregation` expression; see kpi.md § Why KPI Goes Blank (see `authoring/kpi.md`, section `why-kpi-goes-blank`)
KPI `TrendLine` bound to a text or category column	Visual goes blank or sparkline disappears	`TrendLine` requires a date, datetime, or monotonically increasing numeric column; never bind a text/category field — see kpi.md § Why KPI Goes Blank (see `authoring/kpi.md`, section `why-kpi-goes-blank`)
KPI `Indicator` measure returns `BLANK` at the latest trend point (e.g. date table extends into future)	Visual goes blank silently	Wrap the measure with `LASTNONBLANK` or `COALESCE`; see kpi.md § Why KPI Goes Blank (see `authoring/kpi.md`, section `why-kpi-goes-blank`)
KPI `Goal` measure granularity does not align with `Indicator` trend granularity	Target renders blank or zero; status direction wrong	Ensure the Goal measure evaluates at the same time grain as the Indicator — see kpi.md § Why KPI Goes Blank (see `authoring/kpi.md`, section `why-kpi-goes-blank`)
Creating a data-bound image visual with a field that lacks `dataCategory: ImageUrl`	Visual renders blank or error	Warn the user first — the visual will render blank without `dataCategory: ImageUrl`. Present alternatives (other ImageUrl fields, local file, URL) and confirm before creating — see image.md § Select from data (see `authoring/image.md`, section `3-select-from-data`)
Placing background image on page canvas instead of visual plot area	User asks for "background image" alongside a visual (e.g., "column chart with background image") but image is placed on `page.json → objects.background` instead of `visual.objects.plotArea`	When a background image is requested in the context of a specific visual, default to `plotArea.image`. Only use page-level `background.image` when the user explicitly says "page background" / "canvas background" or no visual context exists — see image.md § Plot Area Background Image (see `authoring/image.md`, section `plot-area-background-image-plotareaimage`)
Creating a `multiRowCard` visual	Legacy multi-row card — deprecated; `powerbi-report-author validate` warns with `PBIR_VISUAL_TYPE_DEPRECATED`. Often triggered by user phrases like "multi-card", "cards for each metric", or "card per measure"	Always use `cardVisual`. For multiple KPIs, use a single multi-value `cardVisual` with all measures as projections in the `Data` role — see card.md (see `authoring/card.md`, section `multi-value-template`)
Using `map` or `filledMap` instead of `azureMap` for map visuals	Legacy Bing Maps visuals — deprecated and must not be created; `powerbi-report-author validate` warns with `PBIR_VISUAL_TYPE_DEPRECATED`	Always use `azureMap` — see map.md (see `authoring/map.md`). If the map fails to render or geocode, debug the fields, try alternative geographic columns/coordinates, or ask the user — do not silently substitute a non-map visual without consulting the user first
Creating `tableEx`/`pivotTable` without `columnAdjustment: growToFit`	Columns shrink-wrap to content, leaving unused whitespace	Always set `columnHeaders.columnAdjustment` to `growToFit` and `autoSizeColumnWidth` to `true` — see table.md (see `authoring/table.md`, section `default-rule--grow-to-fit`)
Custom table/matrix row colors with no effect (white background)	Default style preset overrides `objects`-level `backColorPrimary`/`backColorSecondary`	Set `stylePreset` VCO to `'None'` on every `tableEx`/`pivotTable` with custom colors — see table.md § Style Presets (see `authoring/table.md`, section `style-presets-for-tables`)
Table cells white despite dark VCO background	`visualContainerObjects.background` only controls outer container — table cells paint on top	Set dark colors in `objects.values.backColorPrimary/Secondary` and `objects.columnHeaders.backColor`, not in VCO — see re-theming.md § Dark Mode Checklist (see `authoring/re-theming-part-03.md`, section `dark-mode-authoring-checklist`)
Dark theme applied but cards/tables/slicers still white	Dark mode triggers every formatting trap simultaneously	Follow the full re-theming.md § Dark Mode Authoring Checklist (see `authoring/re-theming-part-03.md`, section `dark-mode-authoring-checklist`) — covers stylePreset, fillCustom+id selector, objects vs VCO, and contrast audit
Theme JSON changes do not appear after preview reload	Theme registration is stale, or a host cached the theme file name	Rename the theme JSON with a small random suffix, update the theme registration in `report.json`, validate, then follow the host-specific reload workflow in preview.md (see `authoring/preview.md`)
Placing `sortDefinition` inside `visual` or at root of `visual.json`	Schema validation error; sort silently ignored — chart falls back to alphabetical	`sortDefinition` is a property of `query` — use `visual.query.sortDefinition`. Supported since `visualConfiguration/2.2.0`
Container shape fill doesn't match reference	Text invisible or wrong background color	Match the fill color and transparency to the reference image. If the page background already provides the color, skip the shape entirely. If the shape must be invisible, verify text color still contrasts with the page canvas — see shape.md § Container Shapes (see `authoring/shape.md`, section `container-shapes`)
Shape text invisible after re-theme	Shape `text` object has no explicit `fontColor` — text inherits theme foreground, but when `fill` is a light color (e.g., white pill/button) on a light page canvas, inherited dark foreground may not render or the fill blends with canvas making text vanish	Always set explicit `fontColor` on shape `text` objects (in the `{ selector: { id: "default" } }` entry). During re-theming, audit all shapes with `text.show: true` — bulk hex-replacement misses shapes that need a new `fontColor` property added
Enabling `logAxisScale` on data with zero or negative values	PBI Desktop silently falls back to linear scale with a warning — log of zero/negative is undefined	Warn the user before applying. Use `ask_user` to present alternatives (filter negatives, switch measure, use `labelDisplayUnits`). Apply `logAxisScale: true` only after the user resolves negative values or confirms all bound values are positive — see cartesian.md § Log Scale (see `authoring/cartesian-part-02.md`, section `log-scale-logaxisscale`)
Changing theme without sweeping inline overrides	Old colors remain on shapes, page backgrounds, nav buttons, textboxes — theme-only change has no effect on hardcoded `Literal` hex values at Priority 2 in the cascade	When the report has per-visual color overrides, follow re-theming.md § Re-theming Workflow (see `authoring/re-theming-part-02.md`, section `re-theming-an-existing-report`) Steps 0–3: build a color mapping, update theme JSON, then bulk-sweep `definition/` files for old hex values before preview
Changing only `dataColors` in theme without sweeping	Shapes, accent bars, nav button borders retain old accent colors — they use hardcoded Literal hex from the old `dataColors` array, not `ThemeDataColor` references	Sweep ALL old `dataColors[N]` hex values across `definition/` files. Even same-polarity "just change the accent/data colors" requests need the full sweep — shapes and nav elements commonly hardcode `dataColors[0]` as accent fills/outlines.

Official Documentation

For Microsoft Learn setup guidance, support constraints, and feature availability, use Power BI report authoring docs.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Security

What our scanner noticed· Low risk

Phrasing that asks for actions without confirmation
Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by

Microsoft

Publisher

Microsoft (Official)

Source

microsoft/skills-for-fabric · skills/powerbi-report-cli · commit f8fac11

Licence

MIT License (redistribution allowed)

LICENSE (added by AutoGineer from LICENSE)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-09

Also distributed in

microsoft/skills-for-fabric

AutoGineer is not affiliated with or endorsed by Microsoft or Microsoft.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download powerbi-report-cli.zip