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://mp-staging.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/design/archetypes/comparative-benchmark.md

Comparative / Benchmark Dashboard

Job To Be Done
Core Principles
IBCS Primer
- When to Use IBCS
Layout Variants
- Variant A — Side-by-Side (default, small multiples + headline)
- Variant B — Stacked-Pairs
Callout Evidence Rule
- Variant C — Slope-Graph-First
Chart Selection
- Use
- Do NOT Use
Variance Encoding Standards (continued in comparative-benchmark-part-02.md)
Color & Typography — continued in comparative-benchmark-part-02.md
- Diverging Palette (continued in comparative-benchmark-part-02.md)
- IBCS Purist Palette (continued in comparative-benchmark-part-02.md)
- Typography (continued in comparative-benchmark-part-02.md)
Interaction Design (Moderate) (continued in comparative-benchmark-part-02.md)
- Sort Toggle Implementation (continued in comparative-benchmark-part-02.md)
PBI Formatting Reference (continued in comparative-benchmark-part-02.md)
- Comparison Charts (continued in comparative-benchmark-part-02.md)
- Variance Formatting (continued in comparative-benchmark-part-02.md)
- Navigation & State — continued in comparative-benchmark-part-02.md
- Known Gaps (continued in comparative-benchmark-part-02.md)
Decision Checklist (continued in comparative-benchmark-part-02.md)

Archetype: Comparative / Benchmark Theme: for generated reports, preserve references/design/assets/base.json safeguards while adapting dataColors to domain; for brownfield, preserve the existing theme unless a theme swap is requested Canvas: greenfield default FHD 1920 x 1080; preserve existing size for brownfield unless resize is approved Core question: "Relative to what?"

Job To Be Done

Dimension	Value
Primary user	FP&A analyst, regional manager, product owner
Core question	"Relative to what?" — rank, pair, or benchmark 2+ entities
Typical queries	"Which region overperforms plan?" "Did Product B close the gap to A YoY?"
Success metric	Differences immediately visible — deltas, %, rank shifts, gap-to-benchmark
Failure signal	Viewer does arithmetic in their head
Design implication	Pre-compute every comparison; show absolute AND relative variance

Core Principles

#	Principle	Rationale
1	Shared scales across every small multiple	Independent Y axes silently lie
2	Diverging palette centered at zero	Variance direction is instantly visible
3	Consistent ordering	Sort by recent value or variance desc — NEVER alphabetical (unless lookup)
4	Absolute AND relative variance	Show both when scales differ; Δ and Δ% side by side
5	Align pairs, don't stack	Clustered bars / dumbbells, NOT stacked bars
6	Every comparison has a baseline — draw it	Reference line, constant line, or dedicated series
7	IBCS where audience is trained	Adopt wholesale in finance; cherry-pick notation elsewhere

IBCS Primer

Concept	Description
SUCCESS	Say, Unify, Condense, Check, Express, Simplify, Structure
Visual vocabulary	Filled = Actual (AC), Outlined = Prior Year (PY) / Budget (BU), Hatched = Forecast (FC)
Variance columns	Δ absolute + Δ% side by side
Category axis	Left-aligned text
Time axis	Always horizontal

When to Use IBCS

Context	Recommendation
Finance / controlling audience trained in IBCS	Adopt full visual vocabulary
Mixed audience	Cherry-pick: variance columns + Δ/Δ% notation
Consumer-facing / marketing	Skip IBCS; use standard charting

Caution: IBCS is a coherent system — partial adoption can confuse viewers who expect the full vocabulary.

Layout Variants

Pick ONE variant based on the comparison shape from Step 0. Do NOT mix. Default to A only when signals genuinely tie — record the signal that drove your pick in variant_rationale.

Signal (from semantic model + brief)	Variant
4–6 entities to compare across one metric over time (AC vs PY trend per entity)	A. Side-by-Side
2–4 paired comparisons (AC vs Plan, this-year vs last-year) — pair-wise framing	B. Stacked-Pairs
Ranking many entities (8+) on a single metric — rank shift / position is the point	C. Slope-Graph-First

