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/design/archetypes/operational-monitor.md

Operational Monitor Dashboard

Job To Be Done
Core Principles
Layout Variants
- Variant A — 4-Up Status (default, balanced surveillance + triage)
- Variant B — Wallboard (TV-wall surveillance)
- Variant C — Incident-First (queue dominant for active responders)
Chart Selection
- Use
- Do NOT Use
Color & Typography
- Semaphore Palette
- Typography by Viewing Distance
Freshness & Refresh
- Staleness Decision Table
Interaction Design
PBI Formatting Reference
- Status Tiles
- Time Series
- Exception Table
- Refresh & Page
Decision Checklist

Archetype: Operational Monitor 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 · F-pattern Scan-time target: ≤ 5 seconds to "normal / not-normal"

Job To Be Done

Dimension	Value
Primary user	Shift operator, on-call engineer, warehouse supervisor
Session mode	Continuous peripheral surveillance; burst attention on anomaly
Core question	"Is it me or is it broken?"
Success metric	Deviation detected < 5 s, before downstream alert fires
Failure signal	Operator misses a state change visible on the dashboard
Design implication	Passive consumption — minimize required clicks to zero

Core Principles

#	Principle	Rationale
1	Freshness first	Visible last-updated + staleness flag; stale data is worse than no data
2	Thresholds ARE the design	Explicit good / warn / bad bands on every metric
3	Exceptions bubble up	Sort by severity desc, never alphabetical
4	Density fine, decoration not	Pack information tightly; strip all chrome
5	Alerts paged, not dashboarded	Dashboard shows state; PagerDuty / email sends notifications
6	State persists across refresh	No jarring re-render; viewer tracks delta
7	Four golden signals skeleton	Digital: latency / traffic / errors / saturation; Physical: throughput / queue / exception-rate / asset-health

Layout Variants

Pick ONE variant based on the operational context 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 operational context + brief)	Variant
Desk viewing (≤1.5 m), 4 golden signals, both surveillance and triage	A. 4-Up Status
Wallboard / TV-wall (≥3 m), peripheral surveillance, no detail expected on screen	B. Wallboard
Active incident response — exception queue is the working surface	C. Incident-First

Variant A — 4-Up Status (default, balanced surveillance + triage)

Status tiles, hero time series, and an exception detail row. Optimized for a desk monitor where the operator both surveilles and works the queue.

┌──────────────────────────────────────────────────────────┐
│  ENV / REGION selectors    LAST UPDATED: 14:32 UTC  ⚠️   │  h=56
├──────────┬──────────┬──────────┬──────────────────────────┤
│ STATUS 1 │ STATUS 2 │ STATUS 3 │ STATUS 4                 │  h=120
│ ████░░░  │ ████████ │ ███░░░░  │ █████░░                  │  bullet-style
├──────────┴──────────┴──────────┴──────────────────────────┤
│  HERO TIME SERIES — shared X axis — 24 h window           │  h=280
│  ┌─latency──┐ ┌─traffic──┐ ┌─errors───┐ ┌─saturation─┐  │
│  │  ~∿~∿~   │ │  ~∿~∿~   │ │  ~∿~∿~   │ │  ~∿~∿~     │  │
│  └──────────┘ └──────────┘ └──────────┘ └────────────┘  │
├──────────────────────────────┬────────────────────────────┤
│  EXCEPTION QUEUE             │  GEO / TOPOLOGY MAP        │  h=240
│  (table, severity desc)      │  (filled / shape / azure)  │
├──────────────────────────────┴────────────────────────────┤
│  source · cadence: 30 s · runbook: link                   │  h=24
└──────────────────────────────────────────────────────────┘

Zone	Height	Content
Header	56 px	Environment selector, last-updated, staleness icon
Status tiles	120 px	4 bullet-graph-style indicators
Hero time series	280 px	24 h window, shared X axis, 4 golden signals
Detail row	240 px	Exception queue + geo/topology map
Footer	24 px	Source, refresh cadence, runbook link

Variant B — Wallboard (TV-wall surveillance)

Two composite status tiles dominate the screen. No detail row. Designed to be readable from across a room — peripheral attention catches state changes without the operator looking directly at the screen. These are not bare one-measure cards; each primary tile needs state color, threshold/reference context, and a sparkline or banded status cue.

