
Power Bi Model Design Review
Run a structured Power BI star-schema and relationship review so analytics models stay performant before reports ship.
Overview
Power BI Model Design Review is an agent skill most often used in Grow (also Build backend, Ship review) that runs a structured expert review of Power BI star schema, relationships, and optimization opportunities.
Install
npx skills add https://github.com/github/awesome-copilot --skill power-bi-model-design-reviewWhat is this skill?
- Star schema compliance checklist: facts, dimensions, grain, bridge tables
- Relationship evaluation for cardinality, filter direction, and circular paths
- Table design quality gates for naming, types, keys, and documentation
- Performance and optimization dimension in the review framework
- Acts as expert reviewer persona for scalable Power BI data models
- 4 primary review dimensions including schema architecture and relationship design
- Checkbox-style gates for star schema compliance and relationship quality
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 model has creeping snowflake joins, ambiguous grains, and relationship settings you are afraid to change without a systematic audit.
Who is it for?
Indie analytics owners or small teams maintaining Power BI datasets who need a repeatable modeling audit prompt.
Skip if: Teams not using Power BI, pure app-event pipelines with no semantic model, or beginners who have not imported any tables yet.
When should I use this skill?
You need a comprehensive Power BI data model design review evaluating architecture, relationships, and optimization opportunities.
What do I get? / Deliverables
You get a prioritized modeling review with explicit pass/fail style checks across schema, relationships, and performance so you can refactor before reports break.
- Structured modeling review with checklist findings
- Prioritized optimization and relationship remediation notes
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Grow analytics because the skill optimizes models that power dashboards and lifecycle metrics after data exists. Content targets fact/dimension design, relationships, and DAX-friendly grains—the analytics subphase of compounding insight.
Where it fits
You finished staging tables and want the agent to verify fact grain and dimension roles before import.
You are about to publish a dataset to a shared workspace and need a relationship and filter-direction audit.
Revenue dashboards show inflated totals and you suspect many-to-many bridges or bi-directional filters.
Refresh times spiked and you want modeling hypotheses before tuning partitions or aggregations.
How it compares
Use as a human-in-the-loop modeling review prompt, not as an automatic Tabular Editor or VertiPaq telemetry substitute.
Common Questions / FAQ
Who is power-bi-model-design-review for?
Solo builders and small teams responsible for Power BI semantic models who want structured design feedback without hiring a dedicated BI architect for every iteration.
When should I use power-bi-model-design-review?
While shaping warehouse tables in Build, before publishing a dataset in Ship, or during Grow when dashboard DAX slows down or filter context behaves unexpectedly.
Is power-bi-model-design-review safe to install?
The skill only supplies review instructions; avoid pasting production credentials into chats and check the Security Audits panel on this Prism page for the package source.
SKILL.md
READMESKILL.md - Power Bi Model Design Review
# Power BI Data Model Design Review 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. ## Review Framework ### **Comprehensive Model Assessment** When reviewing a Power BI data model, conduct analysis across these key dimensions: #### 1. **Schema Architecture Review** ``` 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 descriptions ``` #### 2. **Relationship Design Evaluation** ``` Relationship 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 relationships ``` #### 3. **Storage Mode Strategy Review** ``` Storage 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 beneficial ``` ## Detailed Review Process ### **Phase 1: Model Architecture Analysis** #### A. **Schema Design Assessment** ``` Evaluate 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 evaluation ``` #### B. **Data Quality and Integrity Review** ``` Data 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 correctness ``` ### **Phase 2: Performance and Scalability Review** #### A. **Model Size and Efficiency Analysis** ``` Size 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 Scalab