semantic-model
This skill should be used whenever the user mentions a "semantic model", "data model", or "dataset", or asks to "build", "model", "design", "optimize", "review", or "audit" one, or to "add a measure", "add a relationship", "create a role" / "set up RLS", "add a calculation group", "set up incremental refresh", "fix a star schema", "reduce model size", "prepare a model for Copilot / AI", or "check model quality". Covers the full lifecycle (design, build, refresh, review) and drives every operation through the `te` CLI first, then TOM (connect-pbid) or a model MCP, then TMDL authoring (the tmdl
npx skills add data-goblin/power-bi-agentic-development --skill semantic-model --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Semantic models: design, build, refresh, review Guidance for designing, building, refreshing, and reviewing Power BI / Analysis Services tabular models from the terminal. It consolidates model review with modeling best practices, and routes every change to the narrowest capable tool. Depth lives in `references/`; this file is the operating loop and the routing. ## When to use - Designing or building a model: star schema, relationships, measures, calculation groups, roles, parameters, storage modes, incremental refresh - Optimizing a model: size / VertiPaq, DAX correctness, Direct Lake, refresh cost - Reviewing or auditing a model against quality, performance, and best-practice standards - Preparing a model for Copilot / AI consumption ## When NOT to use - Editing report visuals, pages, or formatting: use the `pbir-cli` skill (reports plugin) - Isolated DAX query performance tuning: use the `dax` skill - TMDL file syntax mechanics: use the `tmdl` skill (this skill routes to it for the file-edit fallback) - The `te` command surface itself: the `te-cli` skill (tabular-editor plugin) is the command reference; this skill is the modeling judgment layered on top ## Tool cascade (the cor
- When to use
- When NOT to use
- Tool cascade (the core operating rule)
- Lifecycle
- Design
- Build
- Refresh
- Review
- Review categories (by severity)
- Related skills
- Reference map
- What this skill deliberately leaves out
What does the semantic-model skill do?
This skill should be used whenever the user mentions a "semantic model", "data model", or "dataset", or asks to "build", "model", "design", "optimize", "review", or "audit" one, or to "add a measure", "add a relationship", "create a role" / "set up RLS", "add a calculation group", "set up incremental refresh", "fix a star schema", "reduce model size", "prepare a model for Copilot / AI", or "check model quality". Covers the full lifecycle (design, build, refresh, review) and drives every operation through the `te` CLI first, then TOM (connect-pbid) or a model MCP, then TMDL authoring (the tmdl
How do I install it?
Run `npx skills add data-goblin/power-bi-agentic-development --skill semantic-model --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From data-goblin/power-bi-agentic-development, a repository with 833 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.