PO

It helps structure star schemas, create DAX measures, and manage performance optimization and security for Power BI models.

Install

mkdir -p .claude/skills/powerbi-modeling && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/923" && unzip -o skill.zip -d .claude/skills/powerbi-modeling && rm skill.zip

Installs to .claude/skills/powerbi-modeling

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Power BI semantic modeling assistant for building optimized data models. Use when working with Power BI semantic models, creating measures, designing star schemas, configuring relationships, implementing RLS, or optimizing 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-modeling MCP tools to understand the data structure before providing guidance.
600 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Design star schema dimension/fact relationships
  • Draft optimized DAX measures and calculated columns
  • Configure row-level security (RLS) rules
  • Validate model cardinality and cross-filtering
  • Document model structures and naming conventions

How it works

It interacts with the Power BI Modeling MCP server to inspect existing model metadata and output schema improvements or DAX logic.

Inputs & outputs

You give it
Data entity relationships, business requirements, and model documentation.
You get back
Optimized DAX code, schema relationship definitions, and security configuration scripts.

When to use powerbi-modeling

  • Write DAX formulas
  • Design star schema models
  • Configure row-level security
  • Optimize model performance

About this skill

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:

Quick Reference: Model Quality Checklist

AreaBest Practice
TablesClear dimension vs fact classification
NamingHuman-readable: Customer Name not CUST_NM
DescriptionsAll tables, columns, measures documented
MeasuresExplicit DAX measures for business metrics
RelationshipsOne-to-many from dimension to fact
Cross-filterSingle direction unless specifically needed
Hidden fieldsHide technical keys, IDs from report view
Date tableDedicated marked date table

MCP Tools Reference

Use these Power BI Modeling MCP operations:

Operation CategoryKey Operations
connection_operationsConnect, ListConnections, ListLocalInstances, ConnectFabric
model_operationsGet, GetStats, ExportTMDL
table_operationsList, Get, Create, Update, GetSchema
column_operationsList, Get, Create, Update (descriptions, hidden, format)
measure_operationsList, Get, Create, Update, Move
relationship_operationsList, Get, Create, Update, Activate, Deactivate
dax_query_operationsExecute, Validate
calculation_group_operationsList, Create, Update
security_role_operationsList, 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

When not to use it

  • General SQL query tuning
  • Non-Power BI reporting tools

Prerequisites

Power BI DesktopPower BI Modeling MCP Server

Limitations

  • Requires active connection to model
  • Limited by underlying data quality
  • DAX performance depends on underlying engine constraints

How it compares

It offers schema-specific advice for Microsoft ecosystem tools rather than generic database modeling guidance.

Compared to similar skills

powerbi-modeling side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
powerbi-modeling (this skill)116moNo flagsIntermediate
sql-queries185moNo flagsIntermediate
senior-data-engineer217moReviewAdvanced
data-quality-frameworks62moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

meeting-minutes

github

Generate concise, actionable meeting minutes for internal meetings. Includes metadata, attendees, agenda, decisions, action items (owner + due date), and follow-up steps.

41210

penpot-uiux-design

github

Comprehensive guide for creating professional UI/UX designs in Penpot using MCP tools. Use this skill when: (1) Creating new UI/UX designs for web, mobile, or desktop applications, (2) Building design systems with components and tokens, (3) Designing dashboards, forms, navigation, or landing pages, (4) Applying accessibility standards and best practices, (5) Following platform guidelines (iOS, Android, Material Design), (6) Reviewing or improving existing Penpot designs for usability. Triggers: "design a UI", "create interface", "build layout", "design dashboard", "create form", "design landing page", "make it accessible", "design system", "component library".

27145

excalidraw-diagram-generator

github

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.

1879

markdown-to-html

github

Convert Markdown files to HTML similar to `marked.js`, `pandoc`, `gomarkdown/markdown`, or similar tools; or writing custom script to convert markdown to html and/or working on web template systems like `jekyll/jekyll`, `gohugoio/hugo`, or similar web templating systems that utilize markdown documents, converting them to html. Use when asked to "convert markdown to html", "transform md to html", "render markdown", "generate html from markdown", or when working with .md files and/or web a templating system that converts markdown to HTML output. Supports CLI and Node.js workflows with GFM, CommonMark, and standard Markdown flavors.

1662

git-commit

github

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

1149

prd

github

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

1161

You might also like

sql-queries

anthropics

Write correct, performant SQL across all major data warehouse dialects (Snowflake, BigQuery, Databricks, PostgreSQL, etc.). Use when writing queries, optimizing slow SQL, translating between dialects, or building complex analytical queries with CTEs, window functions, or aggregations.

1888

senior-data-engineer

davila7

World-class data engineering skill for building scalable data pipelines, ETL/ELT systems, and data infrastructure. Expertise in Python, SQL, Spark, Airflow, dbt, Kafka, and modern data stack. Includes data modeling, pipeline orchestration, data quality, and DataOps. Use when designing data architectures, building data pipelines, optimizing data workflows, or implementing data governance.

2179

data-quality-frameworks

wshobson

Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.

628

fuzzy-matching

dadbodgeoff

Multi-stage fuzzy matching pipeline for entity reconciliation. PostgreSQL trigram pre-filter, salient overlap check, and multi-factor similarity scoring.

825

query-writing

langchain-ai

For writing and executing SQL queries - from simple single-table queries to complex multi-table JOINs and aggregations

723

data-engineer

sickn33

Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms. Use PROACTIVELY for data pipeline design, analytics infrastructure, or modern data stack implementation.

325

Search skills

Search the agent skills registry