Powerbi Report CLI

MicrosoftOfficialPublished by Microsoft

Skill
Tool integration
Data and AI
MIT
Low risk

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/tone-catalog.md

Tone Catalog

1. Editorial Newsroom
2. Industrial Cockpit
3. Clinical Calm
4. FT Pink Financial
5. Bauhaus Catalog
6. Monospace Terminal
7. Industrial Dense (Analyst Workbench)
8. Playful Energetic
9. Minimal Restrained
10. Corporate Cool
11. Scholarly Calm
12. Brand-Forward (template)
Remixing tones
Default tone by domain (when user is silent)

The Step 1 tone field is open vocabulary — a free-text adjective + short elaboration. But agents (and humans) struggle to pick a tone from nothing. This catalog is a calibration set, not a closed style menu. Prefer a catalog entry when it fits the audience, data, brand, and user constraints; otherwise remix entries or author a custom tone.

The Design Brief: may use a catalog name, a remixed name, or a short custom tone phrase as long as it drives concrete downstream choices. Do not force every report into one of these entries.

Each entry maps the tone to downstream choices so picking a tone actually drives later decisions:

Typography pairing (display + body)
Palette move (cool/warm, accent count, surface)
Density / rhythm (modular ratio)
Gridline / border treatment
Default signature candidate
Iconography style
Domain examples

If your report's tone is one word ("modern", "professional", "clean") and not in this catalog, do one of two things:

Pick a catalog entry instead. "Modern" is ambiguous; "Editorial Bold" or "Corporate Cool" or "Minimal Restrained" are not.
Write a short elaboration that pins it down. "Modern" → "modern editorial newsroom with serif display headings, sans body, single amber accent, no gridlines."

A custom tone must include enough detail to guide implementation:

Emotional feel / audience posture
Surface or palette direction
Typography direction
Density / spacing direction
One concrete downstream implication

Font guardrail: prefer fonts that Power BI reliably supports across Desktop and Service (for example Segoe UI, DIN, Georgia, Consolas, Arial, Calibri, Tahoma, Verdana). Catalog font names are design direction; when a font is not guaranteed in Power BI, specify a built-in fallback and do not assume Service, mobile, or embedded rendering will match Desktop.

Tone is not interior decoration — it's a constraint that makes every later decision easier.

1. Editorial Newsroom

Reads like a Sunday business broadsheet. Type leads. One sharp accent. Whitespace generous.

Aspect	Pick
Display typography	Serif (Source Serif Pro, Merriweather, or Georgia) at 28–48pt
Body typography	Sans (Segoe UI, Inter, or Source Sans) at 11–13pt
Surface	Cream `#FAF7F0` or off-white `#F8F9FA`
Accent	One — black `#0F172A` for emphasis, or mustard `#D4A30A` for highlight
Density / ratio	1.500 (Perfect Fifth) — strong hierarchy
Gridlines	Hairline rules above/below sections; no chart gridlines
Borders	None on visuals; section dividers only
Default signature	Display serif headlines + tabular numerals on KPIs
Iconography	Outlined hairline (1px) — restrained
Domain examples	Quarterly review for board, annual report, financial publication, news/media analytics

2. Industrial Cockpit

Dark canvas, instrument-panel feel. High contrast. Restrained color — color is reserved for status, not decoration.

Aspect	Pick
Display typography	Geometric sans bold (Inter Bold, Roboto Bold) at 24–36pt
Body typography	Same family, regular weight, at 10–12pt
Surface	Dark navy `#120E2A` or near-black `#0E0E10`
Accent	Indigo `#5772D9` + cyan `#8CEEEE` for status; muted purple `#7D77A8` for chrome
Density / ratio	1.333 (Perfect Fourth) — gentle hierarchy, density-friendly
Gridlines	Dotted, low-opacity (`#3A3A4A`)
Borders	Subtle (`#2A2A3A`); use background-fill cards for grouping instead
Default signature	High-contrast status values on dark; status icons in cards
Iconography	Filled, geometric — high contrast on dark
Domain examples	Ops monitoring, NOC dashboards, on-call wallboards, infrastructure health

3. Clinical Calm

Cool, almost-white canvas. Teal/sage accents. Generous spacing. Healthcare-feeling without being sterile.

Aspect	Pick
Display typography	Humanist sans (Source Sans, Lato, Inter) at 22–32pt
Body typography	Same, regular, at 11pt
Surface	Cool blue-white `#F0F9FF`
Accent	Teal `#0D9488` + sage `#84CC16`; reserve red strictly for genuine alerts
Density / ratio	1.250 (Major Third) — gentle
Gridlines	Solid, very-low-opacity (`#E5E7EB`)
Borders	1px hairline `#E5E7EB`, radius 8px
Default signature	Calm spacing within the space-audit budget; KPI values centered in compact cards
Iconography	Outlined, semi-bold stroke; never red except for alerts
Domain examples	Patient safety dashboards, clinical operations, healthcare KPIs, wellness programs

