メニュー
Use when a Power BI design should become PBIP or TMDL-ready structures, model folders, table specs, measure files, calculation groups, perspectives, roles, and deployment-ready artifacts.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when Power BI tenant administration needs Admin API playbooks for workspace inventory, usage metrics, refresh failures, endorsements, sensitivity labels, sharing risk, gateways, and capacity.
Coordinate virtual Power BI expert roles such as BI Architect, DAX Expert, Power Query Engineer, Fabric Architect, Finance BI Lead, QA Reviewer, Security Reviewer, and CoE Lead. Use to replace manual expert routing with role-based analysis and deliverables.
Use when DAX measures require executable or semi-executable unit tests, query-based assertions, XMLA or Tabular Editor validation, edge cases, totals, RLS contexts, and reconciliation evidence.
Use when Power BI work needs PBIP, Git, deployment pipelines, semantic model versioning, Tabular Editor, DAX checks, regression tests, release gates, workspace promotion, or CI/CD governance.
Use when the user asks for Expert Mode, senior Power BI engineering, deep model/report/DAX/M review, precise control, or developer-facing Power BI delivery with explicit technical evidence.
Use when the user asks for Generalisten Mode, Prozess Manager mode, Process Owner mode, autonomous BI delivery, or wants the plugin to handle Power BI work end-to-end without requiring expert knowledge.
| name | powerbi-pbip-tmdl-generator |
| description | Use when a Power BI design should become PBIP or TMDL-ready structures, model folders, table specs, measure files, calculation groups, perspectives, roles, and deployment-ready artifacts. |
Turn approved designs into PBIP/TMDL implementation artifacts.
en-US and de-DE descriptions when documentation is required.For a complete generated PBIP/PBIR/TMDL package, use:
python scripts\powerbi_expert_factory.py report-package --process <process-id> --sources "<source description>" --goal "<report goal>" --out outputs\report-packages\<process-id>