Powerbi Report CLI
MicrosoftOfficialPublished by Microsoft
- Skill
- Tool integration
- Data and AI
- MIT
- Low risk
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
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/microsoft/powerbi-report-cli/downloadUnzip 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.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
To find workspace details, including its ID, from a workspace name: list all workspaces, then use JMESPath filtering.
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.
Use
powerbi-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 isdesign; encoding it intovisual.jsonisauthoring.Restyling or reformatting an existing local report is
authoring, even when the request uses design language. Usedesignwhen 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 toauthoring.
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 to
approval_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
Design
Mode Guides
<!-- 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 |
Files
- ATTRIBUTION.mdAdded by AutoGineer881 B
- LICENSELicence file added by AutoGineer1.1 KiB
- SKILL.md16.1 KiB
- apm.yml642 B
- references/authoring-part-02.md14.6 KiB
- references/authoring-part-03.md16.0 KiB
- references/authoring-part-04.md15.9 KiB
- references/authoring.md16.8 KiB
- references/authoring/authoring-workflows.md11.7 KiB
- references/authoring/bookmark.md14.3 KiB
- references/authoring/button-part-02.md16.1 KiB
- references/authoring/button-part-03.md7.7 KiB
- references/authoring/button.md15.7 KiB
- references/authoring/card-part-02.md16.1 KiB
- references/authoring/card-part-03.md8.6 KiB
- references/authoring/card.md6.4 KiB
- references/authoring/cartesian-part-02.md17.7 KiB
- references/authoring/cartesian-part-03.md12.3 KiB
- references/authoring/cartesian-part-04.md15.8 KiB
- references/authoring/cartesian.md18.0 KiB
- references/authoring/color-strategy.md8.4 KiB
- references/authoring/conditional-formatting-part-02.md13.5 KiB
- references/authoring/conditional-formatting-part-03.md16.0 KiB
- references/authoring/conditional-formatting-part-04.md14.0 KiB
- references/authoring/conditional-formatting-part-05.md16.9 KiB
- references/authoring/conditional-formatting-part-06.md14.7 KiB
- references/authoring/conditional-formatting-part-07.md14.5 KiB
- references/authoring/conditional-formatting.md18.2 KiB
- references/authoring/custom-visuals.md13.9 KiB
- references/authoring/expressions.md11.9 KiB
- references/authoring/field-parameters.md5.1 KiB
- references/authoring/filter-pane.md5.0 KiB
- references/authoring/filters.md9.3 KiB
- references/authoring/formatting-overview.md4.8 KiB
- references/authoring/formatting-part-02.md3.3 KiB
- references/authoring/formatting.md17.0 KiB
- references/authoring/image.md12.6 KiB
- references/authoring/kpi.md2.5 KiB
- references/authoring/map.md13.4 KiB
- references/authoring/model-binding.md7.7 KiB
- references/authoring/page-formatting.md4.5 KiB
- references/authoring/powerbi-desktop.md2.4 KiB
- references/authoring/powerbi-report-author-cli-part-02.md3.2 KiB
- references/authoring/powerbi-report-author-cli.md17.7 KiB
- references/authoring/preview-part-02.md16.9 KiB
- references/authoring/preview-part-03.md4.0 KiB
- references/authoring/preview-part-04.md2.5 KiB
- references/authoring/preview.md16.1 KiB
- references/authoring/re-theming-part-02.md16.8 KiB
- references/authoring/re-theming-part-03.md4.9 KiB
- references/authoring/re-theming.md1.5 KiB
- references/authoring/screenshot-review.md5.0 KiB
- references/authoring/shape.md13.6 KiB
- references/authoring/slicers-part-02.md16.3 KiB
- references/authoring/slicers.md15.6 KiB
- references/authoring/table.md17.5 KiB
- references/authoring/textbox.md5.6 KiB
- references/authoring/theming-part-02.md6.7 KiB
- references/authoring/theming.md16.4 KiB
- references/authoring/version-control.md6.6 KiB
- references/design.md17.3 KiB
- references/design/accessibility.md11.4 KiB
- references/design/anti-patterns.md18.5 KiB
- references/design/archetype-composition.md3.4 KiB
- references/design/archetypes/analytical-canvas.md17.7 KiB
- references/design/archetypes/comparative-benchmark-part-02.md5.7 KiB
- references/design/archetypes/comparative-benchmark.md15.8 KiB
- references/design/archetypes/executive-summary.md14.7 KiB
- references/design/archetypes/narrative-story.md18.1 KiB
- references/design/archetypes/operational-monitor.md17.0 KiB
- references/design/assets/base.json7.5 KiB
- references/design/brownfield.md5.7 KiB
- references/design/chart-selection.md9.8 KiB
- references/design/color.md10.5 KiB
- references/design/design-brief-part-02.md13.7 KiB
- references/design/design-brief.md8.8 KiB
- references/design/interactivity.md9.2 KiB
- references/design/layout.md11.3 KiB
- references/design/pre-flight-checklist.md10.8 KiB
- references/design/signatures.md12.3 KiB
- references/design/tone-catalog.md14.4 KiB
- references/design/typography.md9.2 KiB
- references/design/visual-cookbook-part-02.md11.0 KiB
- references/design/visual-cookbook.md16.7 KiB
- references/management-part-02.md17.2 KiB
- references/management-part-03.md7.5 KiB
- references/management-part-04.md16.7 KiB
- references/management.md10.1 KiB
- references/planning-part-02.md11.2 KiB
- references/planning.md19.5 KiB
references/authoring/card-part-02.md
Card Visual Authoring Guide - Part 2
Contents
Card Sizing (Required)
Step 0: Read the canvas height
Step 1: Compute dimensions
Step 2: Resolve effective values from cascade
Step 3: Verify no clipping
Step 4: Width considerations
Step 5: Apply in PBIR
Default values (cascade resolution)
Worked examples
Card Sizing Anti-Patterns
Continuation of card.md. Open this file directly from the skill reference index.
Card Sizing (Required)
Before creating or resizing any
cardVisual, compute all sizing values using the formula below. Cards must be compact (not crowd detail visuals) AND not clipped (text fully visible).
Step 0: Read the canvas height
Read from the page's page.json file:
<Report>.Report/definition/pages/<pageId>/page.json → "height"Common values: 720 (standard), 1080 (Full HD), 600 (mobile).
Step 1: Compute dimensions
Fonts scale with the canvas (readability). Height is generated as the content minimum for those fonts — never hardcoded — so text never clips and there is no empty band. The canvas budget only caps height so cards can't crowd out other visuals; it is never added to the height.
# 1. Fonts scale with the canvas — floored and capped
value_font_size = min(28, max(12, floor(canvas_height * 0.028)))
label_font_size = min(14, max(8, floor(value_font_size * 0.55)))
# 2. Fixed inner geometry (applied by the Step 5 recipe)
vco_padding = 8 # visualContainerObjects.padding — outer breathing room
inner_pad = 8 # objects.padding.paddingUniform — keeps text off the accent bar / edge
spacing = 2 # verticalSpacing between value and label
# 3. Height = content minimum for those fonts (label budgeted at >=12pt)
render(fs) = ceil(fs * 1.5)
content_min = 2*vco_padding + 2*inner_pad + spacing
+ render(value_font_size) + render(max(label_font_size, 12))
target_card_height = content_min
# 4. Canvas budget cap (crowd-out guard): height must stay <=15% of canvas
canvas_cap = floor(canvas_height * 0.15)
if content_min > canvas_cap:
reduce value_font_size (then label_font_size) toward the floors until
content_min <= canvas_cap # if already at the floors, the canvas is too small for cards
horizontal_padding = vco_paddingCaps 28/14pt, floors 12/8pt. Caps prevent oversized fonts on large canvases (readability plateaus above them); floors keep text legible. If the fonts hit the floor and
content_minstill exceeds the canvas cap, the canvas is too small for cards.
Quick Reference (height is the generated content minimum):
| Canvas Height | Value Font | Label Font | Card Height |
|---|---|---|---|
| 400px | — | — | Not supported — 15% cap (60px) < 70px minimum |
| 600px | 16pt | 8pt | 76 px |
| 720px | 20pt | 11pt | 82 px |
| 1080px | 28pt (cap) | 14pt (cap) | 97 px |
Heights use the compact recipe (Step 5): inner padding 8, VCO padding 8. Height budgets the label at >=12pt even when a smaller label font is set, so a shown or hidden label never clips.
For cards with reference labels, add ~16px to target_card_height to
accommodate the third text line (reference value/label pair).
Step 2: Resolve effective values from cascade
If modifying an existing card or if a custom theme is active, resolve the effective values before verifying. Inspect these sources in priority order (first match wins):
Visual file (
visual.json→objectsandvisualContainerObjects)Custom theme →
visualStyles.cardVisual.*(type-specific)Custom theme →
visualStyles.*.*(global wildcard)Custom theme →
textClasses.callout.fontSize(for value default)Base theme →
visualStyles.cardVisual.*(content padding, spacing)
Check the base theme (StaticResources/SharedResources/BaseThemes/*.json)
for the content area default properties:
visualStyles.cardVisual.*.padding.paddingUniform→ content inner paddingvisualStyles.cardVisual.*.layout.paddingUniform→ content outer paddingvisualStyles.cardVisual.*.spacing.verticalSpacing→ gap between value and label
These content-area defaults are a
cardVisualruntime built-in and are usually absent from the theme file. The effective defaults arepadding.paddingUniform ≈ 12(inner callout padding) andlayout.paddingUniform = 0—layoutadds height only when explicitly set. The compact recipe (Step 5) setspaddingto 8 (trimming the ≈12 default just enough to keep the value and label off the accent bar and card edge) and leaveslayoutat 0, so budget inner padding at 8, not 12.
These follow the same cascade as other properties (visual objects →
custom theme cardVisual.* → custom theme *.* → base theme).
Check the custom theme JSON for:
textClasses.callout.fontSize→ this is the defaultvalue_fontSizevisualStyles.*.*.padding.top/bottom→ VCO padding overridevisualStyles.*.*.border.show+.width→ border contributionvisualStyles.cardVisual.*.spacing.verticalSpacing→ verticalSpacing override
Check the visual JSON for any per-card overrides on:
objects.value.fontSize,objects.label.fontSizevisualContainerObjects.padding.top/bottomvisualContainerObjects.border.show/widthvisualContainerObjects.title.show/fontSizevisualContainerObjects.spacing.spaceBelowTitleArea
Only after resolving all effective values, proceed to Step 3.
Step 3: Verify no clipping
Card visual anatomy (top to bottom):
┌──────────────────────────────────────────────────────────┐
│ VCO border (top) │ border_width
├──────────────────────────────────────────────────────────┤
│ VCO padding (top) │ padding_top
├──────────────────────────────────────────────────────────┤
│ Title text (if shown) │ render(title_fontSize)
│ Space below title │ spaceBelowTitleArea
├──────────────────────────────────────────────────────────┤
│ Content padding (top) │ content_padding_top
│ Value text: "283K" │ render(value_fontSize)
│ verticalSpacing │ spacing.verticalSpacing
│ Label text: "Sum of Profit" │ render(label_fontSize)
│ Content padding (bottom) │ content_padding_bottom
├──────────────────────────────────────────────────────────┤
│ VCO padding (bottom) │ padding_bottom
├──────────────────────────────────────────────────────────┤
│ VCO border (bottom) │ border_width
└──────────────────────────────────────────────────────────┘Key facts:
Always reserve label height — compute it as
render(max(label,12)), so even a label font below 12pt still gets ≥12pt of vertical room in the card. This keeps a row of cards the same height; only a single, standalone value-only card (label.show=false) may drop it for a tighter fit.Content padding comes from two objects, each with uniform/individual modes:
objects.padding: ifpaddingIndividual=trueuse per-side values, elsepaddingUniformobjects.layout: ifpaddingIndividual=trueusetopOuterMargin/bottomOuterMargin, elsepaddingUniform
VCO padding (
visualContainerObjects.padding):top/bottom/left/rightverticalSpacing: from
objects.spacingorvisualContainerObjects.spacingcalloutSize (
objects.layout.calloutSize): percentage that may scale the content area. Runtime default is unverified.
render(fs) = ceil(fs × 1.5)
# Resolve content padding from cascade:
# - padding object: paddingUniform (or paddingTop/paddingBottom if paddingIndividual=true)
# - layout object: paddingUniform (or topOuterMargin/bottomOuterMargin if paddingIndividual=true)
content_padding_top = padding_obj_top + layout_obj_top
content_padding_bottom = padding_obj_bottom + layout_obj_bottom
required_height = border_width × 2
+ padding_top + padding_bottom
+ (render(title_fontSize) + spaceBelowTitleArea) × title_visible
+ content_padding_top + content_padding_bottom
+ render(value_fontSize)
+ verticalSpacing
+ render(effective_label_fontSize)
+ accentBar_width × accentBar_top_or_bottom
effective_label_fontSize = max(explicit_label_fontSize, 12)
Constraint: required_height ≤ position.heightStep 4: Width considerations
Width overflow shows ellipsis ("...") rather than clipping — less severe than height clipping. Properties that consume horizontal space:
VCO padding left/right (
visualContainerObjects.padding)Content padding left/right (from
objects.paddingandobjects.layout, same uniform/individual logic as vertical)Border width (left + right)
Accent bar width (if positioned left or right)
If values are truncated with ellipsis, increase position.width or reduce
value_font_size.
Use 5 chars when display format is unknown. Width overflow shows ellipsis.
Step 5: Apply in PBIR
The recipe sets objects.padding.paddingUniform to 8 and
objects.layout.paddingUniform to 0. This trims the built-in inner callout
padding (≈12) to keep the card compact, while leaving a small margin so the value
and label never touch the accent bar or card edge. VCO padding (below) supplies
the outer breathing room.
"objects": {
"value": [{ "properties": { "fontSize": { "expr": { "Literal": { "Value": "<value_font_size>D" } } } }, "selector": { "id": "default" } }],
"label": [{ "properties": { "fontSize": { "expr": { "Literal": { "Value": "<label_font_size>D" } } } }, "selector": { "id": "default" } }],
"padding": [{ "properties": { "paddingUniform": { "expr": { "Literal": { "Value": "8D" } } } }, "selector": { "id": "default" } }],
"layout": [{ "properties": { "paddingUniform": { "expr": { "Literal": { "Value": "0D" } } } }, "selector": { "id": "default" } }]
},
"visualContainerObjects": {
"padding": [{
"properties": {
"top": { "expr": { "Literal": { "Value": "<vertical_padding>D" } } },
"bottom": { "expr": { "Literal": { "Value": "<vertical_padding>D" } } },
"left": { "expr": { "Literal": { "Value": "<horizontal_padding>D" } } },
"right": { "expr": { "Literal": { "Value": "<horizontal_padding>D" } } }
},
"selector": { "id": "default" }
}],
"spacing": [{
"properties": {
"customizeSpacing": { "expr": { "Literal": { "Value": "true" } } },
"verticalSpacing": { "expr": { "Literal": { "Value": "2D" } } }
},
"selector": { "id": "default" }
}]
}Default values (cascade resolution)
Priority: visual objects → custom theme cardVisual.* → custom theme *.* → base theme.
| Variable | Source | Notes |
|---|---|---|
value_fontSize | textClasses.callout.fontSize | Override via objects.value.fontSize (id selector) |
label_fontSize | textClasses.label.fontSize | Override via objects.label.fontSize (id selector) |
padding_top/bottom/left/right | visualContainerObjects.padding | VCO padding around the whole visual |
padding object | objects.padding (id selector) | paddingUniform or individual paddingTop/Bottom/Left/Right |
layout object | objects.layout (id selector) | paddingUniform or individual topOuterMargin/bottomOuterMargin |
verticalSpacing | objects.spacing (id selector) | Gap between value and label |
spaceBelowTitleArea | visualContainerObjects.spacing | Gap below title area |
calloutSize | objects.layout.calloutSize | Percentage; runtime default unverified |
title_fontSize | visualContainerObjects.title | Title font size when title is shown |
border_width | visualContainerObjects.border | Only contributes when border.show=true |
accentBar_width | objects.accentBar (id selector) | Only contributes when accentBar.show=true |
Always read the report's base theme file (
StaticResources/SharedResources/BaseThemes/*.json) for authoritative default values. Do not assume hardcoded constants.
Worked examples
These examples use the compact recipe (Step 5): padding.paddingUniform=8,
layout.paddingUniform=0, verticalSpacing=2, VCO padding top/bottom=8, label
budgeted at ≥12pt. Example 1 shows what happens if you skip the recipe and leave
the ≈12 built-in inner padding (plus an added layout).
Example 1 — recipe skipped: built-in padding ≈12 plus an added layout=12 (FAILS):
content_padding = (12 padding + 12 layout) × 2 sides = 48
required_height = 8+8 + 48 + ceil(20×1.5) + 2 + ceil(12×1.5)
= 16 + 48 + 30 + 2 + 18 = 114
→ 114 > 82 → CLIPS!
Fix — apply the Step 5 recipe (padding=8, layout=0):
content_padding = (8 + 0) × 2 = 16
required_height = 16 + 16 + 30 + 2 + 18 = 82 → fits an 82px cardExample 2 — with title and accent bar:
title_area = render(title_fontSize) + spaceBelowTitleArea
required_height = border + VCO_padding + title_area + content_padding
+ render(value) + verticalSpacing + render(label) + accentBarExample 3 — custom VCO padding=4, border=2, value=32/label=14:
content_padding = (8 padding + 0 layout) × 2 = 16
required_height = 2×2 + 4+4 + 16 + ceil(32×1.5) + 2 + ceil(14×1.5)
= 4 + 8 + 16 + 48 + 2 + 21 = 99
→ use h ≥ 100Quick-reference safe dimensions
Compact recipe (padding.paddingUniform=8, layout.paddingUniform=0,
VCO padding=8, verticalSpacing=2, label=12pt, no title, no border):
| value.fontSize | Min height |
|---|---|
| 20 | 82 |
| 24 | 88 |
| 28 | 94 |
| 32 | 100 |
| 36 | 106 |
| 40 | 112 |
| 45 | 120 |
With title: add render(title_fontSize) + spaceBelowTitleArea to height.
With custom VCO padding=4: subtract 8px from height.
These are the true minimums for the compact recipe — the smallest height that renders a value + label without clipping. Step 1 sets card height to this minimum, so cards stay compact by construction. Add
render(title_fontSize) + spaceBelowTitleAreafor a title, and ~16px for a reference/delta line.
Card Sizing Anti-Patterns
| ❌ Anti-pattern | ✅ Do instead |
|---|---|
Hardcoding card height (e.g. height: 80) | Generate it from the Step 1 formula (content minimum for the derived fonts) |
Leaving the ≈12 built-in inner padding, or adding layout padding | Apply the Step 5 recipe: objects.padding.paddingUniform=8, objects.layout.paddingUniform=0 |
| Growing card height to stop the label clipping | Trim inner padding to 8 instead; height then matches the content |
| Setting inner padding to 0 to save space | Keep 8 — at 0 the value/label touch the accent bar and card edge |
Quoting numeric position values ("height": "80") | Use raw numbers ("height": 82) |
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