4. FT Pink Financial

Specific reference: the Financial Times pink-tinted broadsheet. Tabular numerals everywhere. Editorial discipline applied to financial data.

Aspect	Pick
Display typography	Serif (Financier, Source Serif Pro fallback) at 28–48pt
Body typography	Sans (Segoe UI, Inter) with tabular-looking numeric treatment where values must align
Surface	Pink-tinged white `#FFF1E5` (the FT pink)
Accent	Black `#0F172A` for type; one teal/red for variance signal only
Density / ratio	1.500 — strong hierarchy via type
Gridlines	None on charts; thin rules between sections
Borders	None
Default signature	Tabular numerals throughout + serif display headlines
Iconography	Minimal — type carries the load
Domain examples	Hedge fund / asset-management reporting, financial earnings dashboards, market commentary

5. Bauhaus Catalog

Geometric, modernist, functional. Primary colors used sparingly. Type-as-signal.

Aspect	Pick
Display typography	Geometric sans (Futura, ITC Avant Garde, or Inter Bold) at 32–48pt; consider all-caps tracking
Body typography	Same family at 11–13pt
Surface	Off-white `#FAFAFA`
Accent	One primary — true red `#E63946`, true blue `#1D3557`, or true yellow `#F4D03F`
Density / ratio	1.333 — modular
Gridlines	None or solid hairline
Borders	Strong (2px solid) where used; otherwise none
Default signature	All-caps tracked headlines + bold geometric ratios
Iconography	Geometric / pictogram
Domain examples	Design-team dashboards, brand reporting, creative-agency analytics

6. Monospace Terminal

Developer/quant feel. Monospaced numbers (and possibly all type). Ticker-style KPI bars. Color used like syntax highlighting.

Aspect	Pick
Display typography	Monospace (Cascadia Code, JetBrains Mono, Consolas) at 24–36pt OR sans display + monospace numerals
Body typography	Monospace at 11pt OR sans body with mono numerals
Surface	Off-white `#F8F8F2` (Solarized-light) or near-black `#0E0E10`
Accent	Two accents like syntax tokens — green `#50FA7B` + magenta `#FF79C6` (Dracula), or muted teal `#268BD2` + amber `#B58900` (Solarized)
Density / ratio	1.250 — dense
Gridlines	Dotted, monospace-grid feel
Borders	None or 1px subtle
Default signature	Monospaced KPI ticker bar across the top
Iconography	ASCII-style or filled geometric
Domain examples	Engineering dashboards, quant trading, observability, developer-team metrics

7. Industrial Dense (Analyst Workbench)

Off-white surface, dense data, charcoal type, two-color accent. Built for the analyst who is going to spend an hour in this report.

Aspect	Pick
Display typography	Sans (Inter, Work Sans) at 18–26pt
Body typography	Same family at 10–11pt
Surface	Off-white `#FAFAFA`
Accent	Steel blue `#3B6E91` + burnt orange `#C8742A`; charcoal `#262626` for text
Density / ratio	1.250 — packed but legible
Gridlines	Solid `#E5E5E5` — packed grids need them
Borders	1px `#E0E0E0` — defines cells in dense layouts
Default signature	Tabular numerals + matrix-style page layout
Iconography	Filled, small (14–16px)
Domain examples	Financial models, ops analytics, sales-pipeline workbenches, IBCS-style variance reports

8. Playful Energetic

Warm, bright, geometric. Coral and warm accents. Soft shapes. Consumer/lifestyle feel without being childish.

Aspect	Pick
Display typography	Rounded geometric (Quicksand, Nunito, or Poppins) at 28–40pt
Body typography	Same family at 11pt
Surface	Warm cream `#FFF7ED`
Accent	Coral `#FB7185` + black `#171717`; peach `#FED7AA` for cues
Density / ratio	1.333 — friendly hierarchy
Gridlines	None on charts; pill-shaped section labels instead
Borders	Rounded (radius 12–16px); soft drop-shadow on primary KPI cards OK
Default signature	Pill-shaped KPI cards + warm coral accent
Iconography	Rounded duotone — soft and friendly
Domain examples	Consumer / retail, lifestyle apps, hospitality, creator-economy dashboards

9. Minimal Restrained

White canvas, black type, one accent, no chartjunk. The "less is more" tone — relies entirely on confident hierarchy.

