AutoGineer
Generated banner for Powerbi Report CLI
Generated logo for Powerbi Report CLI

Powerbi Report CLI

MicrosoftOfficialPublished by Microsoft

  • Skill
  • Tool integration
  • Data and AI
  • MIT
  • Low risk
Download ZIP

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

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/microsoft/powerbi-report-cli/download

  2. 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

  1. To find workspace details, including its ID, from a workspace name: list all workspaces, then use JMESPath filtering.

  2. To find item details, including its ID, from a workspace ID, item type, and item name: list all items of that type in that workspace, then use JMESPath filtering.

  3. Use powerbi-report-cli for the report artifact: requirements, design, PBIR/PBIP page and visual edits, preview, and publishing. Semantic model, measure, and DAX work belongs to a semantic-model skill. Natural-language questions about report data belong to fabriciq.

Power BI Reports - CLI Skill

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

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

Mode Selection

ModeUse when the request...Existing route examplesRead first
planningcreates a new report/dashboard and needs requirements, model/dependency inspection, scope, a page plan, and approval before implementationcreate a report, build a dashboard, create from a semantic model, plan then implement, walk me through creating a reportreferences/planning.md, then references/planning-part-02.md
designdecides what a report should look like: tone, signature, page archetype, chart type, layout, color, typography, theme direction, accessibility, brand application, redesign, or critiquedesign a Power BI report, make the dashboard professional, choose a chart, apply a brand, redesign the report, create a design briefreferences/design.md
authoringreads or edits local PBIR/PBIP files, validates them, previews the report, or captures screenshotsedit PBIR, create/add a report page or visual, format a visual, add filters/slicers/bookmarks/themes, validate PBIR, preview/reload/screenshot in Desktop or servicereferences/authoring.md
managementmoves a report definition to or from Fabric or manages the workspace report itempublish/upload/download PBIR or PBIP, list reports, get/update/delete a report, rebind a reportreferences/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

ModeCompletion requirement
planningPersist _brief/report-spec.md or the user-named equivalent, ask for explicit approval, and stop before implementation.
designProduce 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.
authoringPersist 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.
managementComplete 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.

<!-- BEGIN GENERATED REFERENCE INDEX -->

Complete Reference Index

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

Authoring
Design
Mode Guides

<!-- END GENERATED REFERENCE INDEX -->

Examples

User requestMode
"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:

ModePreserved route phrases
planningcreate 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
designdesign Power BI report; make dashboard look professional; choose chart type; apply brand to report; redesign report; create design brief; Power BI report design archetype
authoringedit 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
managementupload 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

references/authoring/slicers-part-02.md

Slicer Authoring Guide - Part 2

Contents

  • Calendar Date Picker Templates

  • Date Between Slicer Template

  • Add/Modify a Slicer

    • Slicer types

    • Setting slicer selections

  • Slicer Sync Groups

  • Theme Approach

  • Discovering Properties

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

Calendar Date Picker Templates

Bind exactly one renderable Date/DateTime column to Values.

Use RelativeDatePicker for the calendar-style Date Picker. It supports two selection methods:

  • Manual — select an explicit start and end date on the calendar. Author either an unselected state or a fixed preselected range.

  • Relative — select a rolling range such as Last 30 Days or Last 13 Years.

Keep data.mode set to RelativeDatePicker for both methods. The stored properties and filter expression determine the active selection method and value. Do not substitute Between or Relative; those values author different compact slicer styles without the two-tab Date Picker UI.

Resolve the date field and preselection

Delegate semantic-model discovery to the semantic-model authoring skill or available modeling MCP server. Ask it to return a renderable Date/DateTime column and the exact table/column identity needed by the report query. For a fixed Manual preselection, also request the live minimum and maximum nonblank dates; for a Relative preselection, provide the requested business period so the model workflow can confirm that it intersects available data.

Use the verified field identity and date values returned by that capability in the report templates below; semantic-model inspection and DAX-query procedures remain owned by the semantic-model capability. If no model capability is available, author the unselected Manual state or ask the user to provide the date field and intended range.

Start from the base slicer template and set:

"data": [{
  "properties": {
    "mode": { "expr": { "Literal": { "Value": "'RelativeDatePicker'" } } }
  }
}]
Manual

Omit general.filter, data.startDate, and data.endDate to author Manual with no preselection.

