MCPInstall

power-bi-model-design-review

Comprehensive Power BI data model design review prompt for evaluating model architecture, relationships, and optimization opportunities.

Installs
9K
Last 24h
—
Trending rank
—
Security
Warn

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/github/awesome-copilot --skill power-bi-model-design-review
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads power-bi-model-design-review automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

Security audits

Independent scans of the skill's instructions and bundled files.

Gen Agent Trust Hub PassSAFE ·The analyzed skill is safe. It acts purely as a structured prompt framework for conducting Power BI data model design reviews, containing no code scripts, external references, dependencies, or malicious behavior.
Socket PassNo alerts
Snyk PassLOW ·Risk: LOW · No issues
Runlayer WarnMEDIUM ·1/1 file flagged
ZeroLeaks PassNONE ·Score: 93/100 · 2 sections analyzed

SKILL.md

The instructions your agent reads when the skill is triggered.

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

Scalability Considerations:
- Growth projection accommodation
- Refresh performance requirements
- Query performance expectations
- Concurrent user capacity planning

B. Query Performance Analysis

Performance 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 strategies

Phase 3: Maintainability and Governance Review

A. Model Maintainability Assessment

Maintainability 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 plans

B. Security and Compliance Review

Security 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 measures

Review Output Structure

Executive Summary Template

Data 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)

Detailed Review Report

Schema Architecture Section

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 readiness

Specific Recommendations

For 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

Review Checklist Templates

Quick Assessment Checklist (30-minute review)

□ 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 present

Comprehensive Review Checklist (4-8 hour review)

Architecture & 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 readiness

Specialized Review Types

Pre-Production Review

Focus 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 plan

Performance Optimization Review

Focus 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 criteria

Modernization Assessment

Focus 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 recommendations

Usage Instructions: To request a data model review, provide:

  • Model description and business purpose
  • Current architecture overview (tables, relationships)
  • Performance requirements and constraints
  • Known issues or concerns
  • Specific review focus areas or objectives
  • Available time/resource constraints for implementation

I'll conduct a thorough review following this framework and provide specific, actionable recommendations tailored to your model and requirements.

FAQ

What does the power-bi-model-design-review skill do?

Comprehensive Power BI data model design review prompt for evaluating model architecture, relationships, and optimization opportunities.

How do I install power-bi-model-design-review?

Run npx skills add https://github.com/github/awesome-copilot --skill power-bi-model-design-review in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/power-bi-model-design-review/ (personal) or .claude/skills/power-bi-model-design-review/ (project).

Which AI agents can use power-bi-model-design-review?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is power-bi-model-design-review safe to install?

Security partners have reviewed it: Gen Agent Trust Hub passed; Socket passed; Snyk passed; Runlayer flagged items to review; ZeroLeaks passed. As with any skill, read the SKILL.md and bundled scripts before installing.

Who maintains power-bi-model-design-review?

It is published by github in github/awesome-copilot, and it is an official skill from the maker of the technology it covers. It has 8,962 recorded installs.

More from github/awesome-copilot

View all →

git-commit

github/awesome-copilot

Use this skill when the user wants to make a Git commit or split changes into more than one commit. Also use it when the user types "/commit" or asks for a conventional commit. The skill examines the diff, stages the related files, writes a Conventional Commits message, and runs git commit. Do not use it when the user wants only a commit message and no commit. Do not use it to push, open a pull request, rebase, or change the commit history.

OfficialCode Quality & Workflow47.4K installs

excalidraw-diagram-generator

github/awesome-copilot

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

OfficialDocs & Writing31.9K installs

multi-stage-dockerfile

github/awesome-copilot

Create optimized multi-stage Dockerfiles for any language or framework

Official29.8K installs

documentation-writer

github/awesome-copilot

Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.

OfficialDocs & Writing27.9K installs

prd

github/awesome-copilot

Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

Official24.1K installs

refactor

github/awesome-copilot

Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

OfficialCode Quality & Workflow22.4K installs

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.