microsoft/skills-for-fabric

powerbi-report-cli

Separa el trabajo de Power BI en planificación, diseño, edición local PBIR/PBIP y gestión independiente de Fabric.

Ver código fuente

Descripción detallada

Este Skill distribuye el trabajo sobre el informe entre planificación, diseño, autoría y gestión, cada uno con sus referencias. Para un informe nuevo, planificación convierte los requisitos y el contexto del modelo en una especificación que debe aprobarse antes de implementar; diseño fija el contrato visual. Un cambio concreto en un informe local existente puede ir directamente a autoría.

Autoría modifica páginas, objetos visuales, filtros y temas PBIR/PBIP. La finalización documentada combina validación del esquema, carga de los archivos recientes, capturas de las páginas afectadas y revisión visual. Gestión mueve las definiciones y administra los elementos de informe en Fabric por separado. Una vista previa no publica, y editar en local no autoriza sobrescribir un informe remoto.

El paquete aporta instrucciones, no un entorno Power BI preparado ni permisos de Fabric. La edición requiere el proyecto y contexto del modelo; el transporte documentado utiliza Azure CLI y powerbi-report-author. Las medidas, DAX y los cambios del modelo semántico corresponden a otro flujo; las preguntas en lenguaje natural sobre datos se derivan a fabriciq.

Qué preparar

  • Una tarea concreta: planificar, definir el diseño, editar un informe existente o gestionar un elemento de Fabric.
  • El proyecto PBIR/PBIP correcto y el contexto de tablas, columnas y medidas; para vista previa, el host elegido y los identificadores de enlace.
  • Para gestión remota, acceso autenticado a Fabric, identificadores exactos de espacio, informe y modelo, y herramientas requeridas.

Resultados esperados

  • Planificación entrega una especificación; diseño, un documento visual; autoría, archivos locales con comprobación de estructura y apariencia.
  • Gestión realiza la operación solicitada en Fabric, espera su finalización y verifica mediante lectura posterior, según acceso y autorización.

Cómo utilizarlo

  1. Elige el modo más específico por intención y lee toda su referencia y las continuaciones indicadas.
  2. En informes nuevos, termina y aprueba la especificación antes del diseño e implementación; conserva el trabajo existente.
  3. Edita por bloques lógicos, valida el esquema, carga los archivos recientes y revisa capturas de todas las páginas afectadas.
  4. Pasa a gestión solo para una operación remota solicitada expresamente; verifica el destino y la definición resultante.

Límites y comprobaciones

  • Instalar las instrucciones no instala todos los CLI ni prepara el host, y tampoco concede permisos de inquilino o espacio.
  • Un esquema válido no descarta una vista antigua, objetos sin enlace a datos o una disposición incorrecta.
  • Resuelve los cambios sin guardar del host antes de cargar archivos; una captura antigua no demuestra una edición nueva.
  • La referencia de gestión exige PBIR moderno y powerbi-report-author ≥0.3.0; comprueba definition/report.json y valida antes de empaquetar.
  • Separa medidas y DAX en el flujo del modelo; aprobar una edición o vista previa no autoriza sobrescribir el informe remoto.

Preguntas frecuentes

¿Necesito cuatro Skills distintos?

powerbi-report-cli contiene cuatro modos. Selecciona por tarea y lee su referencia; no todos los cambios pequeños necesitan las cuatro fases.

¿Responde preguntas sobre los datos?

Su alcance principal es el informe como artefacto. Deriva las preguntas de datos a fabriciq y los cambios del modelo o de DAX a un Skill de modelo semántico.

¿Basta con validar correctamente?

No. Autoría también exige cargar el PBIR editado y revisar capturas recientes de todas las páginas afectadas. Un cambio global requiere revisión del informe completo.

¿Editar publica automáticamente en Fabric?

Autoría conserva los cambios localmente. Gestión remota requiere destino, autenticación y permisos propios; la fuente exige autorización expresa para publicar y sobrescribir.

Instalar este Skill

Añade este Skill desde su fuente verificada en GitHub con la Skills CLI.

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

Información de la fuente

Documento original del Skill

Contenido del repositorio de origen con títulos, ejemplos, código, tablas, enlaces e imágenes preservados.

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

Relacionados por tarea

del mismo repositorio

Más Skills

Todos los Skills
microsoft
Oficial

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.

Instalaciones / 1h
1
GitHub Stars
1,3 mil
Actualizado
5 nov
microsoft
Oficial

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.

Instalaciones / 1h
1
GitHub Stars
1,3 mil
Actualizado
5 nov
microsoft
Oficial

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.

Instalaciones / 1h
1
GitHub Stars
1,3 mil
Actualizado
5 nov
microsoft
Oficial

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.

Instalaciones / 1h
1
GitHub Stars
1,3 mil
Actualizado
5 oct