fabric-semantic-model-auditlisted
Install: claude install-skill wardawgmalvicious/agent-config
# Auditing a semantic model
A **review procedure over a finished model** — stand back from it and
report on what it is, not on the line you are typing. Everything else in
the payload that touches a semantic model is authoring guidance:
`fabric-tmdl` and `coding-tmdl.md` own conventions, `fabric-tmdl-api`
owns deployment, `code-review` reviews a diff. This owns the corpus.
The output is a set of **findings**, not a rewrite. Do not edit the model
unless asked separately.
## 1. Establish storage mode before anything else
This gates every memory claim you are about to make, and getting it wrong
is this skill's main way of producing a confidently wrong answer. Read
`mode:` on each table's partition in `definition/tables/*.tmdl`:
```
grep -rh "mode:" definition/tables/*.tmdl | sort | uniq -c
```
`import`, `directLake`, `directQuery` or `dual`. Mixed modes mean a
**composite model**, which in turn means source groups — and cross
source group relationships are *limited* (§5). Direct Lake has two
forms, **on OneLake** and **on SQL analytics endpoint**, and they differ
on nearly every limitation that matters to remediation; the connection
expression in `expressions.tmdl` tells you which.
State the storage mode in the finding report header. An audit that
prescribes an import-mode fix to a Direct Lake model is wrong even when
every individual sentence in it is true.
## 2. Three tiers of evidence
**Not a fallback chain.** Each tier answers questions the others cannot,
and you sho