powerbi-skills

Create and modify Power BI report files in PBIR/PBIP format using the `powerbi-report-author` and `powerbi-desktop` CLIs. Use when the user wants to: (1) implement an approved report spec or design brief, (2) add or edit pages, visuals, filters, slicers, bookmarks, themes, or formatting, (3) validate PBIR and verify rendering in Power BI Desktop. For open-ended visual design, use `power-bi-report-design` first. For end-to-end requirements and approval workflow, use `powerbi-report-planning` first. Triggers: "edit PBIR", "create Power BI report page", "add visual to PBIP", "format report visual", "validate Power BI report", "reload Desktop screenshot", "implement an approved PBIP report spec", "edit PBIR pages/visuals".

Analyze business requirements and define BI strategy for Power BI projects. Use this skill whenever the user wants to analyze business requirements, identify KPIs, define what insights a report should deliver, propose dashboard structure for a business domain, or gather requirements before building a Power BI report or semantic model. Triggers include: "analyze business requirements", "what KPIs should we track", "what insights can we get", "business domain analysis", "requirements gathering", "what should we measure", "what problems can we solve", "propose a dashboard", "what reports do we need", "BI strategy", "define metrics". Do NOT use for actual model building (use power-bi-semantic-model), DAX writing (use power-bi-dax-development), or report generation (use power-bi-report-authoring).

Reference kit for the feedback and iteration phase of a Power BI project. Provides classification taxonomy, prioritization matrix, intake template, change-impact scoping, post-change validation checklist, A/B variant testing workflow, formal UAT workflow, PBIP Git diff guide, changelog template, and a performance quick-check pointer. Use this skill whenever the user provides feedback on an existing Power BI report, requests iteration, wants to run UAT, or needs to document changes. Routing (feedback → correct downstream skill) is owned by the power-bi-developer agent, not by this skill. Triggers include: "user feedback", "improve report", "fix report", "iterate on the report", "report review", "rebuild report", "UAT", "changelog", "release notes", "users are complaining", "performance issue", "add/remove/modify a page/measure/visual on an existing report". Do NOT use this skill for brand-new projects (use power-bi-business-analysis to start from scratch).

Diagnose and resolve Power BI performance issues across models, DAX queries, report visuals, and data refresh. Use this skill whenever the user reports slow report loading, slow visual interactions, long refresh times, high memory usage, query timeouts, or capacity bottlenecks. Triggers include: "report is slow", "performance issue", "optimize report", "slow loading", "query timeout", "refresh takes too long", "high memory", "report performance", "visual is slow", "optimize model", "reduce model size", "aggregation table", "incremental refresh", "Performance Analyzer", "DAX Studio", "server timings", "capacity metrics". Do NOT use for initial model design (use power-bi-semantic-model), initial DAX development (use power-bi-dax-development), or report design decisions (use power-bi-report-design). This skill is for diagnosing and fixing performance problems in existing solutions.

Design Power BI report layouts, select chart types, plan page structures, choose themes, and apply data storytelling principles BEFORE generating PBIR JSON files. Use this skill whenever the user asks to design a report, plan a dashboard layout, choose visualizations, decide on chart types, apply storytelling to data, select a theme or color palette, plan page navigation, or structure report pages for a Power BI project. Also use when the user provides requirements and needs a report design spec before generation, or when reviewing/improving an existing report's visual design, layout, or UX. This skill produces a Design Spec — a structured plan of pages, visuals, layout, theme, and navigation — that feeds into the `power-bi-report-authoring` skill for JSON generation. Do NOT use for generating PBIR JSON files, validating report structure, or building the semantic model. For JSON generation, use `power-bi-report-authoring`.

Design and build Power BI semantic models using star schema principles and the PowerBI Modeling MCP tools. Use this skill whenever the user wants to build a semantic model, create a data model, design a star schema, add tables or columns, create or modify relationships, configure storage modes (Import, DirectQuery, DirectLake, Composite), implement RLS (Row-Level Security), optimize model performance, or explore existing data sources for modeling. Triggers include: "build semantic model", "create data model", "star schema", "add table", "create relationship", "storage mode", "DirectLake", "composite model", "RLS", "optimize model", "model review", "explore data", "connect to gold layer", "extend model", "add dimension", "add fact table". Do NOT use for DAX measure creation (use power-bi-dax-development) or report generation (use power-bi-report-authoring).

Develop, optimize, and validate DAX measures, calculation groups, visual calculations, field parameters, dynamic format strings, time intelligence, semi-additive logic, virtual relationships with TREATAS, DAX window functions, and user-defined functions for Power BI semantic models. Use for requests to write or optimize DAX, create measures, explain CALCULATE or evaluation context, build YTD/YoY/WTD logic, use RUNNINGSUM or MOVINGAVERAGE, rank with RANK/ROWNUMBER/OFFSET/INDEX/WINDOW, or apply advanced DAX patterns. Research Microsoft Learn MCP before recommending patterns.