modifying-theme-json
Design, enforce, audit, and validate Power BI report themes through the pbir CLI. Invoke when a report uses a default or minimal theme, visuals have inconsistent formatting or many local overrides, or the user asks to create, copy, apply, standardize, rebrand, audit, or validate a theme; change theme colors or typography; promote visual formatting into the theme; clear overrides; or improve theme compliance.
npx skills add data-goblin/power-bi-agentic-development --skill modifying-theme-json --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.
# Power BI report themes Use this skill for theme design and compliance decisions. Use the `pbir-cli` skill for command details. ## Non-negotiable tooling rule Use `pbir` for every report and theme mutation. Never edit `theme.json`, `visual.json`, serialized `.Theme` fragments, or other report JSON directly. Never fall back to `jq`, shell replacement, or a JSON-editing skill. If `pbir` lacks the required operation, stop and report the missing capability. Read JSON only through `pbir cat`, `pbir get`, or read-only examples. Prefer structured CLI inspection commands because they explain the formatting cascade and usage. ## Why themes matter A theme centralizes formatting that would otherwise drift across visuals. It should own repeated choices such as: - Data-series palette and semantic good/neutral/bad colors - Background, foreground, structural, gradient, hyperlink, and null colors - Font family, size, weight, and hierarchy - Wildcard container defaults such as titles, borders, padding, and shadows - Visual-type defaults for cards, slicers, charts, tables, textboxes, and images Visual-level overrides should remain only for content-specific exceptions or conditional formatting. Them
- Non-negotiable tooling rule
- Why themes matter
- Formatting cascade
- Audit before changing
- Design rules
- Author through pbir
- Promote a good visual into the theme
- Enforce theme inheritance
- Copy or replace a theme
- Validate and render
- Detailed references
pbir theme colors "Report.Report" pbir theme fonts "Report.Report" pbir color list "Report.Report" pbir fonts list "Report.Report" pbir visuals format "Report.Report/Page.Page/Visual.Visual" pbir bpa run "Report.Report" Apply a known base when requested pbir theme list-templates pbir theme apply-template "Report.Report" sqlbi Set palette and semantic colors
What does the modifying-theme-json skill do?
Design, enforce, audit, and validate Power BI report themes through the pbir CLI. Invoke when a report uses a default or minimal theme, visuals have inconsistent formatting or many local overrides, or the user asks to create, copy, apply, standardize, rebrand, audit, or validate a theme; change theme colors or typography; promote visual formatting into the theme; clear overrides; or improve theme compliance.
How do I install it?
Run `npx skills add data-goblin/power-bi-agentic-development --skill modifying-theme-json --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.