┌──────────────────────────────────────────────────────────┐
│   ENV    LAST UPDATED: 14:32 UTC                     ⚠️  │  h=64
├──────────────────────────────┬───────────────────────────┤
│                              │                           │
│   PRIMARY HEALTH             │   PRIMARY VOLUME          │
│   (huge value + status        │   (huge value + sparkline │
│    color + threshold band)   │    + threshold band)      │  h=440
│                              │                           │
│   FONT: 72-96pt               │   FONT: 72-96pt           │
│                              │                           │
├──────────┬──────────┬────────┴───────┬───────────────────┤
│ Sub 1    │ Sub 2    │ Sub 3          │ Sub 4             │  h=160
│ (med)    │ (med)    │ (med)          │ (med)             │
├──────────┴──────────┴────────────────┴───────────────────┤
│  cadence: 30 s · last incident: 11:42                    │  h=32
└──────────────────────────────────────────────────────────┘

Zone	Height	Content
Header	64 px	Environment + last-updated, large font for room visibility
Primary tiles	440 px	2 composite status tiles: PRIMARY HEALTH, PRIMARY VOLUME — value font 72–96pt plus state/context cues
Sub tiles	160 px	4 secondary indicators, font ~36pt
Footer	32 px	Refresh cadence + last-incident timestamp

Dark wallpaper recommended — set page > background and wallpaper to a near-black fill so alert colors pop in peripheral vision. No exception table — wallboards aren't where you triage; they tell you to go look at the triage screen.

Variant C — Incident-First (queue dominant for active responders)

When the page is consumed by an on-call engineer working an active incident, the exception queue is the working surface. Status tiles shrink to a status strip.

┌──────────────────────────────────────────────────────────┐
│   STATUS STRIP — 4 mini-tiles (h=56)            ⚠️ stale │  h=56
├──────────────────────────────────────────────────────────┤
│                                                          │
│   EXCEPTION QUEUE — full width                           │  h=400
│   ┌─severity─┬──when──┬──what──┬──where──┬──action──┐   │
│   │ Critical │ 2 m ago│ ...    │ region1 │ runbook→ │   │
│   │ Critical │ 4 m ago│ ...    │ region2 │ runbook→ │   │
│   │ Warning  │ 8 m ago│ ...    │ region1 │ runbook→ │   │
│   └──────────┴────────┴────────┴─────────┴──────────┘   │
├──────────────────────────────┬───────────────────────────┤
│  AFFECTED-ENTITY TIMELINE    │  RECENT DEPLOYS / CHANGES │  h=200
│  (sparkline grid for         │  (table, deploy events    │
│   selected entity)           │   correlated to incidents)│
├──────────────────────────────┴───────────────────────────┤
│  cadence: 30 s · runbook root: link                      │  h=24
└──────────────────────────────────────────────────────────┘

Zone	Height	Content
Status strip	56 px	4 compact tiles + staleness flag — context, not the focus
Exception queue	400 px	Full-width table sorted severity desc; columns: severity, when, what, where, action link
Correlation row	200 px	Affected-entity timeline + recent-deploys / change events
Footer	24 px	Cadence + runbook root link

The queue ROW must be selectable, and selecting a row should cross-filter the correlation row below — that's the whole interaction model. Configure actionButton per row (or a column with Web URL action) to jump straight to the runbook.

Chart Selection

Use

Visual type	Role	Notes
Bullet graph (simulated)	Status tile	`barChart` + `referenceLine` + banded `basicShape` behind
`lineChart` sparkline	Inline trends in tables	120 × 40, all chrome off
Status tile	KPI state	`cardVisual` + `shape` + icon; CF drives color
Heat strip	Time × entity state	`matrix` with background CF, suppress numbers
Exception table	Alert queue	`tableEx` with CF icons + data bars, sort severity desc
Maps	Spatial state	`azureMap` preferred. If Azure Maps cannot render the geography because of tenant policy, region support, or environment constraints, use a non-map fallback such as a `tableEx` of locations with conditional formatting or a `clusteredBarChart` by region. Avoid the legacy `map` / `filledMap` visuals; `shapeMap` is a specialized shape-based visual, not a general Azure Maps substitute.

