powerbi-semantic-accelerator

Generate and validate Power BI semantic models from YAML catalogs.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/aurora-atoms/lattice --skill powerbi-semantic-accelerator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: powerbi-semantic-accelerator
Source: https://github.com/aurora-atoms/lattice/tree/main/skills/powerbi-semantic-accelerator
Command: npx skills add https://github.com/aurora-atoms/lattice --skill powerbi-semantic-accelerator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the chaos of unmanaged Power BI semantic models by enforcing a catalog-first, evidence-grounded approach to model engineering, ensuring that metrics and data structures are governed, reusable, and accurate.

Core Features & Use Cases

  • Catalog-Driven Development: Uses YAML manifests to define metrics, display metadata, and model contracts before generating TMDL or DAX.
  • Self-Service Governance: Enables safe, user-defined semantic requests that are validated against governed catalogs before implementation.
  • Use Case: When a business user requests a new KPI, use this Skill to patch the metric and display catalogs, validate the change, and generate the corresponding TMDL measure, ensuring the new metric is consistent with existing star-schema contracts.

Quick Start

Use the powerbi-semantic-accelerator skill to validate the semantic specs in the current directory and generate the starter TMDL measures.

Frequently Asked Questions about powerbi-semantic-accelerator

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

FAQPage Schema
How do I automate Power BI semantic model generation using TMDL?

Automate Power BI semantic model generation by defining model contracts and metric catalogs in YAML manifests, which the accelerator validates and converts into starter TMDL measures and DAX. This enforces a catalog-first approach to consistent model engineering.

What is catalog-first Power BI semantic model engineering?

Catalog-first semantic model engineering is the process of defining metrics, display metadata, and star-schema contracts in YAML manifests before generating TMDL or DAX. This approach ensures that semantic layers remain governed, reusable, and accurate across development cycles.

How do I validate a new KPI request against existing Power BI star-schema contracts?

Validate new KPI requests by patching the YAML metric and display catalogs with the requested changes, then running the validation process to ensure alignment with existing star-schema contracts before generating the corresponding TMDL measure.

Does the Power BI semantic accelerator require PyYAML to process model contracts?

Yes, the accelerator requires PyYAML to parse and process the YAML manifests that define model contracts, metric catalogs, and display specifications for deploying consistent Power BI semantic layers.

Can I use YAML manifests to govern self-service Power BI dashboard workflows?

Yes, YAML manifests enable governed self-service workflows by validating user-defined semantic requests against a controlled catalog before implementation, ensuring that generated DAX measures and TMDL structures adhere to enterprise governance standards.

What is the best way to manage DAX measure development for governed Power BI models?

Manage DAX measure development by maintaining metric definitions within YAML catalogs and generating TMDL programmatically, ensuring that all new measures are validated against existing star-schema contracts before deployment to prevent unmanaged model sprawl.