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/color.md

Color Strategy

Core Principles
Palette Reference Tables
- Sequential Palettes
- Diverging Palettes
- Categorical Palettes
Color Vision Deficiency (CVD) and WCAG Contrast
Semantic Color Rules
Power BI Theme Grounding
Color Assignment Strategy
- Rules
- Example (4 cards + 3 charts on one page)
- Implementation
Archetype Calibration
Highlight Pattern
Conditional Formatting Techniques
Color Assignment Rules
Palette Selection Decision Tree

Core Principles

Palette family matches data family — sequential for ordered, diverging for ±, categorical for nominal.
Never rainbow on ordered data — rainbow has no perceptual order; it misleads.
Color is never the sole channel — always pair with shape, label, or pattern (WCAG 1.4.1).
Cap categorical palettes at 7–8 hues — beyond that, colors become indistinguishable.
Restraint beats vibrance — most of the canvas should be neutral; color draws the eye to what matters.
Contrast is non-negotiable — every text-on-background pair must meet WCAG AA.
Reserve semantic colors — green/red/amber carry meaning; don't waste them on decoration.

Palette Reference Tables

Sequential Palettes

Name	Hex Ramp (5-step)	CVD Safe	Use
Blues (ColorBrewer)	`#EFF3FF` `#BDD7E7` `#6BAED6` `#3182BD` `#08519C`	✅ All	Default sequential; low-to-high magnitude
YlOrRd (ColorBrewer)	`#FFFFB2` `#FECC5C` `#FD8D3C` `#F03B20` `#BD0026`	⚠️ Deutan marginal	Heat / urgency encoding
Viridis	`#440154` `#3B528B` `#21908C` `#5DC863` `#FDE725`	✅ All	Perceptually uniform; print-safe
Cividis	`#002051` `#3F5B75` `#8E8E52` `#CBBE2D` `#FDEA45`	✅ All + grayscale	Best CVD-safe option; blue-yellow only

Diverging Palettes

Name	Low → Mid → High	Midpoint	CVD Safe
RdBu	`#B2182B` → `#F7F7F7` → `#2166AC`	Neutral white/grey	✅
BrBG	`#8C510A` → `#F5F5F5` → `#01665E`	Neutral white/grey	✅
PiYG	`#C51B7D` → `#F7F7F7` → `#4D9221`	Neutral white/grey	⚠️ Protan marginal

Categorical Palettes

Name	Colors (hex)	Count	CVD Safe
Okabe-Ito	`#E69F00` `#56B4E9` `#009E73` `#F0E442` `#0072B2` `#D55E00` `#CC79A7` `#000000`	8	✅ All
Set2 (ColorBrewer)	`#66C2A5` `#FC8D62` `#8DA0CB` `#E78AC3` `#A6D854` `#FFD92F` `#E5C494` `#B3B3B3`	8	✅
Tableau 10	`#4E79A7` `#F28E2B` `#E15759` `#76B7B2` `#59A14F` `#EDC948` `#B07AA1` `#FF9DA7` `#9C755F` `#BAB0AC`	10	⚠️ Deutan pair clash at 9-10

Color Vision Deficiency (CVD) and WCAG Contrast

Contrast and CVD: see references/design/accessibility.md

Semantic Color Rules

Color	Default Meaning	Rule
Green	Good / positive / on-target	Reserve for favorable status only
Red	Bad / negative / critical	Reserve for unfavorable status only
Amber/Yellow	Warning / approaching threshold	Use between green and red
Grey	Neutral / context / benchmark	Default for non-highlighted elements
Blue	Informational / primary brand accent	Safe default when no semantic load

Constraints:

Never flip semantics (green = bad) without explicit user instruction.
Never use red and green as the only differentiator — pair with icon or label.
Cultural caveat: in some East Asian financial contexts, red = gain. Note if the report targets those markets.

Power BI Theme Grounding

Theme Key	Purpose	Notes
`dataColors`	Ordered list of categorical series colors	First 8 entries matter most
`good` / `neutral` / `bad`	Sentiment triplet	Map to green / grey / red
`firstLevelElements` (`foreground`)	Primary text and foreground marks	Must pass 4.5:1 on `background`
`secondLevelElements` (`foregroundNeutralSecondary`)	Axis labels, subtitles, secondary text	Must pass contrast on `background` / `secondaryBackground`
`thirdLevelElements` (`backgroundLight`)	Gridlines, subtle rules, low-emphasis fills	Keep visible on page and visual surfaces
`fourthLevelElements` (`foregroundNeutralTertiary`)	Dimmed labels and tertiary foreground	Use only for non-critical context
`background`	Page canvas	Usually white or near-white
`secondaryBackground` (`backgroundNeutral`)	Visual/container secondary fill, disabled fills	Often slightly offset from `background`
`tableAccent`	Accent lines, borders	Use for gridlines, dividers

Per-visual color choices: dataPoint.fill.solid.color, labels.color, title.fontColor, and visual-specific conditional formatting rules (not custom theme JSON).

Color Assignment Strategy

Assign colors per-page so visuals are visually linked when they share a measure and distinct when they don't.

