Menu
Use when working with Power BI Project files, PBIP structure, PBIR report JSON, TMDL semantic model files, definition.pbir bindings, report folders, model folders, or validation after Power BI file edits.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | pbip |
| description | Use when working with Power BI Project files, PBIP structure, PBIR report JSON, TMDL semantic model files, definition.pbir bindings, report folders, model folders, or validation after Power BI file edits. |
| license | Personal use |
| argument-hint | [pbip-task] [path] |
| metadata | {"author":"data-visualization-kit","version":"1.0.0","source_inspiration":"data-goblin/power-bi-agentic-development@67627c270241f282ad98754194ad58212b0fa886"} |
PBIP is the source-control-friendly Power BI project format. Use this skill to reason about file layout, direct file changes, rename cascades, bindings, and validation.
.pbip, .Report, .SemanticModel, .Dataset, .tmdl, definition.pbir, visual.json, page.json, or report.json..Report/ contains PBIR report metadata..SemanticModel/ or .Dataset/ contains model metadata, often TMDL.definition.pbir tells a report which semantic model it binds to.pbir CLI when available.scripts/hooks/power-bi-output-gate.cjs or equivalent validation before publishing.definition.pbir binding shape and local by-path targets.Record validation status in:
projects/<slug>/docs/visualization.md
projects/<slug>/docs/publish.md
Store exports or screenshots in:
projects/<slug>/docs/assets/exports/
projects/<slug>/docs/assets/screenshots/
Ask the user before:
End-to-end project execution wrapper for Data Visualization Kit. Use when the user types `$dv-cook` or wants to continue a project after `$dv-plan` with the context, dataset, and goals already locked.
Build and refresh visualization layers for Data Visualization Kit projects. Use when the task is dashboard construction, chart refresh, visualization-path selection, dashboard QA, or project-scoped visualization delivery that must follow the kit visualization workflow and resolve to one selected tool path.
Start a new Data Visualization Kit project with structured intake and planning. Use when the user types `$dv-plan`, starts a new project, has a dataset but unclear scope, needs framework mapping, or needs one canonical project plan file before any downstream `$dv-*` workflow runs.
Publish wrapper for Data Visualization Kit. Use when the user types `$dv-publish` or needs to make a project git-ready, deployment-ready, and aligned with the kit's publish rules.
Use when a Data Visualization Kit project chooses Power BI as the visualization path, or when the user asks to build, review, publish, or operate Power BI reports, dashboards, semantic models, PBIP/PBIR assets, DAX, Power BI Desktop, or Microsoft Fabric-backed report workflows.
Maintain and evolve existing Apache Superset analytics stacks (v6.x). Use for SQL Lab, datasets, charts, dashboards, RBAC, RLS, embedding via guest token API, REST API integration, Celery async, caching, Docker/Helm deployment, and migration planning toward Metabase or Grafana. Prefer only for legacy projects that already selected Superset. Requires 4GB+ RAM.