microsoft/skills-for-fabric

powerbi-report-cli

把 Power BI 报表工作分为规划、设计、本地 PBIR/PBIP 编辑和独立的 Fabric 管理。

查看源码

详细说明

这份 Skill 负责报表文件这一层,入口会把任务交给规划、设计、编写和管理四种模式及其详细参考。新报表先把需求与模型背景整理成规格,明确确认后再实施,设计模式负责视觉方案。已有本地报表的小范围修改可以直接进入编写模式,不必每次重走新建报表的完整流程。

编写模式处理 PBIR/PBIP 的页面、图表、筛选器、主题等改动。它要求结构校验之后继续加载最新文件、截图并逐页检查实际渲染;JSON 合法不等于图表已经正确。管理模式则独立负责向 Fabric 传输定义和操作报表项目。打开预览不等于发布,本地编辑也不代表获准覆盖远程报表。

这个包提供操作说明,不会自动配齐 Power BI 环境或授予 Fabric 权限。本地编辑需要对应项目和模型字段背景,文档中的传输流程还依赖 Azure CLI 与 powerbi-report-author。度量值、DAX 和语义模型修改应交给配套语义模型流程;直接向数据提问则由入口转给 fabriciq。

需要准备什么

  • 明确任务:新建规划、制定视觉方案、修改已有报表,或管理 Fabric 报表项目。
  • 本地编辑需准确的 PBIR/PBIP 项目及表、列、度量值背景;预览需选定宿主和相应绑定 ID。
  • 远程管理需有效的 Fabric 身份、准确工作区/报表/模型标识,以及参考文档要求的工具。

可以得到什么

  • 规划交付报表规格,设计交付视觉设计说明,编写交付经过结构与视觉检查的本地报表文件。
  • 管理在权限与确认条件满足后执行指定 Fabric 报表操作,并轮询完成状态、回读验证结果。

使用步骤

  1. 按意图选择最小适用模式,完整阅读该模式参考及它明确指向的后续部分。
  2. 新建报表先完成并确认规格,再进入设计与实施,同时保护已有本地工作。
  3. 本地编写按逻辑批次修改,校验结构,加载最新文件,并检查所有受影响页面的截图。
  4. 只有明确需要远程操作时才进入管理模式,核对准确目标,并验证操作后的报表定义。

限制与检查

  • 安装说明包不等于已经安装全部 CLI、准备好预览宿主,或拥有租户与工作区权限。
  • 结构校验通过后,还要排除预览过期、图表没有数据绑定、布局渲染错误等问题。
  • 加载新文件前先处理预览宿主中的未保存修改,不用旧截图证明新改动正确。
  • 管理参考要求现代 PBIR 和 powerbi-report-author ≥0.3.0;打包前检查 definition/report.json 并完成校验。
  • 度量值、DAX 和模型修改走相应配套流程;同意本地编辑或预览,不等于同意覆盖远程报表。

常见问题

需要安装四份不同的 Skill 吗?

powerbi-report-cli 包内提供四种模式。按任务选模式并阅读相应参考;并不是每个小修改都必须走完四个阶段。

它能直接回答报表数据问题吗?

主要职责是报表文件。入口把数据问答转给 fabriciq,把模型或 DAX 修改转给语义模型 Skill。

校验成功就算完成了吗?

不算。编写参考还要求加载修改后的 PBIR,并检查所有受影响页面的新截图;主题等全局变更需要覆盖全报表。

本地修改会自动发布到 Fabric 吗?

编写模式保持本地修改。远程管理另需准确目标、认证与权限;来源还要求明确获得发布和覆盖远程报表的授权。

安装这个 Skill

通过 Skills CLI,从已验证的 GitHub 来源添加这个 Skill。

npx skills add https://github.com/microsoft/skills-for-fabric --skill powerbi-report-cli

来源信息

仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

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:

text
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

按任务相关推荐

来自同一仓库

更多 Skills

全部 Skills
microsoft
官方

databasehub-cli

Analyzes Database Hub inventory, health, and security posture through Entra-authenticated Fabric APIs. Use for estate counts; SQL/PostgreSQL CPU, storage, and memory; Cosmos DB availability/RU; authentication/auditing/CMK warnings; and Fabric SQL inventory. Fabric SQL tuning routes to sqldb-cli; Warehouse/Lakehouse/Mirrored Database SQL to sqldw-cli. Triggers: data estate performance, database estate health, database security posture.

1小时安装量
1
GitHub Stars
1325
最近更新
11月5日
microsoft
官方

e2e-fabric-cost-estimation

Estimates Fabric capacity cost before a migration by profiling Spark, SQL, Power BI, and Real-Time workloads, then recommending SKU size and comparing Reserved, Pay-As-You-Go, and Autoscale billing. Use only for capacity sizing and pricing questions, not for general migration or connectivity work.

1小时安装量
1
GitHub Stars
1325
最近更新
11月5日
microsoft
官方

onelake-catalog-cli

Governs and curates the Microsoft Fabric OneLake catalog through Fabric Admin, Core and Power BI REST APIs. Use for tenant or data-owner governance audits and guarded remediation of domains, workspace assignment, capacity, labels, tag definitions, workspace tags, certification, refresh and item identity, and for owners curating an item's description, name, tags and table and column descriptions. Item discovery belongs to search-consumption-cli.

1小时安装量
1
GitHub Stars
1325
最近更新
11月5日
microsoft
官方

eventschemaset-cli

Governs Event Schema Sets, the Fabric registries of event types and message payload schemas. Covers create, rename, update and delete of a definition, and listing, property reads or base64 decoding. Every Event Schema Set task belongs here. Ingestion pipelines are eventstream-cli.

1小时安装量
1
GitHub Stars
1264
最近更新
10月5日