standardize-naming-conventions

Audits and renames tables, columns, and measures in TMDL-based Power BI semantic models.

6|3|Updated Jul 4, 2026
One-click install
npx skills add https://github.com/InsightfulAnalytics/PBI_Agentic_Dev --skill standardize-naming-conventions-insightfulanalytics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: standardize-naming-conventions
Source: https://github.com/InsightfulAnalytics/PBI_Agentic_Dev/tree/main/plugins/semantic-models/skills/standardize-naming-conventions
Command: npx skills add https://github.com/InsightfulAnalytics/PBI_Agentic_Dev --skill standardize-naming-conventions-insightfulanalytics

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Power BI semantic models often accumulate inconsistent naming—CamelCase, snake_case, abbreviations, and technical prefixes like DIM_ or FACT_—making them hard for business users to read and maintain. This Skill audits a TMDL-based model and applies consistent, human-readable naming conventions across tables, columns, measures, and display folders. ## Core Features & Use Cases - Naming Audit Report: Scans all TMDL table files and produces a markdown table of proposed renames grouped by issue type (programming conventions, abbreviations, technical prefixes, missing descriptions). - Safe Cross-File Renaming: Updates every DAX reference to renamed measures and columns across all table files and relationships.tmdl, preventing broken references. - Business-Aligned Conventions: Gathers organizational terminology from the user before renaming, applying rules from references/naming-rules.md such as the measure construction order [Aggregation] [Base Name] [Period] ([Unit]). - Use Case: A model contains measures like NetSls, TurnoverMTD, and shp_dt. The Skill proposes Net Sales, Turnover MTD, and Ship Date, confirms with the user, applies the renames, updates all DAX references, and warns about downstream report rebinding. ## Quick Start Ask the agent to standardize naming conventions in the semantic model at the path to your .SemanticModel/definition/ directory.

Frequently Asked Questions about standardize-naming-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize naming conventions in a Power BI semantic model?▼

Point the Skill at your .SemanticModel/definition/ directory containing TMDL files. It scans all tables, proposes renames in an audit report, and applies approved changes while updating every DAX reference across the model.

How to rename measures in TMDL without breaking DAX references?▼

The Skill searches the entire definition directory for references to each renamed measure or column and updates all [Old Name] and 'Table'[Old Column] patterns across table files and relationships.tmdl, then validates no orphaned references remain.

Does renaming Power BI model fields break existing reports?▼

Yes, renaming model objects breaks downstream report visuals that reference those fields. The Skill warns you before applying changes and recommends rebinding visuals in Power BI Desktop or editing visual.json files in PBIR format.

What naming rules does the Skill enforce for measures and columns?▼

Rules cover human-readable names with spaces, no abbreviations or technical prefixes like DIM_ and FACT_, consistent aggregation, unit, and period syntax, numbered display folder hierarchies, and descriptions on all visible objects.

Can I use my organization's own naming conventions instead of the defaults?▼

Yes, the Skill asks about your business terminology, existing standards, and period and unit conventions before renaming. The rules in references/naming-rules.md are defaults that get overridden by your organization's established conventions.