What problem does it solve? Teams wiring Microsoft's official Power BI MCP servers into a Seshat BI workspace risk unsafe configurations, unverified prerequisites, and accidental mutation paths. This Skill provides a governed, read-only doctor that maps tasks to the correct Power BI surface, generates secret-scanned config templates, and runs safe preflight checks without ever granting approvals or mutating models. ## Core Features & Use Cases - Environment Doctor: Maps a task intent (model-edit, published-query, report-authoring, and more) to the governed Power BI surface, reporting recommendations, missing prerequisites, and the next named-human step. - Safe Config Generation: Produces placeholder-only, read-only .mcp.json templates that are secret-scanned before emission and refuse to overwrite existing files. - Read-Only Preflight: Validates runtime availability, refuses write-mode configs and --skipconfirmation, and gracefully skips when no MCP runtime is installed. - Use Case: A developer asks how to query a published semantic model from their agent harness; the doctor checks tenant prerequisites (preview setting, Build permission, Copilot license) and either names the missing prerequisite or records a write-once advisory at .seshat/powerbi-mcp-recommendation.yaml. ## Quick Start Ask the assistant to run the Power BI MCP doctor for your repo with an intent such as published-query to see which official MCP server fits and what prerequisites are missing.