Variant A — Side-by-Side (default, small multiples + headline)

Headline variance chart on the left, optional big-idea callout on the right, small-multiples trellis below. Use the callout only when it adds derived comparison insight (variance %, delta, gap-to-benchmark, rank shift, exception threshold, or generated explanatory text). If the only available value is the same absolute measure already plotted in the headline chart, skip the callout and expand the variance chart, add a compact detail table, or use the space for filter/context notes.

┌──────────────────────────────────────────────────────────┐
│  PAGE TITLE + comparison dimension + period              │  h=56
├──────────────────────────────┬───────────────────────────┤
│                              │                           │
│  HEADLINE VARIANCE           │  OPTIONAL CALLOUT         │
│  (tornado / ranked Δ bar)    │  "EMEA is 12% below plan" │  h=200
│  sorted by abs(Δ) desc       │                           │
│                              │                           │
├──────────────────────────────┴───────────────────────────┤
│  SMALL MULTIPLES (4–6 panels, shared Y axis)             │
│  ┌─Ent A─┐ ┌─Ent B─┐ ┌─Ent C─┐ ┌─Ent D─┐ ┌─Ent E─┐    │  h=260
│  │ AC|PY │ │ AC|PY │ │ AC|PY │ │ AC|PY │ │ AC|PY │    │
│  │ Δ%:+4%│ │ Δ%-12%│ │ Δ%:+1%│ │ Δ%:-3%│ │ Δ%:+8%│    │
│  └───────┘ └───────┘ └───────┘ └───────┘ └───────┘    │
├──────────────────────────────────────────────────────────┤
│  methodology · outlier notes · refresh · source          │  h=40
└──────────────────────────────────────────────────────────┘

Zone	Height	Content
Title	56 px	Page title + comparison dimension + period selector
Headline variance	200 px	Ranked Δ bar or tornado + optional big-idea callout with derived insight
Small multiples	260 px	4–6 panels, shared Y, AC \| PY per panel, Δ% annotation
Footer	40 px	Methodology, outlier notes, refresh timestamp

Variant B — Stacked-Pairs

One paired comparison per row. Each row pairs an entity (or measure) with its baseline. Use when the comparison is fundamentally pair-wise and the entities aren't peers of each other.

┌──────────────────────────────────────────────────────────┐
│  PAGE TITLE + period + scenario [AC ▼] [vs PY ▼]         │  h=56
├──────────────────────────────────────────┬───────────────┤
│  PAIR 1 — Revenue: AC vs Plan            │ Δ: +$4.2M     │  h=140
│  ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ AC          │ Δ%: +6%       │
│  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ Plan          │ ↑ favorable    │
├──────────────────────────────────────────┼───────────────┤
│  PAIR 2 — Margin %: AC vs Plan           │ Δ: -1.4 pp    │  h=140
│  ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ AC               │ Δ%: -7%       │
│  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ Plan            │ ↓ unfavorable  │
├──────────────────────────────────────────┼───────────────┤
│  PAIR 3 — Orders: AC vs PY               │ Δ: +1,240     │  h=140
│  ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓ AC                │ Δ%: +9%       │
│  ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒ PY                   │ ↑ favorable    │
├──────────────────────────────────────────┴───────────────┤
│  PAIR 4 — (similar)                                       │  h=140
├──────────────────────────────────────────────────────────┤
│  methodology · outlier notes · refresh · source          │  h=40
└──────────────────────────────────────────────────────────┘

Zone	Height	Content
Title	56 px	Title + period + scenario toggle (AC / PY / BU / FC)
Pair row 1–N	140 px each	Bar pair (left ~960px) + variance summary block (right ~272px)
Footer	40 px	Methodology, outlier notes, refresh timestamp

