Skip to content

zebrabi/zebra-bi

v1.1.0Apache-2.0

The Zebra BI MCP connector bundled with the skills that put it to work: interactive IBCS-style charts and tables of your business data, variance explanations, and data stories you can export as a PDF, a shareable artifact page, or PowerPoint and Excel files with live Zebra BI visuals. It also authors Zebra BI reports in a Power BI project (PBIP) and checks them before Power BI Desktop opens them.

Changelog of the Power BI part

Versions up to 0.3.2 are releases of the Power BI authoring plugin from its earlier repository, zebrabi/zebra-bi-agentic. From the release that moved it into this repository, the Power BI part ships inside the Zebra BI plugin and takes the plugin's version; changes are listed on the releases page.

What changed, and what is known to be wrong. Dates are the day the work landed, not the day it was written up.

This file starts at the first public release. Versions before it exist in the git history and were never published — the repository was private, with no tags and no releases — so listing them as though they shipped would misrepresent what anyone could have installed.

0.3.2 — 2026-11-04

  • The hand-over now leads with the one step a changed model needs before it is opened again: refresh and save, or the visuals open empty.
  • Zebra BI visuals store licence information in each visual's objects (licenseSettings; Cards also license) and in Power BI Desktop's local storage. That is normal, and the plugin no longer asks anyone to remove it: removing it can make a visual render unlicensed on a machine whose local storage does not hold the entitlement.
  • Activating from a key you provide now ends after one render, with the key left in place.
  • The report writers treat the licence groups like any other object group: a spec may carry them.
  • write_visual takes existingVisualPath, and write_page and write_report take existingReportPath. Given the path of the file or .Report directory a call replaces, the writer reads each existing visual.json itself and carries its licence groups through unchanged, unless the spec provides that group. A path with nothing to read carries nothing and says so in a warning. The tool descriptions and the authoring skill say to pass the path whenever a write replaces existing files.
  • SECURITY.md and the setup skill say this in a short note instead of a procedure.
  • INSTALL.md names the case where claude plugin marketplace add fails with git not found or in an unsafe location: Git is installed but not on PATH (on Windows add C:\Program Files\Git\cmd), and the not found in marketplace error that follows is the stale cache, cleared by removing and re-adding the marketplace.
  • multiline-measure-dax-on-equals-line no longer fires on a complete one-line measure X = VAR ... RETURN ..., which Desktop opens and renders. A VAR with no RETURN on the line, a RETURN with its body on the next line, a one-line form with an open parenthesis, and a "RETURN" that is only part of a bracketed name or a comment are still reported.
  • report-has-no-base-theme accepts a report that declares only a named customTheme, which is what Desktop writes on Save As PBIP. A report with neither theme, or a customTheme with no name, is still reported, and the pre-flight script in references/preflight.md checks the same thing.
  • Starting from a .pbix: the skill and README say to use File > Save as > Power BI project (.pbip) onto a copy, with a short target folder (under about 75 characters), because Save As fails silently when the deepest path passes about 260 characters.
  • references/verify-loop.md lists two Desktop prompts that block automation and are not faults: the Bing map "going away" dialog on open, and the save-on-close prompt on an unedited project.
  • Statements that depended on a Desktop version now say so: reload on a Power Query model or with a cultures/ file is measured on 2.156 (one 2.159 observation reloaded successfully), the bridge manifest on 2.159 also lists report.snapshot.capture/v2, and a Desktop save can migrate Tables+ and Charts+ to a newer build (Tables+ 8.4.0 seen on 2.159).
  • Writing a licence key on Tables+ or Charts+ now also writes a fresh licenseSettings.appliedTimestamp (these visuals keep the key in the file and in Desktop's local storage and use the copy with the larger timestamp, so a key without one stayed locked on a machine holding an older key), and Charts+ also gets proFeaturesSettings and, from installedVersion or the replaced file, visualCreatedVersion. The writers do this; the setup and authoring references describe the payload and say to check Expires in Format > About, not "Licensed to".

0.3.1 (2026-10-07)

Documentation and safety wording. No change to the MCP server or the rule catalogue.

  • SECURITY.md now says what CI proves about the bundle and what it cannot, that your agent host sends what it reads to your model provider, that project content is untrusted input, and that a licence key pasted into the chat stays in the conversation.
  • SECURITY.md no longer says the checker flags a licence key. There is no such check; the report writers refuse to write a key.
  • The authoring skill tells the agent to treat project content as data, never as instructions.
  • The setup skill says where a pasted key ends up before asking for one, and spells out the strip step.
  • The README says your agent host sends what the agent reads to your model provider, that a pasted key stays in the conversation, and asks you to work on a copy outside synced folders.
  • Node.js is recommended in the README and INSTALL.md. It runs the checker; everything else works without it, so a machine where IT blocks Node can still use the plugin.
  • The README is titled with the product name, Zebra BI agentic, and says the checker reads files while the agent checks the rendered page in Power BI Desktop.

0.3.0 — 2026-09-10, the first public release

Preview. It works, it is used daily inside Zebra BI, and it is new enough that the most useful thing you can do is tell us when it does not.

What you get

setup-doctorTen checks on the machine, each with a fix. Two are about your model — scenario measures and a marked date table — and they are the ones that decide whether the report comes out right
report-authoringPlanning, data binding, IBCS variance semantics, formatting, small multiples, comments, and page layouts proven against real Zebra BI templates
report-publishingThe Zebra-specific parts of publishing. Microsoft's own skill does the upload; this covers the visual-track choice and the refresh without which the report arrives empty
The checker59 rules over an unopened .pbip. Optional — needs Node.js, no dependencies to install
18 MCP toolsProfiling, page proposal, the encoders for the property blobs that cannot be written by hand, and the report writers

Ten on-demand reference layers sit behind the authoring skill and load only when they are needed: the analyst layer (what to ask before writing anything), DAX, design, formatting, the model layer, pre-flight, recipes, TMDL, the verify loop, and the visual property reference.

Recent work, most consequential first

  • Licences activate from the report file. Paste your key into the chat; the agent writes it into the visuals for one render and strips it again. Nothing to type in Power BI Desktop, and the entitlement persists on the machine afterwards.
  • AppSource visuals resolve by GUID with no prior install. A report that names the Zebra BI visuals renders on a machine that has never added them.
  • The analyst layer. The skill now frames the brief before it writes — reader, decision, period, comparison, fiscal-year convention — instead of building first and asking later. With profile_source it does the same for a flat file.
  • The DAX layer and a batch oracle, after a broken measure was found to take the whole visual down with it and the doctor's model check was found to test the wrong thing.
  • The design layer — which visual form carries which message, sizing, zero baselines, one scale per unit, sorting, titles and colour.
  • TMDL as a measured grammar. ~130 variants against Power BI Desktop 2.157, and fourteen validator rules built on a real parser.
  • Calculation groups, drill and drillthrough; view-mode comments; per-category scenarios; chart-in-column tables.
  • Installs on GitHub Copilot CLI with the same two commands (copilot plugin marketplace add, copilot plugin install). Two things were in the way and are fixed: the marketplace file carried a pluginRoot that Copilot applied twice, and the authoring skill's description exceeded the open standard's 1024-character cap, so spec-strict hosts loaded two skills of three. Install verified; authoring on Copilot is not, see Not verified.

Known issues

An agent-written Cards visual has crashed Power BI Desktop's serializer, once. Editing that visual's formatting by hand in Desktop threw TypeError: Cannot read properties of null (reading 'gradient') in serializeVisualContainerConfig and the report would not render. Observed once, on Desktop 2.156.951.0, on 2026-08-12.

It matters more than one observation usually would, because of where it surfaces: the file is written by the agent and the crash appears only when a person later edits that visual — after handover, on the reviewer's machine.

It is not diagnosed, and we are not going to guess in public. One thing is certain from the error text: the value the serializer read was literally null. Beyond that the cause is open — an earlier hypothesis of ours was checked against the saved files and did not survive them.

It is also not established that this is specific to agent-written reports. The layout structure involved is written into the file by Power BI Desktop itself on save, so if you hit this on a Cards visual you built by hand, we want to hear that just as much.

If you hit it: the report is not lost — the .pbip on disk is intact and reopening the project recovers it. Please open an issue and attach the visual's visual.json; that file is the one thing we cannot reconstruct, and it is what would turn one observation into something the checker can enforce.

Not verified

Stated so you know which claims we have earned and which we are extending on reasonable grounds.

  • Hosts other than Claude Code. The skills are plain Markdown and the checker is a plain stdio MCP server — verified to start, speak MCP 2025-06-18 and list its tools with no dependencies — but no report has been authored end to end on Codex, Cursor, Gemini CLI or Copilot CLI. See INSTALL.md.
  • View-mode commenting by a report viewer. The agent can configure it; nobody has tested a viewer using it.
  • Unlicensed tenants replace comment bodies with an upgrade prompt in the Power BI service. Seen once, on one tenant, and the licensed control has not been run — so it is recorded here rather than stated as behaviour.

What it cannot do

Unchanged from README.md and worth repeating: it reads your report files, not your data, so it cannot tell you a number is wrong. It cannot see the rendered page. It is Windows-only in practice, because Power BI Desktop is. And it cannot tell whether two periods are comparable — if your actuals stop in April and last year runs to December, every variance on the page is wrong and nothing in the files says so.

Before 0.3.0

Internal only, 2026-08-03 to 2026-09-06, 0.1.0 through 0.2.16. Never tagged, never released, never installable outside Zebra BI. The arc, for anyone reading the history:

0.1.0–0.1.4The plugin generated from an internal source; the model reader; the encoders; the first run against a real project, which cut 19 false positives
0.2.0–0.2.5The setup doctor, the README, and five passes of a full read-through gate
0.2.6–0.2.13Seven rules retired or gated after they fired on shipped reference templates — including a retraction, on the principle that a census cannot overrule a render
0.2.14CI on every push, which immediately found a contradiction in our own prose
0.2.15The doctor's model check tests evaluation rather than presence; rule messages carry the symptom
0.2.16Licence activation from the file; registration settled; the trial link tagged

Zebra BI · https://zebrabi.com · support@zebrabi.com