Rules

Same measure → same color. If a card shows "Total Fights" with a sky blue accent bar, the line chart trending Total Fights should also be sky blue (via defaultColor). This creates a visual link — the card and its trend chart tell the same story.
Breakdown of a measure → gradient of that color. A bar chart showing Total Fights by Weight Class uses a light→dark gradient of sky blue (via dataPoint.fill FillRule). The gradient ties the breakdown to its parent measure while the value shading reinforces the sort order.
Different measure → different hue. A bar chart showing Events by Country uses a different palette hue than a Fights chart. Pick the next unused color from the theme's dataColors array.
Cards consume palette slots first in reading order (top-left → right). Charts derive from or take the next available slot.

Example (4 cards + 3 charts on one page)

Visual	Measure	Color	Source
Card 1: Total Events	count	`dataColors[0]` #D55E00	Slot 0
Card 2: Total Fights	measure	`dataColors[1]` #56B4E9	Slot 1
Card 3: Total Fighters	count	`dataColors[2]` #009E73	Slot 2
Card 4: Finish Rate	rate	`dataColors[3]` #0072B2	Slot 3
Line: Fights by Year	Total Fights	#56B4E9	matches Card 2
Bar: by Weight Class	Total Fights breakdown	#56B4E9 gradient	gradient of Card 2
Bar: by Country	Total Events breakdown	#D55E00 gradient	gradient of Card 1

Implementation

Cards: set accent bar color via accentBar.color (Literal hex)
Line/area charts: set dataPoint.defaultColor to match the card
Bar charts: set dataPoint.fill FillRule linearGradient2 with min (light tint, ~50% toward white) and max (base color). Use Literal hex — ThemeDataColor does not work inside FillRule.
Data labels on charts: always use neutral dark (#252423), never the accent color — colored labels clash with the chart elements

Archetype Calibration

Archetype	Palette Strategy	Typical Colors
Executive	3 semantic (green/amber/red) + 1 brand accent + grey	5 total
Operational	RAG (red/amber/green) + status grey + 1 highlight	5 total
Analytical	Full categorical (Okabe-Ito or Set2) + sequential for heatmaps	Up to 8
Narrative	1 highlight + grey context	2–3 total
Comparative	Diverging (RdBu) or paired categorical	4–6 total

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

Highlight Pattern

Use color to draw attention to the key data point while greying out context:

Element	Color Treatment	Example
Highlighted bar/line	Saturated brand or semantic color	`#3182BD` (blue) or `#E15759` (red)
Context bars/lines	Light grey	`#D9D9D9` or `#E0E0E0`
Reference line	Medium grey, dashed	`#999999`, 1px dashed
Background	White or near-white	`#FFFFFF`

This pattern works across archetypes. In Narrative reports, the highlight is the thesis. In Analytical reports, the highlight is the selected subset.

Conditional Formatting Techniques

Use conditional formatting when it reinforces the page's main comparison, threshold, or exception pattern.

Technique	Use on	Effect
Per-series color	Bar/column charts	Each category bar gets a distinct color when category identity matters
Threshold color	KPI cards	Background or font color changes based on good/neutral/bad thresholds
Data bars	Table numeric columns	In-cell horizontal bars show magnitude at a glance
Icon sets	Table status columns	Pass/fail or good/warn/bad status becomes scannable
Color gradient	Matrix cells, heatmaps	Min→mid→max color scale reveals patterns
Highlight + grey	Any chart	One series in accent color, rest in `#BDBDBD` — draws the eye to the insight

For implementation mechanics, hand these choices to the authoring mode.

Color Assignment Rules

Rule	Description
Consistent mapping	Same category = same color across every page and visual in the report
Semantic priority	If a category has inherent meaning (e.g., "Critical"), use semantic color first
Order follows palette order	First series = first `dataColors` entry; don't skip indices
Legend = data order	Legend should sort to match the visual order of data elements
Conditional formatting sparingly	Only for traffic-light status, heatmaps, or threshold-based alerts
No color for decoration	Every color applied must encode information

Palette Selection Decision Tree

What type of data?
├── Nominal / categorical (no order)
│   ├── ≤8 categories → Okabe-Ito or Set2
│   └── >8 categories → Group into "Other"; limit to 7-8 hues
├── Ordinal / sequential (low→high)
│   ├── Needs CVD safety → Cividis or Viridis
│   └── Standard → Blues (ColorBrewer)
├── Diverging (±from midpoint)
│   ├── Needs CVD safety → BrBG
│   └── Standard → RdBu
└── Semantic (status / sentiment)
    └── Use theme `good` / `neutral` / `bad` keys

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/color.md

Color Strategy

Contents

Core Principles

Palette Reference Tables

Sequential Palettes

Diverging Palettes

Categorical Palettes

Color Vision Deficiency (CVD) and WCAG Contrast

Semantic Color Rules

Power BI Theme Grounding

Color Assignment Strategy

Rules

Example (4 cards + 3 charts on one page)

Implementation

Archetype Calibration

Highlight Pattern

Conditional Formatting Techniques

Color Assignment Rules

Palette Selection Decision Tree

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