powerbi-motionlisted

# Power BI Motion Pipeline: **discover → propose → render**, human-in-the-loop at propose. Never render before the user approves the storyboard. ## Output discipline (governs every turn) This skill produces one MP4, not prose. Per turn the ONLY visible outputs are: - Stage 2: one framing line (≤ 12 words) + the interactive storyboard widget. Nothing else — no data summaries, no interim findings, no recommendations on which to pick, no commentary after the widget. - Stage 3: one sentence confirming what was produced + the file link (`present_files`) + one next-step line only if the user must act. - A short blocker line only if something real is missing (no MCP, no data, no candidates, no ffmpeg). Do Stage 1 silently. If a measure is broken, it becomes a storyboard candidate — that IS the surfacing. Target under 200 tokens of visible text for Stage 1+2. If the user asks for analysis/summary of the report instead of animation, this skill is the wrong tool — answer normally without this pipeline. ## Prerequisites (verify, then stop if missing) 1. **Power BI MCP** connected (`powerbi-modeling-mcp:*` local, or the Remote MCP for published models). Never invent data if absent. 2. **Pillow** (`pip install pillow --break-system-packages`) and **ffmpeg** on PATH. That's the entire dependency chain — there is no Node, no npx, no browser, no HyperFrames anymore (see `references/limitations.md` for why that was retired). Report missing prerequisites as one combined message and wait