詳しい説明
このSkillはレポート成果物の作業を振り分ける入口で、計画、設計、編集、管理に別々の参照文書があります。新規レポートでは要件とモデルの背景を仕様にまとめ、承認後に実装へ進みます。設計は見た目の契約を定めます。既存ローカルレポートの限定的な変更は編集モードへ直接進めるため、毎回新規作成の全工程を繰り返す必要はありません。
編集はPBIR/PBIPのページ、ビジュアル、フィルター、テーマなどを扱います。完了にはスキーマ検証に加え、最新ファイルの読み込み、影響ページの撮影、スクリーンショット確認が必要です。管理はFabricとの定義の送受信やレポート項目の操作を別に担当します。プレビューは公開ではなく、ローカル編集の承認もリモート上書きの承認にはなりません。
パッケージは手順を提供するもので、Power BI環境の準備やFabric権限の付与を自動で行うものではありません。編集には対象プロジェクトとモデル情報、記載の転送手順にはAzure CLIとpowerbi-report-authorが必要です。メジャー、DAX、セマンティックモデルの変更は別のモデル用手順、データへの自然言語質問はfabriciqが担当します。
用意するもの
- 新規計画、見た目の設計、既存編集、Fabric項目管理のどれを行うかという具体的な依頼。
- 編集対象のPBIR/PBIPとテーブル・列・メジャー情報。プレビューには選択したホストと必要なバインドID。
- 遠隔管理にはFabricの認証、正確なワークスペース・レポート・モデルIDと参照文書所定のツール。
得られるもの
- 計画はレポート仕様、設計はデザインブリーフ、編集は構造と表示を確認したローカルファイルを作成します。
- 管理は権限と承認条件の下で依頼されたFabric操作を行い、完了待ちと読み戻しで結果を確認します。
使い方
- 目的に合う最小のモードを選び、その全文と指定された続編を読みます。
- 新規作成では仕様の完成と承認後に設計・実装へ進み、既存作業を保護します。
- 編集は論理単位で変更し、検証、最新ファイルの読み込み、影響ページの画像確認を行います。
- 明示的な遠隔操作が必要な場合に管理へ移り、対象と操作後の定義を照合します。
制約と確認事項
- 手順の導入だけではCLI、プレビューホスト、テナントやワークスペース権限はそろいません。
- スキーマが正しくても、古いプレビュー、データ未接続のビジュアル、表示崩れは別途確認が必要です。
- ホストの未保存変更を解消してから新ファイルを読み込み、古い画像で新しい編集を検証しないでください。
- 管理参考はmodern PBIRとpowerbi-report-author ≥0.3.0を要求します。pack前にdefinition/report.jsonを確認し検証します。
- メジャーやDAXは適切なモデル用手順へ分けます。編集やプレビューの承認は遠隔上書きの承認ではありません。
よくある質問
四つのSkillが必要ですか?
powerbi-report-cliの中に四つのモードがあります。作業ごとに選び、対応参考を読みます。小さな編集にも四段階すべてが必須という意味ではありません。
レポートのデータについて質問できますか?
主対象はレポート成果物です。データ質問はfabriciqへ、モデルやDAXの変更はセマンティックモデルSkillへ振り分けられます。
検証成功だけで完成ですか?
いいえ。編集後のPBIRを読み込み、影響する全ページの新しい画像を確認する必要があります。テーマなど全体変更では全体を確認します。
編集すると自動公開されますか?
編集モードはローカルに留まります。遠隔管理には対象、認証、権限が別途必要で、原文は公開と上書きの明示的な承認も要求しています。
この Skill を導入
Skills CLI を使い、検証済みの GitHub ソースから追加します。
npx skills add https://github.com/microsoft/skills-for-fabric --skill powerbi-report-cli出典情報
- github.com/microsoft/skills-for-fabric/blob/4c3986d2e5b498ce2d6e6025533b94b5e5bb2ccd/skills/powerbi-report-cli/SKILL.md
- github.com/microsoft/skills-for-fabric/blob/4c3986d2e5b498ce2d6e6025533b94b5e5bb2ccd/skills/powerbi-report-cli/references/authoring.md
- github.com/microsoft/skills-for-fabric/blob/4c3986d2e5b498ce2d6e6025533b94b5e5bb2ccd/skills/powerbi-report-cli/references/management.md
見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。
Telemetry — MANDATORY. Everyapi.fabric.microsoft.comcall must carryx-ms-fabric-skill: powerbi-report-cli(az rest:--headers "x-ms-fabric-skill=powerbi-report-cli"), including every LRO poll,fabric_lroand 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. Usepowerbi-report-clifor 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 tofabriciq.
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.
designdecides what the report should look like;authoringwrites 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.
authoringchanges local files and performs preview/validation. It does not
publish to Fabric.
managementtransports definitions and manages Fabric report items. It does
not invent or directly author PBIR content.
planningowns 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 -> managementHandle 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 toapproval_pendingand keepplanningas the only active mode. In this phase, do not loadauthoringormanagement, 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>.mdend 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
planningmode, also readreferences/planning-part-02.mdbefore
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-authorCLI 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
planningordesign. - Publishing from
authoring, or authoring PBIR content frommanagement. - 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
- `authoring/authoring-workflows`
- `authoring/bookmark`
- `authoring/button-part-02`
- `authoring/button-part-03`
- `authoring/button`
- `authoring/card-part-02`
- `authoring/card-part-03`
- `authoring/card`
- `authoring/cartesian-part-02`
- `authoring/cartesian-part-03`
- `authoring/cartesian-part-04`
- `authoring/cartesian`
- `authoring/color-strategy`
- `authoring/conditional-formatting-part-02`
- `authoring/conditional-formatting-part-03`
- `authoring/conditional-formatting-part-04`
- `authoring/conditional-formatting-part-05`
- `authoring/conditional-formatting-part-06`
- `authoring/conditional-formatting-part-07`
- `authoring/conditional-formatting`
- `authoring/custom-visuals`
- `authoring/expressions`
- `authoring/field-parameters`
- `authoring/filter-pane`
- `authoring/filters`
- `authoring/formatting-overview`
- `authoring/formatting-part-02`
- `authoring/formatting`
- `authoring/image`
- `authoring/kpi`
- `authoring/map`
- `authoring/model-binding`
- `authoring/page-formatting`
- `authoring/powerbi-desktop`
- `authoring/powerbi-report-author-cli-part-02`
- `authoring/powerbi-report-author-cli`
- `authoring/preview-part-02`
- `authoring/preview-part-03`
- `authoring/preview-part-04`
- `authoring/preview`
- `authoring/re-theming-part-02`
- `authoring/re-theming-part-03`
- `authoring/re-theming`
- `authoring/screenshot-review`
- `authoring/shape`
- `authoring/slicers-part-02`
- `authoring/slicers`
- `authoring/table`
- `authoring/textbox`
- `authoring/theming-part-02`
- `authoring/theming`
- `authoring/version-control`
Design
- `design/accessibility`
- `design/anti-patterns`
- `design/archetype-composition`
- `design/archetypes/analytical-canvas`
- `design/archetypes/comparative-benchmark-part-02`
- `design/archetypes/comparative-benchmark`
- `design/archetypes/executive-summary`
- `design/archetypes/narrative-story`
- `design/archetypes/operational-monitor`
- `design/brownfield`
- `design/chart-selection`
- `design/color`
- `design/design-brief-part-02`
- `design/design-brief`
- `design/interactivity`
- `design/layout`
- `design/pre-flight-checklist`
- `design/signatures`
- `design/tone-catalog`
- `design/typography`
- `design/visual-cookbook-part-02`
- `design/visual-cookbook`
Mode Guides
- `authoring-part-02`
- `authoring-part-03`
- `authoring-part-04`
- `authoring`
- `design`
- `management-part-02`
- `management-part-03`
- `management-part-04`
- `management`
- `planning-part-02`
- `planning`
<!-- END GENERATED REFERENCE INDEX -->
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 |