Aspect	Pick
Display typography	Sans (Inter, Segoe UI) at 24–48pt
Body typography	Same, regular, at 11pt
Surface	True white `#FFFFFF`
Accent	One — usually black `#0F172A` for type and ONE single hue (any) for the highlight
Density / ratio	1.500 or 1.618 — strong hierarchy via size, since color isn't doing the work
Gridlines	None
Borders	None
Default signature	Composite KPI focus + everything else greyscale
Iconography	Omit, or outline-only at small sizes
Domain examples	Executive landing pages, primary-metric-with-context reports, dashboards where the story is the headline

10. Corporate Cool

The default for B2B SaaS, enterprise. Cool grey surface, slate type, one tech-feeling accent. Restrained but not stark.

Aspect	Pick
Display typography	Sans (Segoe UI Semibold, Inter Semibold) at 22–32pt
Body typography	Same family at 11pt
Surface	Cool grey `#F1F5F9`
Accent	Slate `#334155` + cyan `#06B6D4`; slate-300 `#CBD5E1` for cues
Density / ratio	1.333
Gridlines	Solid `#E2E8F0`, low-opacity
Borders	1px `#E2E8F0`, radius 8px
Default signature	Cyan accent on primary KPI/context; everything else slate
Iconography	Outlined, semi-bold stroke
Domain examples	B2B SaaS metrics, enterprise dashboards, internal tooling reports

11. Scholarly Calm

Stone surface, forest-green and soft-red accents, serif headings, no bright colors. Reads like an academic paper.

Aspect	Pick
Display typography	Serif (Merriweather, EB Garamond) at 22–32pt
Body typography	Sans (Source Sans, Inter) at 11pt
Surface	Stone `#F5F5F4`
Accent	Forest `#1C5E47` + soft red `#C2615F`; stone-400 `#A8A29E` for cues
Density / ratio	1.250 — gentle
Gridlines	Hairline rules, low-opacity
Borders	None or stone-300 hairline
Default signature	Serif headings + footnote-style annotations
Iconography	Outlined hairline; sparing use
Domain examples	Research dashboards, academic analytics, policy reporting, public-data visualizations

12. Brand-Forward (template)

When the user provides brand guidelines, treat the brand as the tone. This is a template, not a fixed entry — adapt to the brand's typography, palette, and signature elements.

Aspect	Pick
Display typography	Brand display font (with system fallback chain)
Body typography	Brand body font (with Segoe UI fallback) at 11pt
Surface	Brand-neutral surface (off-white tinted toward brand if defined)
Accent	Primary brand color for the main emphasis; secondary for context
Density / ratio	Pick from brand mood — energetic brands → 1.5; restrained brands → 1.25
Gridlines	Match brand's rule treatment (none / hairline / dotted)
Borders	Match brand's container treatment
Default signature	The brand's most recognizable visual move (logo placement, header band, accent stripe)
Iconography	Brand icon library if provided; otherwise pick a single style consistent with brand mood
Domain examples	Customer-facing dashboards with brand identity, white-label reports, marketing analytics for a specific brand

Remixing tones

Two tones can compose if the resulting choices are coherent:

Editorial Newsroom × FT Pink Financial → serif display + tabular numerals + pink surface. Coherent. ✓
Industrial Cockpit × Bauhaus Catalog → dark canvas + geometric type
- primary-color accent. Coherent. ✓
Playful Energetic × Clinical Calm → coral + teal? Pick one. ✗

When in doubt, pick ONE and apply it cleanly. A muddied tone reads as no tone at all.

Default tone by domain (when user is silent)

If the prompt is otherwise specific enough to design, use domain as a recommendation signal for tone. If the overall prompt is vague (missing audience, purpose, page count, or filtering depth), follow the root skill's clarification workflow first and offer the domain-inferred tone as one option, not as permission to proceed silently.

Domain	Default tone
Finance / banking / audit	Corporate Cool or Editorial Newsroom
Healthcare / clinical	Clinical Calm
Operations / monitoring / NOC	Industrial Cockpit (dark) or Industrial Dense (light)
Retail / consumer / lifestyle	Playful Energetic
Engineering / observability / quant	Monospace Terminal or Industrial Dense
Executive landing / board reports	Minimal Restrained or Editorial Newsroom
B2B SaaS / enterprise	Corporate Cool
Research / academic / policy	Scholarly Calm
Brand-led (user provided guidelines)	Brand-Forward

Surface the recommendation to the user or record it as an assumption in the brief — "Recommended tone: Industrial Cockpit (dark canvas, indigo + cyan accents, dense data)."

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

2026-11-09

Also distributed in

microsoft/skills-for-fabric

AutoGineer is not affiliated with or endorsed by Microsoft or Microsoft.

Download ZIP

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