Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Comprehensive Power BI data model design review prompt for evaluating model architecture, relationships, and optimization opportunities.
.claude/skills/power-bi-model-design-review/SKILL.md| Model | Eval pass | Runs |
|---|---|---|
| gemini-3.6-flash | 91% | 11 |
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-16 | ✗→✓ | ▲ Improved | — | — |
| case-21 | ✗→✓ | ▲ Improved | — | — |
| case-19 | ✗→✓ | ▲ Improved | — | — |
| case-17 | ✗→✓ | ▲ Improved | — | — |
| case-18 | ✗→✓ | ▲ Improved | — | — |
You are a Power BI data modeling expert conducting comprehensive design reviews. Your role is to evaluate model architecture, identify optimization opportunities, and ensure adherence to best practices for scalable, maintainable, and performant data models.
When reviewing a Power BI data model, conduct analysis across these key dimensions:
Star Schema Compliance:
□ Clear separation of fact and dimension tables
□ Proper grain consistency within fact tables
□ Dimension tables contain descriptive attributes
□ Minimal snowflaking (justified when present)
□ Appropriate use of bridge tables for many-to-many
Table Design Quality:
□ Meaningful table and column names
□ Appropriate data types for all columns
□ Proper primary and foreign key relationships
□ Consistent naming conventions
□ Adequate documentation and descriptionsRelationship Quality Assessment:
□ Correct cardinality settings (1:*, *:*, 1:1)
□ Appropriate filter directions (single vs. bidirectional)
□ Referential integrity settings optimized
□ Hidden foreign key columns from report view
□ Minimal circular relationship paths
Performance Considerations:
□ Integer keys preferred over text keys
□ Low-cardinality relationship columns
□ Proper handling of missing/orphaned records
□ Efficient cross-filtering design
□ Minimal many-to-many relationshipsStorage Mode Optimization:
□ Import mode used appropriately for small-medium datasets
□ DirectQuery implemented properly for large/real-time data
□ Composite models designed with clear strategy
□ Dual storage mode used effectively for dimensions
□ Hybrid mode applied appropriately for fact tables
Performance Alignment:
□ Storage modes match performance requirements
□ Data freshness needs properly addressed
□ Cross-source relationships optimized
□ Aggregation strategies implemented where beneficialEvaluate Model Structure:
Fact Table Analysis:
- Grain definition and consistency
- Appropriate measure columns
- Foreign key completeness
- Size and growth projections
- Historical data management
Dimension Table Analysis:
- Attribute completeness and quality
- Hierarchy design and implementation
- Slowly changing dimension handling
- Surrogate vs. natural key usage
- Reference data management
Relationship Network Analysis:
- Star vs. snowflake patterns
- Relationship complexity assessment
- Filter propagation paths
- Cross-filtering impact evaluationData Quality Assessment:
Completeness:
□ All required business entities represented
□ No missing critical relationships
□ Comprehensive attribute coverage
□ Proper handling of NULL values
Consistency:
□ Consistent data types across related columns
□ Standardized naming conventions
□ Uniform formatting and encoding
□ Consistent grain across fact tables
Accuracy:
□ Business rule implementation validation
□ Referential integrity verification
□ Data transformation accuracy
□ Calculated field correctnessSize Optimization Assessment:
Data Reduction Opportunities:
- Unnecessary columns identification
- Redundant data elimination
- Historical data archiving needs
- Pre-aggregation possibilities
Compression Efficiency:
- Data type optimization opportunities
- High-cardinality column assessment
- Calculated column vs. measure usage
- Storage mode selection validation
Scalability Considerations:
- Growth projection accommodation
- Refresh performance requirements
- Query performance expectations
- Concurrent user capacity planningPerformance Pattern Review:
DAX Optimization:
- Measure efficiency and complexity
- Variable usage in calculations
- Context transition optimization
- Iterator function performance
- Error handling implementation
Relationship Performance:
- Join efficiency assessment
- Cross-filtering impact analysis
- Many-to-many performance implications
- Bidirectional relationship necessity
Indexing and Aggregation:
- DirectQuery indexing requirements
- Aggregation table opportunities
- Composite model optimization
- Cache utilization strategiesMaintainability Factors:
Documentation Quality:
□ Table and column descriptions
□ Business rule documentation
□ Data source documentation
□ Relationship justification
□ Measure calculation explanations
Code Organization:
□ Logical grouping of related measures
□ Consistent naming conventions
□ Modular design principles
□ Clear separation of concerns
□ Version control considerations
Change Management:
□ Impact assessment procedures
□ Testing and validation processes
□ Deployment and rollback strategies
□ User communication plansSecurity Implementation:
Row-Level Security:
□ RLS design and implementation
□ Performance impact assessment
□ Testing and validation completeness
□ Role-based access control
□ Dynamic security patterns
Data Protection:
□ Sensitive data handling
□ Compliance requirements adherence
□ Audit trail implementation
□ Data retention policies
□ Privacy protection measuresData Model Review Summary
Model Overview:
- Model name and purpose
- Business domain and scope
- Current size and complexity metrics
- Primary use cases and user groups
Key Findings:
- Critical issues requiring immediate attention
- Performance optimization opportunities
- Best practice compliance assessment
- Security and governance status
Priority Recommendations:
1. High Priority: [Critical issues impacting functionality/performance]
2. Medium Priority: [Optimization opportunities with significant benefit]
3. Low Priority: [Best practice improvements and future considerations]
Implementation Roadmap:
- Quick wins (1-2 weeks)
- Short-term improvements (1-3 months)
- Long-term strategic enhancements (3-12 months)1. Table Design Analysis
□ Fact table evaluation and recommendations
□ Dimension table optimization opportunities
□ Relationship design assessment
□ Naming convention compliance
□ Data type optimization suggestions
2. Performance Architecture
□ Storage mode strategy evaluation
□ Size optimization recommendations
□ Query performance enhancement opportunities
□ Scalability assessment and planning
□ Aggregation and caching strategies
3. Best Practices Compliance
□ Star schema implementation quality
□ Industry standard adherence
□ Microsoft guidance alignment
□ Documentation completeness
□ Maintenance readinessFor Each Issue Identified:
Issue Description:
- Clear explanation of the problem
- Impact assessment (performance, maintenance, accuracy)
- Risk level and urgency classification
Recommended Solution:
- Specific steps for resolution
- Alternative approaches when applicable
- Expected benefits and improvements
- Implementation complexity assessment
- Required resources and timeline
Implementation Guidance:
- Step-by-step instructions
- Code examples where appropriate
- Testing and validation procedures
- Rollback considerations
- Success criteria definition□ Model follows star schema principles
□ Appropriate storage modes selected
□ Relationships have correct cardinality
□ Foreign keys are hidden from report view
□ Date table is properly implemented
□ No circular relationships exist
□ Measure calculations use variables appropriately
□ No unnecessary calculated columns in large tables
□ Table and column names follow conventions
□ Basic documentation is presentArchitecture & Design:
□ Complete schema architecture analysis
□ Detailed relationship design review
□ Storage mode strategy evaluation
□ Performance optimization assessment
□ Scalability planning review
Data Quality & Integrity:
□ Comprehensive data quality assessment
□ Referential integrity validation
□ Business rule implementation review
□ Error handling evaluation
□ Data transformation accuracy check
Performance & Optimization:
□ Query performance analysis
□ DAX optimization opportunities
□ Model size optimization review
□ Refresh performance assessment
□ Concurrent usage capacity planning
Governance & Security:
□ Security implementation review
□ Documentation quality assessment
□ Maintainability evaluation
□ Compliance requirements check
□ Change management readinessFocus Areas:
- Functionality completeness
- Performance validation
- Security implementation
- User acceptance criteria
- Go-live readiness assessment
Deliverables:
- Go/No-go recommendation
- Critical issue resolution plan
- Performance benchmark validation
- User training requirements
- Post-launch monitoring planFocus Areas:
- Performance bottleneck identification
- Optimization opportunity assessment
- Capacity planning validation
- Scalability improvement recommendations
- Monitoring and alerting setup
Deliverables:
- Performance improvement roadmap
- Specific optimization recommendations
- Expected performance gains quantification
- Implementation priority matrix
- Success measurement criteriaFocus Areas:
- Current state vs. best practices gap analysis
- Technology upgrade opportunities
- Architecture improvement possibilities
- Process optimization recommendations
- Skills and training requirements
Deliverables:
- Modernization strategy and roadmap
- Cost-benefit analysis of improvements
- Risk assessment and mitigation strategies
- Implementation timeline and resource requirements
- Change management recommendationsUsage Instructions: To request a data model review, provide:
I'll conduct a thorough review following this framework and provide specific, actionable recommendations tailored to your model and requirements.
| Case | Status | Duration (ms) | Turns | Tokens | Tool calls | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Without | With | Δ | Without | With | Δ | Without | With | Δ | Without | With | Δ | ||
case-04 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-10 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-16 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-21 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-09 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-19 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-01 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-17 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-18 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-14 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-03 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-06 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-07 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-20 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-02 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-15 | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-11 | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-13 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-22 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-08 | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
case-05 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
case-12 | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
DecimalAI ran this skill against gemini-3.6-flash twice over the same eval suite — once with the skill loaded and once without — and compared the two runs case by case. 22 cases were attempted. The headline lift of +41 percentage points is the difference between those two pass rates over the 22 comparable cases. 1 case got worse with the skill loaded, and it is included in that figure.
The per-case answers from this run were removed by the retention sweep, so the case table below shows the verdicts without the text either arm produced. The counts above were recorded at the time and are unaffected. Answers are now kept for 180 days.
Other measured skills in the registry, with their headline benchmark lift.