deneb-visuals
Deneb visual creation, Vega/Vega-Lite spec authoring, and Deneb best practices for PBIR reports. Automatically invoke whenever the user mentions "Deneb" in any context, or asks about Vega/Vega-Lite specs in Power BI, Deneb cross-filtering, Deneb interactivity, pbiColor theme integration, Deneb field name escaping, or Deneb rendering issues.
npx skills add data-goblin/power-bi-agentic-development --skill deneb-visuals --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Deneb Visuals in Power BI (PBIR) > **Use `pbir` for every report mutation.** Read PBIR metadata only for diagnosis. If `pbir` is > unavailable or lacks an operation, stop and report the gap; never edit report JSON directly. 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. ## Provider Policy **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](https://vega.github.io/vega/docs/). ## Visual Identity - **visualType:** `deneb7E15AEF80B9E4D4F8E12924291ECE89A` - **Bundled runtime:** Vega 6.2.0 / Vega-Lite 6.4.1 (since Deneb 1.8; use `v6.json` schema URLs) - **Data role:** Single `dataset` role (all fields go into one "Values" well) - **Default row limit:** 10,000 rows (override via `dataLimit.override`) - **Provider:** `vegaLite` (default) or `vega` (when Vega-specific features needed) - **Render mode
- Provider Policy
- Visual Identity
- Custom Visual Registration (Required)
- Workflow: Creating a Deneb Visual
- Step 1: Add the Visual
- Step 2: Write the Spec
- Step 3: Inject the Spec
- Step 3b: Review
- Step 4: Validate
- Spec Authoring Rules
- Data Binding
- Field Name Escaping in Expressions (Critical)
- Responsive Sizing (Vega)
- Config (Separate from Spec)
pbir add visual deneb7E15AEF80B9E4D4F8E12924291ECE89A \ pbir visuals bind "Report.Report/Page.Page/RevenueByCategoryDeneb.Visual" \ pbir visuals deneb "Report.Report/Page.Page/RevenueByCategoryDeneb.Visual" \ pbir visuals bind "Report.Report/Page.Page/RevenueByCategoryDeneb.Visual" --show pbir validate "Report.Report" --all
What does the deneb-visuals skill do?
Deneb visual creation, Vega/Vega-Lite spec authoring, and Deneb best practices for PBIR reports. Automatically invoke whenever the user mentions "Deneb" in any context, or asks about Vega/Vega-Lite specs in Power BI, Deneb cross-filtering, Deneb interactivity, pbiColor theme integration, Deneb field name escaping, or Deneb rendering issues.
How do I install it?
Run `npx skills add data-goblin/power-bi-agentic-development --skill deneb-visuals --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From data-goblin/power-bi-agentic-development, a repository with 833 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.