Powerbi Report CLI — Agent Skill by Microsoft

From the author

Plan, design, author, preview, publish, and manage Power BI reports across requirements, page design, local PBIR/PBIP edits, validation, screenshots, Fabric upload/download, and rebinding. Use for report lifecycle work; use semantic-model-authoring for model or DAX changes and fabriciq for data questions. Triggers: plan Power BI report, design report page, edit PBIR, preview PBIP, publish report, rebind report

— the description by Microsoft

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://autogineer.com/agent-skills/microsoft/powerbi-report-cli/download

Unzip 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.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
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-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

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.
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:

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

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>.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.

Complete Reference Index

Open every relevant reference directly from this index. Files named part-XX continue the named topic.

Authoring

Design

Mode Guides

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/design/archetypes/executive-summary.md

Executive Summary Dashboard

Job To Be Done
Core Principles
Layout Variants
- Variant A — Hero-Right (default)
- Variant B — KPI-Strip
- Variant C — Headline-Hero
Chart Selection
- Use
- Do NOT Use
Color & Typography
Interaction Design
- Do NOT Use
PBI Formatting Reference
- Card / CardVisual
- Sparkline (lineChart)
- Variance Bar (barChart)
- Page & Navigation
Decision Checklist

Archetype: Executive Summary Theme: for generated reports, preserve references/design/assets/base.json safeguards while adapting dataColors to domain; for brownfield, preserve the existing theme unless a theme swap is requested Canvas: greenfield default FHD 1920 x 1080; preserve existing size for brownfield unless resize is approved · pageAlignment: Middle Scan-time target: ≤ 10 seconds to comprehension

Job To Be Done

Dimension	Value
Primary user	CEO, GM, VP — time-poor decision-maker
Session trigger	Monday-morning skim before leadership standup
Core question	"Is the business on or off track, and why?"
Success metric	State comprehension in ≤ 10 s
Failure signal	Viewer opens a second artifact to understand status
Design implication	Everything beyond headline + KPIs belongs behind drill-through

Core Principles

#	Principle	Rationale
1	Descriptive title — thesis sentence, not label ("Revenue is 4 % above plan" not "Executive Dashboard Q3")	Eliminates interpretation step
2	3–6 KPI hard cap	Miller's 7 ± 2; beyond 6, comprehension collapses
3	Period-over-period context mandatory	Absolute + delta + direction arrow on every KPI
4	Sparklines over full trend charts	Convey trajectory without consuming scan budget
5	One hero chart proving the headline	Anchors the "why" behind the insight
6	3-color semantic palette	Green / Red / Neutral + grey — nothing else
7	Drill-through for all detail	Keeps surface clean; depth is one click away

Layout Variants

Pick ONE variant based on the data shape from Step 0. Do NOT mix. Default to A only when signals genuinely tie — record the data signal that drove your pick in variant_rationale.

Signal (from semantic model + brief)	Variant
3–4 KPIs and ONE clear hero metric with a meaningful trend/chart	A. Hero-Right
5–6 KPIs of comparable importance, no single hero metric	B. KPI-Strip
1–2 KPIs and a strong narrative chart (waterfall, decomp, big trend)	C. Headline-Hero

Variant A — Hero-Right (default)

KPI cards on the left, hero chart on the right. The classic executive Z-pattern. The hero is the explanatory chart, not a blown-up single card.

┌──────────────────────────────────────────────────────────┐
│  TITLE BAR (h=48)                         [date slicer] │  ← thesis sentence
│  subtitle / as-of date (h=24)                           │
├────────┬────────┬────────┬────────┬──────────────────────┤
│ KPI 1  │ KPI 2  │ KPI 3  │ KPI 4  │   HERO CHART        │  h=160
│ +spark │ +spark │ +spark │ +spark │   (bar / line)       │
├────────┴────────┴────────┴────────┼──────────────────────┤
│  VARIANCE SNAPSHOT                │  RISK / EXCEPTION    │  h=240
│  (ranked bar, top-5 movers)       │  LIST (table, ≤8)    │
├───────────────────────────────────┴──────────────────────┤
│  source · refresh · active filters · [drill buttons]     │  h=32
└──────────────────────────────────────────────────────────┘

Zone	Height	Content
Title bar	48 px	Descriptive title + subtitle
KPI row + hero	160 px	4 cards (sparklines on) + 1 hero chart
Analysis row	240 px	Variance snapshot + risk/exception list
Footer	32 px	Source, refresh, filter state, drill buttons

KPI cards take the left ~830px (4 × 200 + gaps); hero chart takes the right ~400px. Sparklines on cards convey trajectory; the hero chart proves the headline.

Variant B — KPI-Strip

Full-width KPI row across the top, dual analysis charts below. No single hero — the KPI row IS the message.