Do NOT Use

Visual type	Reason
`pieChart` / `donutChart`	Cannot show deviation; no threshold encoding
`scatterChart`	Requires analytical attention; wrong mode
`treemap`	Area encoding unreliable at glance
Analytical slicers	Operators don't slice; they surveille
`decompositionTree`	Analytical, not operational

Color & Typography

Semaphore Palette

State	Color	Hex	Shape	Icon
Good	Green	`#107C10`	●	✓
Warning	Amber	`#FF8C00`	◐	◐
Critical	Red	`#D13438`	▲	▲
Unknown / stale	Grey	`#797775`	○	?

WCAG 1.4.1: Never encode state with color alone — always pair with shape + icon.

Saturated reds: Use calibrated, vivid reds for critical. Pastels fail to trigger peripheral attention.

Typography by Viewing Distance

Context	Body	Tile headline	Card value	Axis labels
Laptop (0.5 m)	14 pt	18 pt	24 pt	10 pt
TV wall (3 m)	18 pt	24 pt	36 pt	14 pt

Dark background advisory: NOC/control-room screens benefit from dark wallpaper (reduces bloom, makes alert colors pop). Not the default — configure via page > background and wallpaper.

Freshness & Refresh

Mechanism	PBI property	Constraint
Auto page refresh	`autoPageRefreshInterval`	DirectQuery only; Premium 1 s min, shared 30 min
Change-detection refresh	`changeDetection`	Fires refresh only when upstream data changes
Last-updated display	`MAX(timestamp)` measure or `NOW()`	Show prominently in header
Stale-flag CF	Conditional formatting rule	Flag when elapsed > 2× expected cadence

Staleness Decision Table

Expected cadence	Stale threshold	Action
Real-time (≤ 5 s)	> 15 s	Amber icon + "Data may be stale"
Near-real-time (30 s)	> 90 s	Red icon + suppress KPI values
Batch (hourly)	> 3 h	Grey overlay + "Awaiting refresh"

Interaction Design

Pattern	Implementation	Notes
Mostly passive	No required clicks in normal operation	—
Page tooltip on status tile	24 h sparkline + threshold bands	320 × 240 tooltip page
Drill-through on red tile	Detail page with timeline + runbook	One click from anomaly to root cause
Shift bookmarks	Day / night context	Adjusts thresholds + background
Cross-highlight	Subtle; never rearranges layout	Avoid disorienting the peripheral viewer

Anti-patterns: see references/design/anti-patterns.md

PBI Formatting Reference

Status Tiles

Property path	Value	Purpose
`cardVisual` background CF	Green / amber / red fill	State encoding
`shape` (backing plate)	Rectangle behind card	Colored status indicator
`visualHeader > show`	`false`	Clean tile surface

Time Series

Property path	Value	Purpose
`lineChart > categoryAxis > axisType`	`DateTime`	Continuous time axis
`referenceLine` / `constantLine`	SLO threshold values	Draw good / warn / bad bands
Shared X axis	Align all charts to same 24 h window	Visual correlation

Exception Table

Property path	Value	Purpose
`tableEx` CF icons	Severity icon set	Visual severity ranking
`tableEx` data bars	Metric magnitude	Quick magnitude scan
Sort	Severity desc	Worst-first ordering

Refresh & Page

Property path	Value	Purpose
`autoPageRefreshInterval`	Per data source cadence	Live refresh (DQ/Premium)
`changeDetection`	`true`	Efficient refresh trigger
`page > background`	Optional dark fill	NOC screen optimization
`page > wallpaper`	Optional dark fill	NOC screen optimization
`border > show`	`false`	Clean tile boundaries

Decision Checklist

#	Check	Pass?
1	Last-updated timestamp is visible and prominent	☐
2	Staleness flag fires when data exceeds expected cadence	☐
3	Every metric has explicit good / warn / bad thresholds	☐
4	State encoded with color + shape + icon (never color alone)	☐
5	Exception list sorted by severity desc	☐
6	Four golden signals represented	☐
7	Font sizes calibrated for actual viewing distance	☐
8	Zero clicks required for normal-state assessment	☐
9	Drill-through from red tile to detail + runbook	☐

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