Power BI Semantic Modelling
Guide users in building optimised, well-documented Power BI semantic models following Microsoft best practices.
When to Use This Skill
Use this skill when users ask about:
- Creating or optimising 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 optimisation
- Calculation groups and field parameters
- Model validation and best practice checks
Trigger phrases: "create a measure", "add relationship", "star schema", "optimise model", "DAX formula", "RLS", "naming convention", "model documentation", "cardinality", "cross-filter"
Prerequisites
Required Tools
- Power BI Modelling 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 Analyse First
Before providing any modelling 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 optimisation: 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 Modelling 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 modelling scenarios (SCD Type 2, many-to-many)
- Performance optimisation techniques
- Security implementation patterns
1---2name: powerbi-modelling3description: 'Power BI semantic modelling assistant for building optimised data models. Use when working with Power BI semantic models, creating measures, designing star schemas, configuring relationships, implementing RLS, or optimising model performance. Triggers on queries about DAX calculations, table relationships, dimension/fact table design, naming conventions, model documentation, cardinality, cross-filter direction, calculation groups, and data model best practices. Always connects to the active model first using power-bi-modelling MCP tools to understand the data structure before providing guidance.'4metadata:5 source: https://skillmd.com/skills/marielynneblock/powerbi-modelling6 skill-author: 'Marie-Lynne Block'7 version: '0.0.1'8---910# Power BI Semantic Modelling1112Guide users in building optimised, well-documented Power BI semantic models following Microsoft best practices.1314## When to Use This Skill1516Use this skill when users ask about:17- Creating or optimising Power BI semantic models18- Designing star schemas (dimension/fact tables)19- Writing DAX measures or calculated columns20- Configuring table relationships (cardinality, cross-filter)21- Implementing row-level security (RLS)22- Naming conventions for tables, columns, measures23- Adding descriptions and documentation to models24- Performance tuning and optimisation25- Calculation groups and field parameters26- Model validation and best practice checks2728**Trigger phrases:** "create a measure", "add relationship", "star schema", "optimise model", "DAX formula", "RLS", "naming convention", "model documentation", "cardinality", "cross-filter"2930## Prerequisites3132### Required Tools33- **Power BI Modelling MCP Server**: Required for connecting to and modifying semantic models34 - Enables: connection_operations, table_operations, measure_operations, relationship_operations, etc.35 - Must be configured and running to interact with models3637### Optional Dependencies38- **Microsoft Learn MCP Server**: Recommended for researching latest best practices39 - Enables: microsoft_docs_search, microsoft_docs_fetch40 - Use for complex scenarios, new features, and official documentation4142## Workflow4344### 1. Connect and Analyse First4546Before providing any modelling guidance, always examine the current model state:4748```491. List connections: connection_operations(operation: "ListConnections")502. If no connection, check for local instances: connection_operations(operation: "ListLocalInstances")513. Connect to the model (Desktop or Fabric)524. Get model overview: model_operations(operation: "Get")535. List tables: table_operations(operation: "List")546. List relationships: relationship_operations(operation: "List")557. List measures: measure_operations(operation: "List")56```5758### 2. Evaluate Model Health5960After connecting, assess the model against best practices:6162- **Star Schema**: Are tables properly classified as dimension or fact?63- **Relationships**: Correct cardinality? Minimal bidirectional filters?64- **Naming**: Human-readable, consistent naming conventions?65- **Documentation**: Do tables, columns, measures have descriptions?66- **Measures**: Explicit measures for key calculations?67- **Hidden Fields**: Are technical columns hidden from report view?6869### 3. Provide Targeted Guidance7071Based on analysis, guide improvements using references:72- Star schema design: See [star-schema.md](references/star-schema.md)73- Relationship configuration: See [relationships.md](references/relationships.md)74- DAX measures and naming: See [measures-dax.md](references/measures-dax.md)75- Performance optimisation: See [performance.md](references/performance.md)76- Row-level security: See [rls.md](references/rls.md)7778## Quick Reference: Model Quality Checklist7980| Area | Best Practice |81|------|--------------|82| Tables | Clear dimension vs fact classification |83| Naming | Human-readable: `Customer Name` not `CUST_NM` |84| Descriptions | All tables, columns, measures documented |85| Measures | Explicit DAX measures for business metrics |86| Relationships | One-to-many from dimension to fact |87| Cross-filter | Single direction unless specifically needed |88| Hidden fields | Hide technical keys, IDs from report view |89| Date table | Dedicated marked date table |9091## MCP Tools Reference9293Use these Power BI Modelling MCP operations:9495| Operation Category | Key Operations |96|-------------------|----------------|97| `connection_operations` | Connect, ListConnections, ListLocalInstances, ConnectFabric |98| `model_operations` | Get, GetStats, ExportTMDL |99| `table_operations` | List, Get, Create, Update, GetSchema |100| `column_operations` | List, Get, Create, Update (descriptions, hidden, format) |101| `measure_operations` | List, Get, Create, Update, Move |102| `relationship_operations` | List, Get, Create, Update, Activate, Deactivate |103| `dax_query_operations` | Execute, Validate |104| `calculation_group_operations` | List, Create, Update |105| `security_role_operations` | List, Create, Update, GetEffectivePermissions |106107## Common Tasks108109### Add Measure with Description110```111measure_operations(112 operation: "Create",113 definitions: [{114 name: "Total Sales",115 tableName: "Sales",116 expression: "SUM(Sales[Amount])",117 formatString: "$#,##0",118 description: "Sum of all sales amounts"119 }]120)121```122123### Update Column Description124```125column_operations(126 operation: "Update",127 definitions: [{128 tableName: "Customer",129 name: "CustomerKey",130 description: "Unique identifier for customer dimension",131 isHidden: true132 }]133)134```135136### Create Relationship137```138relationship_operations(139 operation: "Create",140 definitions: [{141 fromTable: "Sales",142 fromColumn: "CustomerKey",143 toTable: "Customer",144 toColumn: "CustomerKey",145 crossFilteringBehavior: "OneDirection"146 }]147)148```149150## When to Use Microsoft Learn MCP151152Research current best practices using `microsoft_docs_search` for:153- Latest DAX function documentation154- New Power BI features and capabilities155- Complex modelling scenarios (SCD Type 2, many-to-many)156- Performance optimisation techniques157- Security implementation patterns