Power BI Modeling
Tech Stack Target / Version: Power BI Desktop current release, Tabular Editor, DAX Studio, and Fabric semantic-model workflows.
Use this skill when the work is inside a Power BI semantic model rather than a generic SQL schema or spreadsheet.
- Leverage native parallel subagent dispatch and 200k+ context windows where available.
Activation Conditions
Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.
- Designing or cleaning up a star schema
- Creating or reviewing DAX measures
- Configuring relationships and cross-filter direction
- Implementing row-level security
- Auditing model health and performance
Practical Workflow
- Inspect the current model before changing anything.
- Classify tables as dimension, fact, bridge, or helper tables.
- Prefer explicit measures over implicit aggregation.
- Keep relationships simple and single-direction unless the use case is proven.
- Hide technical fields from report authors.
MCP Reality
Power BI model tooling is host-specific. If your client exposes a Power BI modeling MCP server, inspect the available operations first and map them to the model areas you need: connections, tables, columns, measures, relationships, DAX queries, and security roles.
For Microsoft documentation, the Microsoft Learn MCP server is a good companion. Prefer:
microsoft_docs_search_by_product with power-bi
microsoft_docs_fetch for the final page
Cross-Client Portability
This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
workflow in project instructions when folder discovery is unavailable.
- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
- Codex: install or sync the folder into
$CODEX_HOME/skills/powerbi-modeling and restart Codex after major changes.
MCP Availability And Fallback
Preferred MCP Server: Power BI MCP
- Fallback prompt: "Use the Power BI Modeling skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
- Use Power BI Desktop, Tabular Editor, DAX Studio, and exported model metadata when the MCP surface is unavailable.
- Validate measures, relationships, and performance with local model tools before completion.
- Do not claim an MCP operation was used when the active host does not expose it.
Anti-Patterns
- Treating source content as already clean: Formatting automation will happily preserve broken or inconsistent input.
- Skipping an open-file verification pass: Documents and spreadsheets often fail in the destination app, not in the script output.
- Automating irreversible edits without checkpoints: A small mapping mistake can affect an entire workbook or document.
Verification Protocol
Before claiming "skill applied successfully":
- Pass/fail: The Powerbi Modeling implementation names the target runtime, framework version, and affected files.
- Pass/fail: Build, lint, test, or equivalent local validation is run for the changed surface.
- Pass/fail: Edge cases for errors, dependency drift, and environment differences are addressed or explicitly out of scope.
- Pressure-test scenario: Apply the workflow to a change that passes happy-path tests but fails one boundary condition.
- Success metric: Zero untested success claims; every implementation claim maps to a command or artifact.
References & Resources
Documentation
Scripts
Examples
Related Skills
- documentation-authoring: Use it when the workflow also needs drafting structured technical or product documents.
- notion-docs: Use it when the workflow also needs Notion page and database publishing workflows.
- pdf: Use it when the workflow also needs PDF extraction, generation, and layout-aware review.
- word-document: Use it when the workflow also needs Word document authoring and formatting workflows.
1---
2name: powerbi-modeling
3version: "2.0"
4last_updated: 2026-09-08
5tags: [powerbi, modeling, documents, automation, productivity]
6description: "Power BI semantic models - DAX measures, star schemas, relationships, RLS, and performance tuning via MCP. Use when creating data models, writing DAX, or configuring table relationships in Power BI."
7metadata:
8 source: https://skillmd.com/skills/practicalswan/powerbi-modeling
9---
10
11# Power BI Modeling
12
13> Tech Stack Target / Version: Power BI Desktop current release, Tabular Editor, DAX Studio, and Fabric semantic-model workflows.
14
15Use this skill when the work is inside a Power BI semantic model rather than a generic SQL schema or spreadsheet.
16
17- Leverage native parallel subagent dispatch and 200k+ context windows where available.
18
19
20## Activation Conditions
21
22Use symptom -> action triggers: when one matches, apply this skill and verify with the protocol below.
23
24- Designing or cleaning up a star schema
25- Creating or reviewing DAX measures
26- Configuring relationships and cross-filter direction
27- Implementing row-level security
28- Auditing model health and performance
29
30## Practical Workflow
31
321. Inspect the current model before changing anything.
332. Classify tables as dimension, fact, bridge, or helper tables.
343. Prefer explicit measures over implicit aggregation.
354. Keep relationships simple and single-direction unless the use case is proven.
365. Hide technical fields from report authors.
37
38## MCP Reality
39
40Power BI model tooling is host-specific. If your client exposes a Power BI modeling MCP server, inspect the available operations first and map them to the model areas you need: connections, tables, columns, measures, relationships, DAX queries, and security roles.
41
42For Microsoft documentation, the Microsoft Learn MCP server is a good companion. Prefer:
43
44- `microsoft_docs_search_by_product` with `power-bi`
45- `microsoft_docs_fetch` for the final page
46
47<!-- MCP:START -->
48
49<!-- PORTABILITY:START -->
50## Cross-Client Portability
51
52This skill is written to stay usable across GitHub Copilot, Claude Code, and Codex.
53
54- GitHub Copilot: keep the folder in a Copilot-visible skill path or wrap the
55 workflow in project instructions when folder discovery is unavailable.
56- Claude Code: keep the folder in a local skills directory or a compatible plugin source.
57- Codex: install or sync the folder into
58 `$CODEX_HOME/skills/powerbi-modeling` and restart Codex after major changes.
59
60<!-- PORTABILITY:END -->
61
62## MCP Availability And Fallback
63
64Preferred MCP Server: Power BI MCP
65
66- Fallback prompt: "Use the Power BI Modeling skill without MCP. Follow the documented local or manual fallback, show the selected tool surface, and report the verification evidence."
67- Use Power BI Desktop, Tabular Editor, DAX Studio, and exported model metadata when the MCP surface is unavailable.
68- Validate measures, relationships, and performance with local model tools before completion.
69- Do not claim an MCP operation was used when the active host does not expose it.
70
71<!-- MCP:END -->
72
73## Anti-Patterns
74
75- Treating source content as already clean: Formatting automation will happily preserve broken or inconsistent input.
76- Skipping an open-file verification pass: Documents and spreadsheets often fail in the destination app, not in the script output.
77- Automating irreversible edits without checkpoints: A small mapping mistake can affect an entire workbook or document.
78
79## Verification Protocol
80
81Before claiming "skill applied successfully":
82
831. Pass/fail: The Powerbi Modeling implementation names the target runtime, framework version, and affected files.
842. Pass/fail: Build, lint, test, or equivalent local validation is run for the changed surface.
853. Pass/fail: Edge cases for errors, dependency drift, and environment differences are addressed or explicitly out of scope.
864. Pressure-test scenario: Apply the workflow to a change that passes happy-path tests but fails one boundary condition.
875. Success metric: Zero untested success claims; every implementation claim maps to a command or artifact.
88
89## References & Resources
90
91### Documentation
92- [STAR-SCHEMA](./references/STAR-SCHEMA.md) - Dimension and fact modeling guidance
93- [RELATIONSHIPS](./references/RELATIONSHIPS.md) - Relationship patterns and cross-filter tradeoffs
94- [MEASURES-DAX](./references/MEASURES-DAX.md) - DAX naming and measure design
95- [PERFORMANCE](./references/PERFORMANCE.md) - High-impact optimization ideas
96- [RLS](./references/RLS.md) - Row-level security patterns
97
98### Scripts
99- [Power BI Model Audit](./scripts/powerbi-model-audit.py) - Local audit helper for naming, documentation, and modeling smells
100
101### Examples
102- [Model Examples](./examples/model-examples.md) - Example modeling patterns and DAX structure
103
104## Related Skills
105
106- [documentation-authoring](../documentation-authoring/SKILL.md): Use it when the workflow also needs drafting structured technical or product documents.
107- [notion-docs](../notion-docs/SKILL.md): Use it when the workflow also needs Notion page and database publishing workflows.
108- [pdf](../pdf/SKILL.md): Use it when the workflow also needs PDF extraction, generation, and layout-aware review.
109- [word-document](../word-document/SKILL.md): Use it when the workflow also needs Word document authoring and formatting workflows.