To author Manual with a fixed inclusive range, add matching startDate and endDate literals to the data entry and add a matching general.filter. Encode the exclusive filter upper bound as the day after endDate:

"data": [{
  "properties": {
    "mode": { "expr": { "Literal": { "Value": "'RelativeDatePicker'" } } },
    "startDate": { "expr": { "Literal": { "Value": "datetime'2014-01-01T00:00:00'" } } },
    "endDate": { "expr": { "Literal": { "Value": "datetime'2014-06-30T00:00:00'" } } }
  }
}],
"general": [{
  "properties": {
    "filter": {
      "filter": {
        "Version": 2,
        "From": [{ "Name": "d", "Entity": "<table>", "Type": 0 }],
        "Where": [{
          "Condition": {
            "And": {
              "Left": {
                "Comparison": {
                  "ComparisonKind": 2,
                  "Left": {
                    "Column": {
                      "Expression": { "SourceRef": { "Source": "d" } },
                      "Property": "<date_column>"
                    }
                  },
                  "Right": { "Literal": { "Value": "datetime'2014-01-01T00:00:00'" } }
                }
              },
              "Right": {
                "Comparison": {
                  "ComparisonKind": 3,
                  "Left": {
                    "Column": {
                      "Expression": { "SourceRef": { "Source": "d" } },
                      "Property": "<date_column>"
                    }
                  },
                  "Right": { "Literal": { "Value": "datetime'2014-07-01T00:00:00'" } }
                }
              }
            }
          }
        }]
      }
    }
  }
}]
Relative

To author Relative with a preselection, keep mode: 'RelativeDatePicker', add the relative controls to data, add dateRange.includeToday, and add a matching relative general.filter. Keep relativeDuration and the negative DateAdd amount synchronized. Set that negative DateAdd.TimeUnit to the selected period, but keep both enclosing DateSpan.TimeUnit values at 0:

"data": [{
  "properties": {
    "mode": { "expr": { "Literal": { "Value": "'RelativeDatePicker'" } } },
    "relativeRange": { "expr": { "Literal": { "Value": "'Last'" } } },
    "relativePeriod": { "expr": { "Literal": { "Value": "'Days'" } } },
    "relativeDuration": { "expr": { "Literal": { "Value": "30D" } } }
  }
}],
"dateRange": [{
  "properties": {
    "includeToday": { "expr": { "Literal": { "Value": "true" } } }
  }
}],
"general": [{
  "properties": {
    "filter": {
      "filter": {
        "Version": 2,
        "From": [{ "Name": "d", "Entity": "<table>", "Type": 0 }],
        "Where": [{
          "Condition": {
            "Between": {
              "Expression": {
                "Column": {
                  "Expression": { "SourceRef": { "Source": "d" } },
                  "Property": "<date_column>"
                }
              },
              "LowerBound": {
                "DateSpan": {
                  "Expression": {
                    "DateAdd": {
                      "Expression": {
                        "DateAdd": {
                          "Expression": { "Now": {} },
                          "Amount": 1,
                          "TimeUnit": 0
                        }
                      },
                      "Amount": -30,
                      "TimeUnit": 0
                    }
                  },
                  "TimeUnit": 0
                }
              },
              "UpperBound": {
                "DateSpan": {
                  "Expression": { "Now": {} },
                  "TimeUnit": 0
                }
              }
            }
          }
        }]
      }
    }
  }
}]

For the negative DateAdd, use TimeUnit 0 for days, 1 for weeks, 2 for months, and 3 for years. Set relativePeriod to the matching Days, Weeks, Months, or Years value. Do not apply that period unit to DateSpan.TimeUnit; Desktop stores both DateSpan wrappers with value 0. Use the relative-filter expression variants in filters.md § Relative Date/Time filter (see filters.md, section relative-datetime-filter) for other periods and directions.

Size RelativeDatePicker at w >= 280, h >= 240.

Date Between Slicer Template

Use the slicer visual in Between mode only when users need arbitrary date-range exploration and the bound field is a renderable Date/DateTime column. For executive dashboards or annual/quarterly grain, prefer a compact Year/Period dropdown or tile.

