Powerbi Report CLI — Agent Skill by Microsoft

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/typography.md

Typography for Data

Core Principles

Sans-serif for screens — Segoe UI is the PBI default; it renders cleanly at small sizes.
3–4 tiers maximum — More tiers create visual noise, not hierarchy.
Data-ink over label-ink — Numbers and chart marks dominate; text supports, never competes.
Align numbers when comparison matters — Use tabular-looking digits or right alignment for KPI rows, tables, axes, and labels where readers compare magnitudes.
Consistency across pages — Same role = same size, weight, and color everywhere.
WCAG floors — Use 9pt as the normal minimum for visible text; 8pt is only acceptable for non-critical captions/footnotes with strong contrast. Maintain 4.5:1 contrast ratio on background.
Weight before size — Differentiate tiers with weight changes first; increase size only when weight alone is insufficient.

Type Ramp

The 6-tier system below names conceptual roles (not theme keys). Power BI's primary textClasses are callout, title, header, and label; secondary classes derive from those primaries. Visual titles use the documented secondary class largeTitle, which derives from title. The other tiers (body-lg, body, caption) are sizing conventions the agent applies inline via fontSize overrides; they do NOT correspond to theme keys.

Tier	Role	Size (pt)	Weight	Line Height	Use	Theme key
H1	Page title	20	SemiBold 600	1.2×	Report header, page banner	`textClasses.title`
H2	Visual title	14	SemiBold 600	1.2×	Chart and table titles	`textClasses.largeTitle`
H3	KPI value	28–36	Bold 700	1.0×	Card callout numbers	`textClasses.callout`
body-lg	KPI label	11	Regular 400	1.3×	Card subtitle, section label	(none — set inline)
body	Axis, legend, labels	9–10	Regular 400	1.3×	Default body text in visuals	`textClasses.label`
caption	Footnote, timestamp	8–9	Regular 400	1.3×	Below visual, page footer	(none — set inline)

Scaling rule: each step ≈ 1.25–1.5× the previous. Never exceed 4 distinct sizes on one page.

Tone / Signature Overrides

The type ramp is the baseline. Tone and signature may override it when the identity depends on typography, but the override must be explicit in the Design Brief: and remain authorable in Power BI.

Override	Allowed scope	Guardrail
Serif display typography	Page titles, section headers, narrative annotations	Do not use serif for axis labels, data labels, matrix cells, or dense numeric text
Oversized editorial/display titles	H1/page banner or one hero text element	Treat 28–48pt as a tone-driven exception, not the default ramp
Monospace/tabular number treatment	KPI values, comparison tables, aligned numeric labels	Use only where alignment improves reading; do not make body text monospace unless that is the signature
All-caps headings	Page title, section label, or short chip text	Do not all-caps body copy, table values, or long chart titles
Caption-style annotations	Subtitles/annotations under visuals	Keep captions 8–9pt only when non-critical and high contrast; otherwise use 9–10pt

Power BI does not expose every CSS typography control. Treat requests like tabular-figure features, letter-spacing, and optical sizing as design intent; the authoring mode chooses the closest PBIR-authorable implementation.

Font Family Guidance

PBI's safest default is Segoe UI — it ships with the platform, renders consistently across Desktop / Service / mobile / embedded, and has wide glyph coverage. Use it as the baseline unless brand requirements or the design identity justify a display font.

Scenario	Font	Reason
Default — all text	Segoe UI	PBI native; good hinting; wide glyph coverage
Brand alternative	Brand sans-serif	Only when the brand standard mandates it; test at 9pt
Tight tabular columns	Segoe UI (or any tabular-numeral monospace fallback)	Avoid serif fonts — serifs collide in narrow cells
Monospace fallback	Consolas, Cascadia Code	Only when normal font digits do not align reliably

Custom font fallback caveat

Custom fonts can render differently across Desktop, Service, Mobile, and embedded reports. When using a custom font, provide a fallback chain such as 'BrandName, "Segoe UI", sans-serif'; for mission-critical reports, prefer Segoe UI to avoid silent font substitution.

Never use decorative or serif fonts for axis labels, data labels, or matrix cells.

Tabular Numerals & Number Formatting

Rule	Example	Why
Use tabular-looking or right-aligned numbers	`1,234` aligns with `9,876`	Columns scan vertically
Decimal-align currency	`$1,234.56` / `$ 987.00`	Right-align with consistent decimals
Thousands separators	`1,234,567` not `1234567`	Readability for 5+ digit numbers
Unit abbreviations	`$1.2M` not `$1,200,000`	Cards and axes; full precision in tooltips
Negative format	`(1,234)` or `−1,234`	Parentheses for finance; minus sign for general
Percentage decimals	`12.3%` (1 decimal)	0 decimals if ≥10%; 1 decimal if <10%
Date axis labels	`Jan`, `Feb` or `Q1 '24`	Abbreviate; full dates only in detail tables

