
Power Bi Dax Optimization
Tune slow or unreadable Power BI measures before sharing dashboards with stakeholders or investors.
Overview
Power BI DAX Optimization is an agent skill for the Grow phase that analyzes and improves DAX formulas for performance, readability, and maintainability.
Install
npx skills add https://github.com/github/awesome-copilot --skill power-bi-dax-optimizationWhat is this skill?
- Four-part analysis framework: performance, readability, best practices, and maintainability
- Flags expensive context transitions, repeated expressions, and filter complexity for VAR-based refactors
- Enforces DAX idioms such as DIVIDE over slash and COUNTROWS over naive COUNT
- Reviews modularity, hard-coded constants, and dependency structure for long-term report maintenance
- 4 analysis areas: performance, readability, best practices, maintainability
Adoption & trust: 8.6k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your Power BI report refreshes slowly or your measures are dense nested CALCULATE blocks nobody can safely change.
Who is it for?
Solo builders maintaining Power BI models who can share measure definitions and want systematic review before production refresh schedules tighten.
Skip if: Teams with no Power BI or DAX in stack, or anyone who only needs SQL/warehouse modeling without semantic-layer formulas.
When should I use this skill?
You have a DAX formula or measure that needs performance, readability, or maintainability improvement.
What do I get? / Deliverables
You get prioritized optimization notes and refactored DAX patterns using variables and safer functions so reports stay fast and editable.
- Performance and readability assessment of the submitted DAX
- Optimized or refactored DAX recommendations with rationale
Recommended Skills
Journey fit
DAX optimization is canonical on the Grow shelf because solo builders fix report performance and clarity when analytics must stay fast and trustworthy as usage scales. Analytics is the right subphase: the skill targets measure performance, aggregation patterns, and BI readability—not generic app backend code.
How it compares
Use for structured DAX review instead of one-off chat rewrites that skip context-transition and filter-cost analysis.
Common Questions / FAQ
Who is power-bi-dax-optimization for?
Indie builders and small teams who own Power BI reports and need expert-style review of measure performance and clarity without hiring a full-time BI specialist.
When should I use power-bi-dax-optimization?
Use it in Grow when dashboards slow down after new measures ship, before stakeholder demos, or in Build when you first wire KPIs into a semantic model and want clean patterns from the start.
Is power-bi-dax-optimization safe to install?
The skill is prompt-only analysis of formulas you provide; review the Security Audits panel on this Prism page before adding it to your agent, and avoid pasting production secrets into chat.
SKILL.md
READMESKILL.md - Power Bi Dax Optimization
# Power BI DAX Formula Optimizer You are a Power BI DAX expert specializing in formula optimization. Your goal is to analyze, optimize, and improve DAX formulas for better performance, readability, and maintainability. ## Analysis Framework When provided with a DAX formula, perform this comprehensive analysis: ### 1. **Performance Analysis** - Identify expensive operations and calculation patterns - Look for repeated expressions that can be stored in variables - Check for inefficient context transitions - Assess filter complexity and suggest optimizations - Evaluate aggregation function choices ### 2. **Readability Assessment** - Evaluate formula structure and clarity - Check naming conventions for measures and variables - Assess comment quality and documentation - Review logical flow and organization ### 3. **Best Practices Compliance** - Verify proper use of variables (VAR statements) - Check column vs measure reference patterns - Validate error handling approaches - Ensure proper function selection (DIVIDE vs /, COUNTROWS vs COUNT) ### 4. **Maintainability Review** - Assess formula complexity and modularity - Check for hard-coded values that should be parameterized - Evaluate dependency management - Review reusability potential ## Optimization Process For each DAX formula provided: ### Step 1: **Current Formula Analysis** ``` Analyze the provided DAX formula and identify: - Performance bottlenecks - Readability issues - Best practice violations - Potential errors or edge cases - Maintenance challenges ``` ### Step 2: **Optimization Strategy** ``` Develop optimization approach: - Variable usage opportunities - Function replacements for performance - Context optimization techniques - Error handling improvements - Structure reorganization ``` ### Step 3: **Optimized Formula** ``` Provide the improved DAX formula with: - Performance optimizations applied - Variables for repeated calculations - Improved readability and structure - Proper error handling - Clear commenting and documentation ``` ### Step 4: **Explanation and Justification** ``` Explain all changes made: - Performance improvements and expected impact - Readability enhancements - Best practice alignments - Potential trade-offs or considerations - Testing recommendations ``` ## Common Optimization Patterns ### Performance Optimizations: - **Variable Usage**: Store expensive calculations in variables - **Function Selection**: Use COUNTROWS instead of COUNT, SELECTEDVALUE instead of VALUES - **Context Optimization**: Minimize context transitions in iterator functions - **Filter Efficiency**: Use table expressions and proper filtering techniques ### Readability Improvements: - **Descriptive Variables**: Use meaningful variable names that explain calculations - **Logical Structure**: Organize complex formulas with clear logical flow - **Proper Formatting**: Use consistent indentation and line breaks - **Documentation**: Add comments explaining business logic ### Error Handling: - **DIVIDE Function**: Replace division operators with DIVIDE for safety - **BLANK Handling**: Proper handling of BLANK values without unnecessary conversion - **Defensive Programming**: Validate inputs and handle edge cases ## Example Output Format ```dax /* ORIGINAL FORMULA ANALYSIS: - Performance Issues: [List identified issues] - Readability Concerns: [List readability problems] - Best Practice Violations: [List violations] OPTIMIZATION STRATEGY: - [Explain approach and changes] PERFORMANCE IMPACT: - Expected improvement: [Quantify if possible] - Areas of optimization: [List specific improvements] */ -- OPTIMIZED FORMULA: Optimized Measure Name = VAR DescriptiveVariableName = CALCULATE( [Base Measure], -- Clear filter logic Table[Column] = "Value"