┌──────────────────────────────────────────────────────────┐
│  TITLE BAR (h=48)                         [date slicer] │
├──────┬──────┬──────┬──────┬──────┬──────────────────────┤
│KPI 1 │KPI 2 │KPI 3 │KPI 4 │KPI 5 │ KPI 6 (optional)    │  h=120
│value │value │value │value │value │ value               │
│ +Δ   │ +Δ   │ +Δ   │ +Δ   │ +Δ   │ +Δ                  │
├──────┴──────┴──────┴──────┼──────┴──────────────────────┤
│  TREND — last 6 periods   │  TOP MOVERS — ranked bar    │  h=300
│  (line, multi-measure)    │  (top-5 by Δ%)              │
├───────────────────────────┴──────────────────────────────┤
│  source · refresh · filters · [drill buttons]            │  h=32
└──────────────────────────────────────────────────────────┘

The callout row is conditional: use it for a thesis sentence, variance summary, exception note, or dynamic narrative that explains the hero chart. Do not fill it with a bare card repeating a measure already visible in the hero chart or KPI strip.

Zone	Height	Content
Title bar	48 px	Descriptive title + subtitle
KPI strip	120 px	5–6 cards equal-width across full canvas
Analysis row	300 px	Multi-measure trend + ranked top movers
Footer	32 px	Source, refresh, filter state, drill buttons

Sparklines OFF on cards in this variant — the KPI strip already conveys breadth, and inline sparklines would compete with the trend chart below. Cards lose ~24px of value-area in exchange.

Variant C — Headline-Hero

One or two KPI cards stacked on the left, a single dominant narrative chart on the right. Use when the headline IS the chart (a waterfall, decomp, or big annotated trend). The KPI cards may be larger than strip cards, but they are context panels; the dominant hero remains the chart.

┌──────────────────────────────────────────────────────────┐
│  TITLE BAR (h=48)                         [date slicer] │
├────────────┬─────────────────────────────────────────────┤
│            │                                             │
│  KPI 1     │  HERO CHART                                 │
│  (large)   │  (waterfall / decomp / annotated trend)     │  h=400
│            │                                             │
│  KPI 2     │  Annotations and reference lines            │
│  (large)   │  carry the explanation                      │
│            │                                             │
├────────────┴─────────────────────────────────────────────┤
│  CALLOUT — thesis sentence supporting the chart          │  h=80
├──────────────────────────────────────────────────────────┤
│  source · refresh · filters · [drill buttons]            │  h=32
└──────────────────────────────────────────────────────────┘

The callout row is conditional: use it for a thesis sentence, variance summary, exception note, or dynamic narrative that explains the hero chart. Do not fill it with a bare card repeating a measure already visible in the hero chart or KPI strip.

Zone	Height	Content
Title bar	48 px	Descriptive title + subtitle
Hero block	400 px	1–2 large KPI cards (left ~280px) + dominant chart (right)
Callout	80 px	Textbox: one-sentence interpretation of the hero chart
Footer	32 px	Source, refresh, filter state, drill buttons

Annotations on the hero chart matter more than KPI count. Use reference lines, shaded periods, or arrow shapes to point at the moment that made the point.

Chart Selection

Use

Visual type	Role	Sizing / Notes
`cardVisual`	KPI display (value + delta + label)	One per metric
`lineChart` (sparkline)	Inline trend on KPI cards	120 × 48 px, all chrome off
`barChart`	Ranked variance (top movers)	Sort desc by absolute delta
`actionButton`	Drill-through navigation	One per target page

Do NOT Use

Visual type	Reason
`scatterChart`	Requires interpretation time > 10 s
`treemap`	Area encoding unreliable at small size
`histogram`	Statistical; wrong audience
`pivotTable` / `matrix`	Detail belongs behind drill-through
`gauge`	Consumes space, poor information density
`donutChart`	Part-to-whole not the question asked

Color & Typography

Element	Spec	Token
Descriptive title	20–24 pt SemiBold	`foreground`
KPI value	28–36 pt Bold	`foreground`
KPI label	10–11 pt Regular	`secondaryForeground`
Delta / change	12 pt SemiBold	Semantic color (green ↑ / red ↓)
Body text	11 pt Regular	`foreground`

Palette (3 + grey)

Role	Hex	Usage
Positive	`#107C10`	Delta up, on-track KPI
Negative	`#D13438`	Delta down, off-track KPI
Neutral	`#605E5C`	Flat / within-tolerance
Chrome / baseline	`#E1DFDD`	Grid lines, borders, backgrounds

Numeral rule: Always tabular / lining figures — proportional numerals misalign columns.

Interaction Design

Pattern	Implementation	Notes
Drill-through from KPI	`actionButton` with `drillthrough` action + `altText`	One button per detail page
Page tooltip on KPI card	Tooltip page 320 × 240, `tooltipType: ReportPage`	Shows 24 h sparkline + context
Period toggle	Bookmarks: vs-week / vs-plan	ONE toggle, not N slicers
Date filter	Single date picker, top-right	Maximum ONE slicer on page

