powerbi-r-visuals
Skill3 starsChanged 7 months agoMITView on GitHub
R visual creation and ggplot2 patterns for PBIR reports. Automatically invoke when the user mentions "R visual", "ggplot2", "ggplot in Power BI", or asks to "create an R visual", "add an R chart", "write an R visual script", "inject an R script into Power BI".
- Installs packages
In this repository58 other files it gives its agents.
- powerbi-audit-tenant-settingsSkill
- powerbi-bpa-rulesSkill
- powerbi-connect-pbidSkill
- powerbi-connectSkill
- powerbi-create-pbi-reportSkill
- powerbi-c-sharp-scriptingSkill
- powerbi-custom-visualsSkill
- powerbi-cyber-securitySkill
- powerbi-data-catalog-lineageSkill
- powerbi-data-governance-traceabilitySkill
- powerbi-data-transformationSkill
- powerbi-dax-masterySkill
- powerbi-dax-performanceSkill
- powerbi-daxSkill
- powerbi-deneb-visualsSkill
- powerbi-doctorSkill
- powerbi-duckdb-lakehouseSkill
- powerbi-fabric-appsSkill
- powerbi-fabric-app-templatesSkill
- powerbi-fabric-capacitySkill
- powerbi-fabric-cliSkill
- powerbi-fabric-pipelinesSkill
- powerbi-fabricSkill
- powerbi-lineage-analysisSkill
- powerbi-measure-glossarySkill
- powerbi-medallion-architectureSkill
- powerbi-modelSkill
- powerbi-modifying-theme-jsonSkill
- powerbi-paginated-reportsSkill
- powerbi-pbi-cliSkill
- powerbi-pbip-formatSkill
- powerbi-pbir-cliSkill
- powerbi-pbir-format-enhancedSkill
- powerbi-performance-scaleSkill
- powerbi-power-querySkill
- powerbi-project-managementSkill
- powerbi-python-visualsSkill
- powerbi-refresh-semantic-modelSkill
- powerbi-report-authoringSkill
- powerbi-report-conversionSkill
- powerbi-report-designSkill
- powerbi-reportSkill
- powerbi-report-structureSkill
- powerbi-report-themingSkill
- powerbi-review-reportSkill
- powerbi-review-semantic-modelSkill
- powerbi-security-rlsSkill
- powerbi-source-integrationSkill
- powerbi-spark-livySkill
- powerbi-standardize-naming-conventionsSkill
- powerbi-star-schema-modelingSkill
- powerbi-svg-visualsSkill
- powerbi-te2-cliSkill
- powerbi-te-cliSkill
- powerbi-te-docsSkill
- powerbi-testing-validationSkill
- powerbi-time-series-dataSkill
- powerbi-tmdlSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 29
Create the visual.json file manually (see pbir-format skill in the pbip plugin for JSON structure) with visualType: scriptVisual, field …
- Very specific: line 48
Use backticks for column names with spaces:
dataset$Order Lines - Very specific: line 52
Before presenting the script to the user, dispatch the r-reviewer agent to validate correctness and provide design feedback.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
R Visuals in Power BI (PBIR)
Report modification requires tooling. Two paths exist:
pbirCLI (preferred) -- use thepbircommand and thepbir-cliskill. Install withuv tool install pbir-cliorpip install pbir-cli. Check availability withpbir --version.- Direct JSON modification -- if
pbiris not available, use thepbir-formatskill (pbip plugin) for PBIR JSON structure and patterns. Validate every change withjq empty <file.json>.If neither the
pbir-cliskill nor thepbir-formatskill is loaded, ask the user to install the appropriate plugin before proceeding with report modifications.
R visuals execute R scripts (primarily ggplot2) to render static PNG images on the Power BI canvas. ggplot2 is the preferred library -- its grammar of graphics approach produces clean, publication-quality statistical visualizations with less code. R is particularly strong for statistical visualizations.
Visual Identity
- visualType:
scriptVisual - Data role:
Values(columns and measures, multiple allowed) - Data variable:
dataset(data.frame, auto-injected) - Row limit: 150,000 rows
- Output: Static PNG at 72 DPI -- no interactivity
Workflow: Creating an R Visual
Step 1: Add the Visual
Create the visual.json file manually (see pbir-format skill in the pbip plugin for JSON structure) with visualType: scriptVisual, field bindings for the columns and measures you need (use Values:Table.Column or Values:Table.Measure format), and position/size as required.
Step 2: Write the Script
library(ggplot2)
p <- ggplot(dataset, aes(x=Date, y=Sales)) +
geom_col(fill="#5B8DBE") +
theme_minimal(base_size=12) +
theme(panel.grid.major.x=element_blank())
print(p) # MANDATORY for ggplot2Critical rules:
print(p)is mandatory for ggplot2 objects -- they do not auto-display in Power BIdatasetis auto-injected as a data.frame; do not create it- Access columns by index (
dataset[,1]) to avoid name escaping issues - Use backticks for column names with spaces:
dataset$`Order Lines`
Step 2b: Review
Before presenting the script to the user, dispatch the r-reviewer agent to validate correctness and provide design feedback.
Step 3: Inject the Script
Set the script content in the visual's objects.script[0].properties.source literal value (see PBIR Format section below).
Escaping rules for visual.json injection:
The script must be encoded as a single-quoted DAX literal string inside expr.Literal.Value:
- Newlines in the script become
\nin the JSON string - Double quotes inside the script (e.g.,
"#5B8DBE") become\"in the JSON string - The entire script is wrapped in single quotes:
'library(ggplot2)\n...\nprint(p)' - See
examples/visual/for a complete real-world visual.json showing this encoding
Step 4: Validate
Validate JSON syntax with jq empty <visual.json> and inspect the visual.json to confirm script content and field bindings.
PBIR Format
Scripts are stored in visual.objects.script[0].properties:
{
"source": {"expr": {"Literal": {"Value": "'library(ggplot2)\\n...\\nprint(p)'"}}},
"provider": {"expr": {"Literal": {"Value": "'R'"}}}
}Identical structure to Python visuals except visualType is scriptVisual and provider is 'R'.
Supported Packages
Power BI Service (R 4.3.3)
| Package | Version | Purpose |
| ggplot2 | 3.5.1 | Grammar of graphics |
| dplyr | 1.1.4 | Data manipulation |
| tidyr | 1.3.1 | Data tidying |
| ggrepel | 0.9.5 | Non-overlapping labels |
| patchwork | 1.2.0 | Compose multiple plots |
| cowplot | 1.1.3 | Publication-quality plots |
| corrplot | 0.94 | Correlation matrices |
| viridis | 0.6.5 | Color scales |
| RColorBrewer | 1.1-3 | Color palettes |
| forecast | 8.23.0 | Time series forecasting |
| pheatmap | 1.0.12 | Heatmaps |
| treemap | 2.4-4 | Treemaps |
| lattice | 0.22-6 | Trellis graphics |
~1000 CRAN packages available. Not supported: packages requiring networking (RgoogleMaps, mailR).
Full package list: https://learn.microsoft.com/power-bi/connect-data/service-r-packages-support
Desktop
Any locally installed R package works without restriction. R must be installed separately.
Best Practices
- Always call
print(p)-- ggplot2 objects require explicit printing - Guard against empty data --
if (nrow(dataset) == 0) { plot.new(); text(0.5, 0.5, "No data") } - Use index-based column access --
dataset[,1]avoids name escaping issues - Use
theme_minimal()-- clean aesthetic that works well with Power BI - Factor categorical variables -- control sort order explicitly with
factor() - Use hex colors matching the report theme
- Set margins --
plot.margin=margin(t, r, b, l)to prevent clipping - Keep scripts concise -- 5-min timeout Desktop, 1-min Service
Limitations
| Constraint | Desktop | Service |
| Output | Static PNG, 72 DPI | Static PNG, 72 DPI |
| Timeout | 5 minutes | 1 minute |
| Row limit | 150,000 | 150,000 |
| Output size | 2 MB | 30 MB |
| Networking | Unrestricted | Blocked |
| Gateway | Personal only | Personal only |
| Cross-filter FROM | Not supported | Not supported |
| Receive cross-filter | Yes | Yes |
| Publish to web | Not supported | Not supported |
| Embed (app-owns-data) | Ending May 2026 | Ending May 2026 |
Script Structure Template
library(ggplot2)
# 1. Guard against empty data
if (nrow(dataset) == 0) {
plot.new()
text(0.5, 0.5, "No data available", cex=1.5)
} else {
# 2. Data preparation (index-based access)
df <- data.frame(
category = dataset[,1],
value = dataset[,2]
)
# 3. Create visualization
p <- ggplot(df, aes(x=reorder(category, -value), y=value)) +
geom_col(fill="#5B8DBE", width=0.7) +
theme_minimal(base_size=12) +
theme(
panel.grid.major.x = element_blank(),
axis.title = element_blank()
)
# 4. Render
print(p)
}R vs Python Comparison
| Aspect | R (scriptVisual) | Python (pythonVisual) |
| Primary library | ggplot2 | matplotlib |
| Render call | print(p) | plt.show() |
| Column access | dataset[,1] or dataset$col | dataset.iloc[:,0] or dataset["col"] |
| Empty guard | if (nrow(dataset) == 0) | if len(dataset) == 0: |
| Factor control | factor(x, levels=...) | pd.Categorical(x, categories=...) |
| Runtime (Service) | R 4.3.3 | Python 3.11 |
When to Use R Visuals
R visuals are the preferred choice for statistical and analytical visualizations, particularly where R's statistical ecosystem excels. Use R visuals when you need:
- Distribution analysis (violin, ridgeline, density, boxplot)
- Statistical modeling (regression, correlation, ANOVA)
- Publication-quality analytical charts with ggplot2
- Packages like forecast, corrplot, pheatmap that have no Python equivalent of equal quality
Output is static PNG -- no cross-filtering FROM the visual, no hover/tooltip interactivity. Use Deneb instead for interactive custom visuals. Use SVG measures for simple inline graphics in tables/cards.
References
references/community-examples.md-- R Graph Gallery examples organized by chart type (distribution, correlation, ranking, evolution, flow)references/ggplot2-patterns.md-- Common ggplot2 chart patterns (bar, donut, line, heatmap, bullet)examples/script/-- Standalone R scripts (bar-chart, trend-line) -- ready to inject into visual.json after escapingexamples/visual/bullet-chart.json-- PBIR visual.json: bullet chart with conditional coloring, error handling, and extensive escapingexamples/visual/bar-chart.json-- PBIR visual.json: horizontal bar with PY comparison lines and colored account labelsexamples/visual/trend-line.json-- PBIR visual.json: area chart with ribbon plot and month factor handling
Fetching Docs
To retrieve current R visual / package support docs, use microsoft_docs_search + microsoft_docs_fetch (MCP) if available, otherwise mslearn search + mslearn fetch (CLI). Search based on the user's request and run multiple searches as needed to ensure sufficient context before proceeding.
Related Skills
pbi-report-design-- Layout and design best practicespython-visuals-- Python Script visuals (same concept, different language)deneb-visuals-- Vega/Vega-Lite visuals (interactive, vector-based alternative)svg-visuals-- SVG via DAX measures (lightweight inline graphics)pbir-format(pbip plugin) -- PBIR JSON format reference
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

