Powerbi Modeling
GitHubOfficialFirst committed by AlahmadiQ8Distributed by GitHub
- Skill
- Tool integration
- Data and AI
- MIT
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The Power BI Modeling assistant helps users design and maintain efficient semantic models. It enforces Microsoft best practices by connecting directly to active models to analyze structure, relationships, and DAX measures. The skill provides guidance on star schema design, performance tuning, row-level security, and naming conventions, ensuring models are well-documented and optimized for report performance.
What it does
- Connects to active Power BI models to inspect tables, relationships, and measures.
- Provides guidance on designing star schemas and configuring model relationships.
- Assists in writing and optimizing DAX measures and calculated columns.
- Implements row-level security and model documentation standards.
- Offers performance tuning advice, including data reduction and column optimization.
- Validates models against established naming conventions and best practices.
When to use it
- When creating a new Power BI semantic model from scratch.
- When troubleshooting performance issues in an existing model.
- When needing to define complex DAX measures or calculation groups.
- When standardizing naming conventions and documentation across a model.
- When configuring security roles or complex relationship cardinalities.
Advantages
- Ensures adherence to official Microsoft Power BI modeling best practices.
- Automates the inspection of model health and structure.
- Reduces manual effort in documenting and organizing semantic models.
- Provides actionable performance optimization techniques for DAX and data structures.
- Maintains consistency through standardized naming and folder organization.
Usage examples
- “Create a new measure for Total Sales with a currency format and description.”
- The agent will use measure_operations to create the 'Total Sales' measure with the specified expression, format string, and documentation.
- “Analyze my current model and suggest performance improvements.”
- The agent will list tables, relationships, and measures, then identify opportunities like removing unused columns or optimizing relationship cardinalities.
- “How should I name my dimension and fact tables?”
- The agent will provide the recommended naming conventions, such as using singular nouns for dimensions and business process names for fact tables.
- “Create a relationship between my Sales and Customer tables.”
- The agent will verify the columns and use relationship_operations to establish a one-to-many relationship with the correct cross-filtering behavior.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/github/powerbi-modeling/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip powerbi-modeling.zip -d .agents/skills
Documentation by AlahmadiQ8
Power BI Semantic Modeling
Guide users in building optimized, well-documented Power BI semantic models following Microsoft best practices.
When to Use This Skill
Use this skill when users ask about:
Creating or optimizing Power BI semantic models
Designing star schemas (dimension/fact tables)
Writing DAX measures or calculated columns
Configuring table relationships (cardinality, cross-filter)
Implementing row-level security (RLS)
Naming conventions for tables, columns, measures
Adding descriptions and documentation to models
Performance tuning and optimization
Calculation groups and field parameters
Model validation and best practice checks
Trigger phrases: "create a measure", "add relationship", "star schema", "optimize model", "DAX formula", "RLS", "naming convention", "model documentation", "cardinality", "cross-filter"
Prerequisites
Required Tools
Power BI Modeling MCP Server: Required for connecting to and modifying semantic models
Enables: connection_operations, table_operations, measure_operations, relationship_operations, etc.
Must be configured and running to interact with models
Optional Dependencies
Microsoft Learn MCP Server: Recommended for researching latest best practices
Enables: microsoft_docs_search, microsoft_docs_fetch
Use for complex scenarios, new features, and official documentation
Workflow
1. Connect and Analyze First
Before providing any modeling guidance, always examine the current model state:
1. List connections: connection_operations(operation: "ListConnections")
2. If no connection, check for local instances: connection_operations(operation: "ListLocalInstances")
3. Connect to the model (Desktop or Fabric)
4. Get model overview: model_operations(operation: "Get")
5. List tables: table_operations(operation: "List")
6. List relationships: relationship_operations(operation: "List")
7. List measures: measure_operations(operation: "List")2. Evaluate Model Health
After connecting, assess the model against best practices:
Star Schema: Are tables properly classified as dimension or fact?
Relationships: Correct cardinality? Minimal bidirectional filters?
Naming: Human-readable, consistent naming conventions?
Documentation: Do tables, columns, measures have descriptions?
Measures: Explicit measures for key calculations?
Hidden Fields: Are technical columns hidden from report view?
3. Provide Targeted Guidance
Based on analysis, guide improvements using references:
Star schema design: See STAR-SCHEMA.md
Relationship configuration: See RELATIONSHIPS.md
DAX measures and naming: See MEASURES-DAX.md
Performance optimization: See PERFORMANCE.md
Row-level security: See RLS.md
Quick Reference: Model Quality Checklist
| Area | Best Practice |
|---|---|
| Tables | Clear dimension vs fact classification |
| Naming | Human-readable: Customer Name not CUST_NM |
| Descriptions | All tables, columns, measures documented |
| Measures | Explicit DAX measures for business metrics |
| Relationships | One-to-many from dimension to fact |
| Cross-filter | Single direction unless specifically needed |
| Hidden fields | Hide technical keys, IDs from report view |
| Date table | Dedicated marked date table |
MCP Tools Reference
Use these Power BI Modeling MCP operations:
| Operation Category | Key Operations |
|---|---|
connection_operations | Connect, ListConnections, ListLocalInstances, ConnectFabric |
model_operations | Get, GetStats, ExportTMDL |
table_operations | List, Get, Create, Update, GetSchema |
column_operations | List, Get, Create, Update (descriptions, hidden, format) |
measure_operations | List, Get, Create, Update, Move |
relationship_operations | List, Get, Create, Update, Activate, Deactivate |
dax_query_operations | Execute, Validate |
calculation_group_operations | List, Create, Update |
security_role_operations | List, Create, Update, GetEffectivePermissions |
Common Tasks
Add Measure with Description
measure_operations(
operation: "Create",
definitions: [{
name: "Total Sales",
tableName: "Sales",
expression: "SUM(Sales[Amount])",
formatString: "$#,##0",
description: "Sum of all sales amounts"
}]
)Update Column Description
column_operations(
operation: "Update",
definitions: [{
tableName: "Customer",
name: "CustomerKey",
description: "Unique identifier for customer dimension",
isHidden: true
}]
)Create Relationship
relationship_operations(
operation: "Create",
definitions: [{
fromTable: "Sales",
fromColumn: "CustomerKey",
toTable: "Customer",
toColumn: "CustomerKey",
crossFilteringBehavior: "OneDirection"
}]
)When to Use Microsoft Learn MCP
Research current best practices using microsoft_docs_search for:
Latest DAX function documentation
New Power BI features and capabilities
Complex modeling scenarios (SCD Type 2, many-to-many)
Performance optimization techniques
Security implementation patterns
Files
- ATTRIBUTION.mdAdded by AutoGineer869 B
- LICENSELicence file added by AutoGineer1.0 KiB
- SKILL.md5.8 KiB
- references/MEASURES-DAX.md4.9 KiB
- references/PERFORMANCE.md5.3 KiB
- references/RELATIONSHIPS.md3.4 KiB
- references/RLS.md5.3 KiB
- references/STAR-SCHEMA.md3.1 KiB
references/STAR-SCHEMA.md
Star Schema Design for Power BI
Overview
Star schema is the optimal design pattern for Power BI semantic models. It organizes data into:
Dimension tables: Enable filtering and grouping (the "one" side)
Fact tables: Enable summarization (the "many" side)
Table Classification
Dimension Tables
Contain descriptive attributes for filtering/slicing
Have unique key columns (one row per entity)
Examples: Customer, Product, Date, Geography, Employee
Naming convention: Singular noun (
Customer,Product)
Fact Tables
Contain measurable, quantitative data
Have foreign keys to dimensions
Store data at consistent grain (one row per transaction/event)
Examples: Sales, Orders, Inventory, WebVisits
Naming convention: Business process noun (
Sales,Orders)
Design Principles
1. Separate Dimensions from Facts
BAD: Single denormalized "Sales" table with customer details
GOOD: "Sales" fact table + "Customer" dimension table2. Consistent Grain
Every row in a fact table represents the same thing:
Order line level (most common)
Daily aggregation
Monthly summary
Never mix grains in one table.
3. Surrogate Keys
Add surrogate keys when source lacks unique identifiers:
// Power Query: Add index column
= Table.AddIndexColumn(Source, "CustomerKey", 1, 1)4. Date Dimension
Always create a dedicated date table:
Mark as date table in Power BI
Include fiscal periods if needed
Add relative date columns (IsCurrentMonth, IsPreviousYear)
Date =
ADDCOLUMNS(
CALENDAR(DATE(2020,1,1), DATE(2030,12,31)),
"Year", YEAR([Date]),
"Month", FORMAT([Date], "MMMM"),
"MonthNum", MONTH([Date]),
"Quarter", "Q" & FORMAT([Date], "Q"),
"WeekDay", FORMAT([Date], "dddd")
)Special Dimension Types
Role-Playing Dimensions
Same dimension used multiple times (e.g., Date for OrderDate, ShipDate):
Option 1: Duplicate the table (OrderDate, ShipDate tables)
Option 2: Use inactive relationships with USERELATIONSHIP in DAX
Slowly Changing Dimensions (Type 2)
Track historical changes with version columns:
StartDate, EndDate columns
IsCurrent flag
Requires pre-processing in data warehouse
Junk Dimensions
Combine low-cardinality flags into one table:
OrderFlags dimension: IsRush, IsGift, IsOnlineDegenerate Dimensions
Keep transaction identifiers (OrderNumber, InvoiceID) in fact table.
Anti-Patterns to Avoid
| Anti-Pattern | Problem | Solution |
|---|---|---|
| Wide denormalized tables | Poor performance, hard to maintain | Split into star schema |
| Snowflake (normalized dims) | Extra joins hurt performance | Flatten dimensions |
| Many-to-many without bridge | Ambiguous results | Add bridge/junction table |
| Mixed grain facts | Incorrect aggregations | Separate tables per grain |
Validation Checklist
[ ] Each table is clearly dimension or fact
[ ] Fact tables have foreign keys to all related dimensions
[ ] Dimensions have unique key columns
[ ] Date table exists and is marked
[ ] No circular relationship paths
[ ] Consistent naming conventions
Requirements and compatibility
Written for: GitHub Copilot
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs an MCP server
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- First committed by
AlahmadiQ8
- Publisher
- GitHub (Official)
- Distributed by
- GitHub
- Source
- github/awesome-copilot · skills/powerbi-modeling · commit 797337f
- Licence
- MIT License (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
- Contributors
- AlahmadiQ8
AutoGineer is not affiliated with or endorsed by AlahmadiQ8 or GitHub.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download powerbi-modeling.zip