standardize-naming-conventions
Interactive naming convention standardization for TMDL-based Power BI semantic models. Automatically invoke when the user asks to "standardize naming conventions", "fix naming conventions", "clean up model names", "apply naming standards", "audit naming", "make names human readable", "rename fields", "fix abbreviations in model", or mentions renaming measures, columns, or tables for consistency across a model.
npx skills add data-goblin/power-bi-agentic-development --skill standardize-naming-conventions --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.
# Standardize Naming Conventions Interactive workflow for auditing and standardizing naming conventions in Power BI semantic models stored as TMDL files. Ensures tables, columns, measures, and display folders follow human-readable, consistent, business-aligned naming standards. ## Primary Workflow ### Phase 1: Discover the Model Locate the TMDL files. Ask the user for the path to the `.SemanticModel/definition/` directory if not obvious from context. Then scan the model structure: ```bash # Count tables and get an overview ls <path>/tables/*.tmdl ``` Read all table TMDL files to build a complete picture of current naming patterns. Focus on: - Table names (check for DIM_, FACT_, or other technical prefixes) - Measure names (check for abbreviations, programming conventions, inconsistent syntax) - Column names (check for CamelCase, snake_case, abbreviations) - Display folder structure (check for organization and consistency) - Presence of descriptions (`///` comments) ### Phase 2: Understand Business Context **CRITICAL: Do not rename anything without understanding the business terminology.** Use `AskUserQuestion` to gather context: 1. **Business terminology**: "What terminology does y
- Primary Workflow
- Phase 1: Discover the Model
- Phase 2: Understand Business Context
- Phase 3: Audit and Report
- Phase 4: Apply Changes
- Phase 5: Validate
- Naming Convention Rules
- Key Anti-Patterns to Detect
- Downstream Report Impact
- Additional Resources
- Reference Files
- Fetching Docs
Count tables and get an overview ls <path>/tables/*.tmdl Find all references to a renamed measure rg "OldMeasureName" <path>/definition/tables/ rg "OldMeasureName" <path>/definition/relationships.tmdl Check for any remaining old names rg -n "old_name_pattern" <path>/definition/
What does the standardize-naming-conventions skill do?
Interactive naming convention standardization for TMDL-based Power BI semantic models. Automatically invoke when the user asks to "standardize naming conventions", "fix naming conventions", "clean up model names", "apply naming standards", "audit naming", "make names human readable", "rename fields", "fix abbreviations in model", or mentions renaming measures, columns, or tables for consistency across a model.
How do I install it?
Run `npx skills add data-goblin/power-bi-agentic-development --skill standardize-naming-conventions --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.