{
  "$schema": "https://developer.microsoft.com/json-schemas/fabric/item/report/definition/visualContainer/2.9.0/schema.json",
  "name": "<unique-id>",
  "position": { "x": 1040, "y": 8, "z": 1000, "height": 104, "width": 216, "tabOrder": 1000 },
  "visual": {
    "visualType": "slicer",
    "query": {
      "queryState": {
        "Values": {
          "projections": [{
            "field": { "Column": { "Expression": { "SourceRef": { "Entity": "<table>" } }, "Property": "<date_column>" } },
            "queryRef": "<table>.<date_column>",
            "nativeQueryRef": "<date_column>"
          }]
        }
      }
    },
    "objects": {
      "data": [{ "properties": { "mode": { "expr": { "Literal": { "Value": "'Between'" } } } } }],
      "header": [{ "properties": {
        "show": { "expr": { "Literal": { "Value": "true" } } },
        "text": { "expr": { "Literal": { "Value": "'Date Range'" } } }
      }}]
    },
    "visualContainerObjects": {
      "padding": [{ "properties": {
        "top":    { "expr": { "Literal": { "Value": "8D" } } },
        "bottom": { "expr": { "Literal": { "Value": "8D" } } },
        "left":   { "expr": { "Literal": { "Value": "8D" } } },
        "right":  { "expr": { "Literal": { "Value": "8D" } } }
      }}]
    }
  }
}

Sizing:

  • Compact: w=216, h = 84 + top + bottom — dates stack vertically. With theme default 8/8 padding, snap 100 up to the 8px grid and use h=104.

  • Wider layouts may render dates side-by-side. Do not assume a fixed threshold; validate the target Desktop build by screenshot and use h = 60 + top + bottom only after both inputs visibly share one row.

Fill and light variants are the same as the dropdown slicer (see above).

Add/Modify a Slicer

Slicer types
TypevisualTypeQuery rolesdata.modeNotes
DropdownslicerValues only (Column/Hierarchy)'Dropdown'Any cardinality, compact; default for executive Year/Period filters
Date PickerslicerValues only (Date/DateTime column)'RelativeDatePicker'Calendar-style picker; supports Manual and Relative selection
Compact date rangeslicerValues only (Date/DateTime column)'Between'Side-by-side or stacked date bounds without the calendar picker
SingleslicerValues only (Column)'Single'Single-select
BeforeslicerValues only (Date/Numeric)'Before'Upper bound only (≤)
AfterslicerValues only (Date/Numeric)'After'Lower bound only (≥)
Relative date controlslicerValues only (Date column)'Relative'Compact "Last N days/months/years" control; use RelativeDatePicker when the calendar-style picker is required
Relative timeslicerValues only (DateTime column)'RelativeTime'"Last N minutes/hours" — uses data.relativeTimePeriod instead of relativePeriod
Scrollable listlistSlicerValues (Column/Hierarchy), Tooltips (Measure/Aggregation)—Default for list-style slicers. data.mode not available.
Button/tileadvancedSlicerVisualValues (1 Column only), Label (1 Measure, optional), Tooltips (Aggregations)—≤10 values, tile layout. data.mode not available.

Temporal decision matrix:

SignalUse
Executive page, annual grain, ≤10 yearsYear dropdown or year tile
Discrete period comparison (e.g., 2020 vs 2023)Year/month dropdown with multi-select
Month/quarter reporting with 12-36 periodsPeriod dropdown or relative date
Calendar-based day/month range exploration on Date/DateTime fieldRelativeDatePicker
Compact lower/upper date boundsBetween
Integer/text date key or date picker does not renderYear/Period dropdown

Constraints:

  • data.mode is only available on the classic slicer visual — not on listSlicer or advancedSlicerVisual.

  • advancedSlicerVisual allows only one field in Values.

  • Hierarchy slicers: only slicer (mode: Basic/Dropdown) and listSlicer support hierarchies. Add expansionStates for expanded nodes (see expressions.md).

  • A full-date column does not automatically require a Date Picker. Use a Year/Period dropdown or tile for annual/quarterly executive pages, RelativeDatePicker for calendar-based exploration, and Between for compact lower/upper bounds.

Setting slicer selections

The general.filter property in objects controls which values are selected. This is only needed when pre-selecting specific values — omit it entirely for the default "All" state.

