npx claudepluginhub data-goblin/power-bi-agentic-development --plugin reportsThis skill uses the workspace's default tool permissions.
> **Report modification requires tooling.** Two paths exist:
examples/spec/vega-lite/bullet-chart.jsonexamples/spec/vega-lite/kpi-card.jsonexamples/spec/vega/bar-chart.jsonexamples/spec/vega/line-chart.jsonexamples/standard-config.jsonexamples/visual/bullet-chart.jsonexamples/visual/kpi-card.jsonexamples/visual/trend-line.jsonexamples/visual/ytd-comparison.jsonexamples/visual/ytd-line-chart.jsonreferences/capabilities.mdreferences/community-examples.mdreferences/pbir-structure.mdreferences/vega-lite-patterns.mdreferences/vega-patterns.mdSearches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Guides MCP server integration in Claude Code plugins via .mcp.json or plugin.json configs for stdio, SSE, HTTP types, enabling external services as tools.
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.
Deneb is a certified custom visual for Power BI that enables Vega and Vega-Lite declarative visualization specs directly inside reports. Author specs using this skill.
Prefer Vega-Lite for new Deneb visuals unless specific Vega-only features are required (signals, event streams, custom projections, force/voronoi layouts). Vega-Lite is more concise, easier to maintain, and covers most chart types. For advanced Vega features, see references/vega-patterns.md and the Vega documentation.
deneb7E15AEF80B9E4D4F8E12924291ECE89Av6.json schema URLs)dataset role (all fields go into one "Values" well)dataLimit.override)vegaLite (default) or vega (when Vega-specific features needed)svg (default, sharp text) or canvas (better for large datasets)Register deneb7E15AEF80B9E4D4F8E12924291ECE89A in report.json publicCustomVisuals array manually. Without this, the visual shows "Can't display this visual."
For more information, use the pbir-format skill and check the report.md reference.
{
"publicCustomVisuals": ["deneb7E15AEF80B9E4D4F8E12924291ECE89A"]
}
Create the visual.json file manually (see pbir-format skill in the pbip plugin for JSON structure) with visualType: deneb7E15AEF80B9E4D4F8E12924291ECE89A, field bindings for the columns and measures you need, and position/size as required.
All fields bind to the single dataset role. Use Table.Column for columns and Table.Measure for measures. Field names in bindings must match those used in the Vega/Vega-Lite spec.
Create a Vega-Lite (or Vega) JSON spec file. Key difference:
"data": {"name": "dataset"} (object)"data": [{"name": "dataset"}] (array){
"$schema": "https://vega.github.io/schema/vega-lite/v6.json",
"data": {"name": "dataset"},
"mark": {"type": "bar", "tooltip": true},
"encoding": {
"y": {"field": "Category", "type": "nominal"},
"x": {"field": "Value", "type": "quantitative"}
}
}
See examples/spec/ for complete spec files (Vega and Vega-Lite) and examples/visual/ for full PBIR visual.json files. Field names in the spec must match the nativeQueryRef (display name) from the field bindings.
Set the spec and config in the visual's objects.vega[0].properties as single-quoted DAX literal strings. The jsonSpec property holds the Vega spec (stringified JSON), jsonConfig holds the config, and provider is set to 'vega' or 'vegaLite'. See the PBIR structure reference (references/pbir-structure.md) for the full encoding pattern.
Escaping rules for visual.json injection:
The spec JSON must be stringified into a single line and wrapped in single quotes inside the expr.Literal.Value:
"jsonSpec": {"expr": {"Literal": {"Value": "'{\"$schema\":\"...\",\"data\":{\"name\":\"dataset\"},\"marks\":[...]}'" }}}
") become \" (standard JSON string escaping)'...'datum[''Sales Amount'']examples/visual/ for complete real-world visual.json files showing this encodingBefore presenting the spec to the user, dispatch the deneb-reviewer agent to validate syntax and provide design feedback.
Validate JSON syntax with jq empty <visual.json> and inspect the visual.json to confirm spec content and field bindings.
"data": [{"name": "dataset"}] (array form)"data": {"name": "dataset"} (object form)., [, ], \, ") become _"Order Lines")Escaping depends on whether the spec is standalone or injected into a PBIR visual.json:
Standalone spec files (in examples/spec/): use double quotes with JSON escaping:
{"calculate": "datum[\"Order Lines\"] - datum[\"Order Lines (PY)\"]", "as": "diff"}
Inside PBIR visual.json (in examples/visual/): the entire spec is a single-quoted DAX literal string. Field names with spaces use doubled single quotes (''):
datum[''Order Lines''] - datum[''Order Lines (PY)'']
Single quotes that are NOT part of field name escaping (e.g., string literals in filter expressions like datum.Series == 'Actuals') work as-is because they don't conflict with the outer single-quote wrapper.
Use Deneb's built-in signals for responsive container sizing:
"width": {"signal": "pbiContainerWidth - 25"},
"height": {"signal": "pbiContainerHeight - 27"}
The offsets account for padding. For absolute positioning of text marks, use {"signal": "width"} instead of hardcoded pixel values.
Always provide a config file for consistent styling. See the Standard Config section in references/vega-patterns.md. Key settings: autosize: fit, view.stroke: transparent, font: Segoe UI.
Use Power BI theme colors instead of hardcoded hex values:
| Function/Scheme | Purpose | Usage in Vega |
|---|---|---|
pbiColor(index) | Theme color by index (0-based) | {"signal": "pbiColor(0)"} |
pbiColor(0, -0.3) | Darken theme color by 30% | Shade: -1 (dark) to 1 (light) |
pbiColor("negative") | Sentiment colors | "min", "middle", "max", "negative", "positive" |
pbiColor("bad") | Aliases for sentiment | "bad" = "negative", "good" = "positive", "neutral" = "middle" |
pbiColorNominal | Categorical palette (distinct) | "range": {"scheme": "pbiColorNominal"} |
pbiColorOrdinal | Ordinal palette (ordered categories) | "range": {"scheme": "pbiColorOrdinal"} |
pbiColorLinear | Continuous gradient | "range": {"scheme": "pbiColorLinear"} |
pbiColorDivergent | Divergent gradient | "range": {"scheme": "pbiColorDivergent"} |
Enable interactivity via the vega objects in visual.json:
| Feature | Property | Default | Notes |
|---|---|---|---|
| Tooltips | enableTooltips | true | Use "tooltip": {"signal": "datum"} in encode |
| Context menu | enableContextMenu | true | Right-click drill-through |
| Cross-filtering | enableSelection | false | Requires __selected__ handling |
| Cross-highlighting | enableHighlight | false | Creates <field>__highlight fields |
When enableSelection is true, handle __selected__ ("on", "off", "neutral") in encode blocks. Selection modes: simple (auto-resolves) or advanced (requires event definitions, Vega only). See references/vega-patterns.md for the full pattern.
Use layered marks -- background at reduced opacity, foreground shows <field>__highlight values. See references/vega-patterns.md for details.
Deneb injects runtime fields into each dataset row. See references/capabilities.md for the full table.
Key fields: __row__ (zero-based row index, replaces removed __identity__), __selected__ (selection state), <field>__highlight + <field>__highlightStatus + <field>__highlightComparator (cross-highlighting), <field>__formatted (pre-formatted value string), <field>__format (Power BI format string).
Breaking change in 1.9:
__identity__and__key__were removed. Replace anydatum.__identity__withdatum.__row__.
autosize: fit in config for responsive Power BI sizingpbiContainerWidth/pbiContainerHeight signals for responsive Vega specspbiColor, pbiColorNominal) instead of hex valuesenter/update/hover encode blocks for clean state management (Vega only)"tooltip": {"signal": "datum"} on marksdataLimit.override and use renderMode: canvas for large datasetsnativeQueryRef matches spec field referencesDeneb is the preferred choice for advanced custom visuals that need interactivity (cross-filtering, tooltips, hover effects) and go beyond what native Power BI visuals offer. Use Deneb when you need:
Use SVG measures instead for simple inline graphics in tables/cards (sparklines, data bars, progress bars) where interactivity is not needed. Use Python/R instead for statistical visualizations (distribution analysis, regression, correlation) where the focus is analytical rigor over interactivity.
references/community-examples.md -- 170+ community templates organized by chart type, with author citations and direct linksreferences/vega-patterns.md -- Vega chart patterns (bar, line, scatter, donut, stacked, heatmap, area, lollipop, bullet, KPI card), standard config, transforms and scales referencereferences/vega-lite-patterns.md -- Vega-Lite chart patterns (for editing existing Vega-Lite visuals only)references/pbir-structure.md -- PBIR JSON structure (literal encoding, query state, interactivity example)references/capabilities.md -- Full Deneb object properties reference and template formatexamples/visual/bullet-chart.json -- PBIR visual.json: faceted bullet chart with conditional indicators and cross-filtering (Vega-Lite)examples/visual/kpi-card.json -- PBIR visual.json: KPI card with layered text and conditional % change coloring (Vega-Lite)examples/visual/trend-line.json -- PBIR visual.json: dual-series line chart with fold transform and color/legend mapping (Vega-Lite)examples/visual/ytd-comparison.json -- PBIR visual.json: YTD vs target with dashed lines, endpoint labels, number formatting, and rank-based filtering (Vega-Lite)examples/spec/vega/ -- Standalone Vega spec files (bar-chart, line-chart) -- ready to inject into visual.json after escapingexamples/spec/vega-lite/ -- Standalone Vega-Lite spec files (bullet-chart, kpi-card) -- ready to inject after escapingexamples/standard-config.json -- Standard config for all Deneb specsTo retrieve current Power BI custom visual 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. Note: Vega/Vega-Lite docs live at vega.github.io (not MS Learn) -- use WebFetch for those.
pbir-format (pbip plugin) -- PBIR JSON format referencepbi-report-design -- Layout and design best practicesr-visuals -- R Script visuals (ggplot2)python-visuals -- Python Script visuals (matplotlib)svg-visuals -- SVG via DAX measures (lightweight inline graphics)