agentleFS
santoshkanthetysantoshkanthety/powerbi-agent/skills/powerbi-dax-performance/SKILL.md

powerbi-dax-performance

Skill3 starsChanged 7 months agoMITView on GitHub

DAX performance optimization for semantic models. Automatically invoke when the user asks to "optimize DAX", "fix slow DAX", "DAX performance", "tune a measure", "debug a measure", "DAX anti-patterns", or mentions slow queries, server timings, or DAX authoring.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Local models (Power BI Desktop): Use the connect-pbid skill — specifically performance-profiling.md for FE/SE timing and …

    line 25
  2. Very specific:

    Remote models (Fabric Service / XMLA): Use the powerbi-modeling-mcp VS Code extension for trace and query operations.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

DAX

Skills and references for writing, debugging, and optimizing DAX in semantic models.

Optimization

For systematic DAX query performance optimization, read the workflow reference first:

references/dax-performance-optimization.md — Tiered framework (4 tiers), phased workflow, decision guide, and error handling.

Detailed reference files (progressive disclosure — consult as directed by the workflow):

  • references/engine-internals.md — FE/SE architecture, xmSQL, compression/segments, SE fusion, trace diagnostics
  • references/dax-patterns.md — Tier 1 DAX patterns (DAX001–DAX021) + Tier 2 query structure (QRY001–QRY004)
  • references/model-optimization.md — Tier 3 model patterns (MDL001–MDL010) + Tier 4 Direct Lake (DL001–DL002)

Trace capture and performance profiling:

  • Local models (Power BI Desktop): Use the connect-pbid skill — specifically performance-profiling.md for FE/SE timing and evaluateandlog-debugging.md for intermediate result inspection.
  • Remote models (Fabric Service / XMLA): Use the powerbi-modeling-mcp VS Code extension for trace and query operations. Install: code --install-extension analysis-services.powerbi-modeling-mcp

Related Skills

  • review-semantic-model — Model auditing including DAX anti-patterns and best practices
  • connect-pbid (pbi-desktop plugin) — Trace capture, performance profiling, EVALUATEANDLOG debugging
  • lineage-analysis — Impact analysis before model changes

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.