자세한 설명
이 Skill은 보고서 산출물 작업을 기획, 디자인, 작성, 관리로 분기하며 각 모드에 별도 참고 문서가 있습니다. 새 보고서의 기획은 요구 사항과 모델 배경을 명세로 정리하고 구현 전에 승인을 받습니다. 디자인은 시각적 기준을 정합니다. 기존 로컬 보고서의 작은 수정은 전체 신규 절차를 반복하지 않고 작성 모드로 바로 갈 수 있습니다.
작성 모드는 PBIR/PBIP 페이지, 시각화, 필터, 테마 등을 다룹니다. 문서상 완료 조건에는 스키마 검사뿐 아니라 최신 파일 로드, 영향받은 페이지 캡처와 이미지 검토가 포함됩니다. 관리 모드는 Fabric 정의 전송과 보고서 항목 조작을 따로 담당합니다. 미리 보기는 게시가 아니며, 로컬 수정 승인도 원격 덮어쓰기 승인이 아닙니다.
이 패키지는 지침을 제공하며 Power BI 환경이나 Fabric 권한을 자동으로 갖춰 주지는 않습니다. 편집에는 해당 프로젝트와 모델 맥락이 필요하고, 문서의 전송 절차에는 Azure CLI와 powerbi-report-author가 사용됩니다. 측정값, DAX, 의미 체계 모델 변경은 별도 모델 작업으로, 자연어 데이터 질문은 fabriciq로 보냅니다.
준비할 사항
- 새 보고서 기획, 디자인 결정, 기존 보고서 편집, Fabric 항목 관리 중 구체적인 작업.
- 편집할 정확한 PBIR/PBIP 프로젝트와 테이블·열·측정값 정보. 미리 보기에는 선택한 호스트와 필요한 바인딩 ID.
- 원격 관리에는 인증된 Fabric 접근, 정확한 작업 영역·보고서·모델 ID, 참고 문서가 요구하는 도구.
예상 결과
- 기획은 보고서 명세, 디자인은 시각적 설계 문서, 작성은 구조·화면을 확인한 로컬 보고서 파일을 만듭니다.
- 관리는 접근 권한과 승인 조건에 따라 요청한 Fabric 작업을 수행하고 완료 상태와 읽기 검증으로 결과를 확인합니다.
사용 순서
- 의도에 맞는 최소 모드를 고르고 해당 참고 문서 전체와 지정된 후속 부분을 읽습니다.
- 새 보고서는 명세를 완료하고 승인받은 뒤 디자인·구현으로 진행하며 기존 작업을 보존합니다.
- 논리적 단위로 편집하고 스키마 검사, 최신 파일 로드, 영향받은 모든 페이지의 캡처 검토를 수행합니다.
- 명시적으로 요청한 원격 작업일 때만 관리로 전환하고 정확한 대상과 작업 후 정의를 확인합니다.
제한 및 확인 사항
- 지침 설치만으로 모든 CLI, 미리 보기 호스트, 테넌트나 작업 영역 권한이 준비되지는 않습니다.
- 스키마가 유효해도 오래된 미리 보기, 데이터 바인딩 누락, 잘못된 레이아웃은 따로 확인해야 합니다.
- 새 파일 로드 전에 호스트의 저장하지 않은 변경을 해결하며, 예전 캡처로 새 편집을 검증하지 않습니다.
- 관리 참고 문서는 최신 구조의 PBIR와 powerbi-report-author ≥0.3.0을 요구합니다. pack 전에 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출처 정보
- 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 |