Each row is a complete comparison with its own variance summary — Δ absolute, Δ%, and a directional arrow. Maximum 4 pair rows per page; beyond that, split into multiple pages or switch to A.

Callout Evidence Rule

Callouts are conditional. A callout placement must name its callout_value_basis in the design brief:

Acceptable basis	Example
Absolute + relative variance	`Sales vs Plan: -$1.2M (-8.4%)`
Rank shift	`Region moved from #5 to #2 YoY`
Gap-to-benchmark	`Margin trails peer median by 3.1 pp`
Threshold exception	`3 segments below SLA target`
Dynamic narrative measure	`Top driver text` measure generated from model logic

Implementation may be a textbox, compact KPI/context tile, or Smart Narrative (aiNarratives). Choose Smart Narrative only when the summary needs to respond dynamically to filters and the authoring mode verifies the formatting/query mechanics for the target report version.

Do not create a callout whose only value is the same absolute measure used by the adjacent bar/line/table. A plain Total Sales card next to a Total Sales by Region chart is redundant; the chart already carries that measure.

Variant C — Slope-Graph-First

A slope graph (or dot plot) ranking many entities dominates the page. Position on the shared scale IS the point — readers see who moved up/down at a glance. Supporting bar chart shows current absolute values.

┌──────────────────────────────────────────────────────────┐
│  PAGE TITLE + comparison dimension + period              │  h=56
├──────────────────────────────────────────────────────────┤
│                                                          │
│  SLOPE GRAPH — entity rank/position, period A → period B │
│                                                          │
│  Ent01 ●─────────────────────────────● Ent01             │  h=420
│  Ent02 ●╲           ╱──────────────● Ent03               │
│  Ent03 ●─╲─────────╱──────────────●  Ent02              │
│  Ent04 ●──╲───────╱────────────────● Ent04               │
│  Ent05 ●───╲─────╱─────────────────● Ent06               │
│  Ent06 ●────╲───╱──────────────────● Ent05               │
│  ...                                                     │
│        period A                          period B        │
├──────────────────────────────────────────────────────────┤
│  SUPPORTING — current-period ranked bar, all entities    │  h=200
│  Ent01 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                            │
│  Ent03 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                                │
│  Ent02 ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓                                 │
├──────────────────────────────────────────────────────────┤
│  methodology · refresh · source                          │  h=40
└──────────────────────────────────────────────────────────┘

Zone	Height	Content
Title	56 px	Title + comparison dimension + period selector
Slope graph	420 px	All entities, position = metric value at start/end period; crossing lines show rank shifts
Supporting bar	200 px	Same entities ranked by current-period absolute value
Footer	40 px	Methodology, refresh, source

PBI has no native slope graph — simulate with a lineChart (categorical X axis: period A, period B). Highlight gainers and losers in two distinct colors; everything else grey. Use the supporting bar to give absolute scale that the slope graph hides.

Chart Selection

Use

Visual type	Role	Best for
Paired / clustered bar	AC vs PY side by side	Direct entity comparison
Dumbbell plot (simulated)	Gap = variance	Before / after or actual vs target
Variance column	Standalone Δ bars diverging at zero	Deviation magnitude + direction
Small multiples trellis	Shared Y, one panel per entity	Time trend across entities
Ranked horizontal bar	Sorted by metric desc	Performance ranking
Tornado / butterfly	Back-to-back bars	Two-entity head-to-head
`waterfallChart`	Additive contribution	Bridge from budget to actual
Dot plot / barbell	Position on shared scale	Multiple entities on one axis

Do NOT Use

Visual type	Reason
Stacked bar	Obscures per-segment comparison; inner segments lack common baseline
`pieChart` / `donutChart`	Cannot show variance or deviation
`gauge`	Single-entity; no comparison affordance
Radar / spider	Distorts magnitude via area encoding

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-08

Also distributed in

microsoft/skills-for-fabric

AutoGineer is not affiliated with or endorsed by Microsoft.

Download ZIP

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