Density & Readability

Guideline	Rule
Axis label truncation	Truncate with ellipsis (`…`) when label exceeds allocated width; full text in tooltip
Tick density	5–8 ticks per axis; more clutters, fewer loses reference
In-chart labels vs legend	Label directly on chart when ≤4 series; legend when >4
Minimum legible size	9pt preferred; 8pt only for non-critical captions/footnotes with strong contrast
Line spacing in cards	KPI value and label should have ≥4px vertical gap
Matrix row height	Minimum 20px per row for touch; 16px for dense desktop
Text wrapping	Avoid wrapping in axis labels and card values; wrap only in text boxes

Power BI Formatting Keys

Element	Key Path	Default
Visual title text	`title.fontSize`	12
Visual title weight	`title.bold`	true
Axis labels	`categoryAxis.fontSize` / `valueAxis.fontSize`	10
Data labels	`labels.fontSize`	9
Legend text	`legend.fontSize`	9
Card callout value	`calloutValue.fontSize`	27
Card category label	`categoryLabel.fontSize`	12
Table header	`columnHeaders.fontSize`	10
Table values	`values.fontSize`	9
Slicer header	`header.fontSize`	10
Slicer items	`items.fontSize`	10
Tooltip text	`default.fontSize` (tooltip visual)	10

Archetype Calibration

Archetype	H1	H2	H3 (KPI)	body	Notes
Executive	20pt SemiBold	14pt SemiBold	36pt Bold	10pt	Large KPI callouts; minimal body text
Operational	16pt SemiBold	12pt SemiBold	28pt Bold	9pt	Dense; prioritize scan speed
Analytical	16pt SemiBold	12pt SemiBold	—	9pt	No hero KPIs; axis labels matter most
Narrative	20pt SemiBold	14pt SemiBold	28pt Bold	11pt	More body text; slightly larger for reading
Comparative	16pt SemiBold	12pt SemiBold	—	9pt	Uniform sizing for fair comparison

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

Number Format Decision Table

Data Type	Format	Example	When
Currency (large)	`$#.#M` / `$#.#B`	`$4.2M`	Cards, axes, tooltips for millions+
Currency (exact)	`$#,##0.00`	`$1,234.56`	Tables, detail views
Percentage (large)	`#%`	`12%`	Cards, data labels when ≥1%
Percentage (small)	`#.#%`	`0.3%`	When precision matters, values <1%
Integer count	`#,##0`	`1,234`	Row counts, units sold
Decimal measure	`#,##0.0`	`98.7`	Scores, rates, indices
Date (axis)	`MMM 'YY`	`Jan '24`	Time axis labels
Date (detail)	`DD MMM YYYY`	`15 Jan 2024`	Table columns, tooltips
Duration	`#h #m` or `#.# hrs`	`2h 15m`	Time-based measures

Alignment Rules

Element	Horizontal Alignment	Vertical Alignment
Visual titles	Left	Top
Numbers in tables	Right	Center
Text in tables	Left	Center
Card KPI values	Center or Left	Center
Card labels	Center or Left (match value)	Below value
Axis labels	Auto (axis-aligned)	Auto
Data labels	Centered on mark or end-aligned	Auto
Page titles	Left	Top
Footnotes	Left	Bottom

Rule: Numbers always right-align so decimal points stack vertically. Text always left-aligns for readability.

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.

Matplotlib
K-Dense· Community
Creates and customizes scientific plots with Matplotlib. Used for fine-grained control over plot elements, novel plot types, and scientific workflows. Export to PNG/PDF/SVG for publication. For quick statistical plots use seaborn; for interactive plots use plotly; for publication-ready multi-panel figures with journal styling, use scientific-visualization.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskHas scriptsGitHub stars of the source repository56.4k
Seaborn
K-Dense· Community
A Python library for creating publication-quality statistical graphics with integrated pandas support.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskGitHub stars of the source repository56.4k
Kpi Dashboard Design
Seth Hobson· Community
A framework for designing effective, actionable KPI dashboards that drive business decisions through clear metrics and visualization best practices.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Power Bi Report Design Consultation
GitHubOfficial
A comprehensive framework for designing effective, accessible, and user-friendly Power BI reports.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository40.9k
Power Bi Visualization Expert
GitHubOfficial
Expert guidance for designing effective, performant, and accessible Power BI reports following Microsoft best practices.
Data and AIGitHub Copilot
MITGitHub stars of the source repository40.9k
Build Dashboard
AnthropicOfficial
Generate self-contained, interactive HTML dashboards featuring charts, filters, and data tables.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
Apache-2.0GitHub stars of the source repository35.1k

Download ZIP

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