Navigation model: Executive reports get minimal navigation — prefer the auto Page Navigator (or 1–2 drill-through buttons), never a dense custom button bar. See interactivity.md § Navigation Model Decision (see ../interactivity.md, section navigation-model-decision).

Do NOT Use

Anti-pattern	Why
Slicer panels / filter pane	Configuration tax; scan-time > 10 s
Cross-filter webs	Unpredictable state changes on passive page
Multiple slicer combos	Adds cognitive load incompatible with ≤ 10 s goal

Anti-patterns: see references/design/anti-patterns.md

PBI Formatting Reference

Card / CardVisual

Property path	Value	Purpose
`calloutValue > fontSize`	`36`	KPI prominence
`categoryLabel > show`	`true`	Metric name below value
`referenceLabel > show`	`true`	Delta / period-over-period
`visualHeader > show`	`false`	Clean card surface
`border > show`	`false`	Borderless card

Sparkline (lineChart)

Property path	Value	Purpose
`categoryAxis > show`	`false`	No X axis labels
`valueAxis > show`	`false`	No Y axis labels
`labels > show`	`false`	No data labels
`markers > show`	`false`	Clean line only
Size	160 × 48 px	Inline with KPI card

Variance Bar (barChart)

Property path	Value	Purpose
`fillRule` (CF)	Diverging at zero	Green positive / red negative
`sortByColumn`	Desc by absolute delta	Worst first

Property path	Value	Purpose
`page > width`	`1920` for greenfield	FHD default unless user requests another size
`page > height`	`1080` for greenfield	16:9 ratio
`pageAlignment`	`Middle`	Centered rendering
`actionButton > action`	`Drillthrough`	Navigate to detail
`actionButton > altText`	Descriptive label	Accessibility
Page tooltip canvas	320 × 240	Compact context tooltip
`tooltipType`	`ReportPage`	Enable custom tooltip page

Decision Checklist

Before shipping, verify every row:

#	Check	Pass?
1	Title is a thesis sentence, not a label	☐
2	KPI count ≤ 6	☐
3	Every KPI shows absolute + delta + direction	☐
4	One hero chart directly supports the headline	☐
5	Palette is exactly 3 semantic colors + grey	☐
6	All detail is behind drill-through	☐
7	Page scans in ≤ 10 s (test with a colleague)	☐
8	Maximum ONE slicer visible	☐
9	Visual headers hidden on all cards	☐
10	Footer shows data source + refresh timestamp	☐

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.

Matplotlib
K-Dense· Community
Creates and customizes scientific plots with Matplotlib. Used for fine-grained control over plot elements, novel plot types, and scientific workflows. Export to PNG/PDF/SVG for publication. For quick statistical plots use seaborn; for interactive plots use plotly; for publication-ready multi-panel figures with journal styling, use scientific-visualization.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskHas scriptsGitHub stars of the source repository56.4k
Seaborn
K-Dense· Community
A Python library for creating publication-quality statistical graphics with integrated pandas support.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
MITLow riskGitHub stars of the source repository56.4k
Kpi Dashboard Design
Seth Hobson· Community
A framework for designing effective, actionable KPI dashboards that drive business decisions through clear metrics and visualization best practices.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository42.3k
Power Bi Report Design Consultation
GitHubOfficial
A comprehensive framework for designing effective, accessible, and user-friendly Power BI reports.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
MITGitHub stars of the source repository40.9k
Power Bi Visualization Expert
GitHubOfficial
Expert guidance for designing effective, performant, and accessible Power BI reports following Microsoft best practices.
Data and AIGitHub Copilot
MITGitHub stars of the source repository40.9k
Build Dashboard
AnthropicOfficial
Generate self-contained, interactive HTML dashboards featuring charts, filters, and data tables.
Data and AIClaude CodeClaude appsOpenAI Codex+14 more
Apache-2.0GitHub stars of the source repository35.1k

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download powerbi-report-cli.zip

From the author

AutoGineer summary

What it does

When to use it

Advantages

Usage examples

Install

Documentation by Microsoft

Power BI Reports - CLI Skill

Mode Selection

Mode Boundary Rules

Required Deliverable by Mode

Rules

MUST

PREFER

AVOID

Complete Reference Index

Authoring

Design

Mode Guides

Examples

Route Compatibility

Files

references/design/archetypes/executive-summary.md

Executive Summary Dashboard

Contents

Job To Be Done

Core Principles

Layout Variants

Variant A — Hero-Right (default)

Variant B — KPI-Strip

Variant C — Headline-Hero

Chart Selection

Use

Do NOT Use

Color & Typography

Interaction Design

Do NOT Use

PBI Formatting Reference

Card / CardVisual

Sparkline (lineChart)

Variance Bar (barChart)

Page & Navigation

Decision Checklist

Requirements and compatibility

Security

Attribution and licence

Related skills

Matplotlib

Seaborn

Kpi Dashboard Design

Power Bi Report Design Consultation

Power Bi Visualization Expert

Build Dashboard

Download ZIP