"general": [{
  "properties": {
    "orientation": { "expr": { "Literal": { "Value": "0D" } } },
    "filter": {
      "filter": {
        "Version": 2,
        "From": [
          { "Name": "d", "Entity": "dim_company", "Type": 0 }
        ],
        "Where": [{
          "Condition": { /* filter expression — see expressions.md */ },
          "Annotations": {
            "filterExpressionMetadata": {
              "expressions": [{ /* Column Expression for the filtered field */ }],
              "decomposedIdentities": {
                "values": [[
                  { "0": [{ "Literal": { "Value": "'A. Datum'" } }] },
                  { "1": [{ "Literal": { "Value": "'N'" } }] },
                  { "2": [{ "Literal": { "Value": "5L" } }] },
                  { "3": [{ "Literal": { "Value": "'A. Datum'" } }] }
                ]],
                "columns": [{ "value": { /* Column Expression — grouping key */ } }]
              },
              "valueMap": [{ "0": "A. Datum", "1": "N", "2": "5", "3": "A. Datum" }]
            }
          }
        }]
      }
    }
  }
}]

  • decomposedIdentities.values — the actual selected values as literals

  • decomposedIdentities.columns — the grouping key columns

  • valueMap — maps indices in decomposedIdentities to queryRef values

  • expansionStates — only needed for hierarchy slicers when nodes are expanded; identityKeys defined on the first level only, identityValues inside root.children[] only when a specific node has been toggled open

  • Literal format: strings use single quotes inside double quotes ("Value": "'A. Datum'"); numbers use type suffixes ("Value": "5L").

Slicer Sync Groups

Slicers can be synced across pages so that changing a selection on one page applies to all other pages with slicers in the same sync group. Add syncGroup inside the visual object (sibling of visualType, query, objects):

{
  "visual": {
    "visualType": "slicer",
    "syncGroup": {
      "groupName": "DateSync",
      "fieldChanges": true,
      "filterChanges": true
    },
    "query": { /* ... */ },
    "objects": { /* ... */ }
  }
}
PropertyTypeDescription
groupNamestringUnique name for the sync group. Slicers with the same groupName across pages are synced.
fieldChangesbooleanWhen true, field/projection changes propagate to all group members.
filterChangesbooleanWhen true, filter/selection changes propagate to all group members.

Rules:

  • All slicers in the same sync group must have the same visualType and bound column. Slicers of the same type that produce the same filter expressions can be in the same group — e.g. two slicer visuals both bound to Date.Date with mode 'Between'.

  • Set the same groupName on each slicer you want synced (e.g. "DateSync"; any unique string works).

  • Typically set both fieldChanges: true and filterChanges: true.

Note: The published PBIR JSON schemas (visualContainer/2.5.0–2.9.0) do not list syncGroup. However, the internal schema (visualConfiguration/9999.0.0) does include it with full type definition. Desktop reads and writes it correctly.

Theme Approach

These slicer defaults are applied report-wide via theme visualStyles (plain JSON, not PBIR expr wrappers):

"slicer": {
  "*": {
    "header": [{
      "fontFamily": "Segoe UI Semibold",
      "textSize": 10,
      "fontColor": { "solid": { "color": "#252423" } },
      "outlineStyle": 0
    }],
    "items": [{
      "fontFamily": "Segoe UI Variable, Segoe UI, sans-serif",
      "textSize": 9,
      "fontColor": { "solid": { "color": "#252423" } },
      "outlineStyle": 0,
      "padding": 2
    }]
  }
}

The global *.* wildcard also provides: border (#E8E8E8, radius=8), hidden visual header, and VCO padding (8px). Per the VCO override caveat, this *.*.padding cascade is dropped the moment a slicer sets any per-visual VCO, so every slicer template must redeclare padding explicitly — 8/8/8/8 to match the theme for normal slicers, or 0/0/0/0 for the fill variant (so the white fill reaches the container edges).

header.text does NOT usefully cascade from theme — it would set the same name on every slicer. Always set per-visual.

Discovering Properties

# List all formatting objects for a slicer type
powerbi-report-author formatting list-objects slicer
powerbi-report-author formatting list-objects advancedSlicerVisual
powerbi-report-author formatting list-objects listSlicer

# Inspect specific objects
powerbi-report-author formatting describe-object slicer header
powerbi-report-author formatting describe-object slicer items
powerbi-report-author formatting describe-object slicer data
powerbi-report-author formatting describe-object slicer selection

# Search across all objects
powerbi-report-author formatting search slicer "font|text|padding"

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