Install any skill in seconds. Free to start, no credit card required.
Get Started Free →data-goblin/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.
Passed 17 of 20 test cases with the skill, and 12 of 20 without it.
and 3 more in the full report
6 fixed13 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to add business documentation comments directly above measure and column declarations in TMDL files so they appear as description tooltips in Power BI. What TMDL comment syntax prefix creates object descriptions?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies triple-slash `///` docstrings for TMDL descriptions | Missed | Passed |
The instructions your model reads when the skill loads.
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.
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:
# 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:
/// comments)CRITICAL: Do not rename anything without understanding the business terminology.
Use AskUserQuestion to gather context:
Adapt the naming rules to the user's business context. The rules in references/naming-rules.md are defaults -- override them when the user's organization has established conventions.
Before making changes, produce an audit report. Present a markdown table showing each proposed rename:
test cases passed, vs 12 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.