Individual skill

semantic-model-analyzer

Use when someone asks for a Power BI semantic model audit, review or documentation, hands over or pastes TMDL, a PBIP or Power Query M, or asks about a model's measures, lineage, relationships, query folding, Copilot readiness or what changed between versions. Not for row counts, refresh or performance; never edits the model.

plugins/semantic-model-analyzer/skills/semantic-model-analyzer/SKILL.md

Read pinned source

Source commit c827dfb26119a88614e1cce6ea610210a43b0d3f

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
21
Repository last updated
Oct 29, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Semantic Model Analyzer

## Outcome
The user gets an answer about a Power BI semantic model that is grounded in its definition, with
every claim traced to a file and line, and, when they ask for one, a set of offline HTML pages
that present the model: a landing page with data and measure lineage, a page per segment, an AI
readiness checklist and a finder. The bundled engine (`sma`) parses TMDL and Power Query M as
text into one dataset; the rules, the `list` and `explain` answers, the comparison of two
versions and the HTML all read that dataset, so an answer never rests on something the files do
not say.

## Use when
- Someone wants a semantic model reviewed, audited or documented: "what needs fixing in this
  model", "document this model for the client".
Back to top