pbip

Estrellas11

Forks1

Actualizado26 de mayo de 2026 a las 13:07

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.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

young-lillo

young-lillo/data-visualization-skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

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 Skill

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.

When To Use

The project contains .pbip, .Report, .SemanticModel, .Dataset, .tmdl, definition.pbir, visual.json, page.json, or report.json.
The user asks to validate a Power BI project or diagnose a report that will not open.
The user asks to rename a table, measure, column, page, visual, report, or model.
The user asks about thick vs thin reports, by-path vs by-connection binding, or PBIP/PBIX conversion.

Core Concepts

.Report/ contains PBIR report metadata.
.SemanticModel/ or .Dataset/ contains model metadata, often TMDL.
definition.pbir tells a report which semantic model it binds to.
A thick project usually has report and semantic model folders together.
A thin report usually binds to a remote semantic model.

Direct Edit Rules

Prefer official tools or pbir CLI when available.
If editing JSON directly, parse it before and after changes.
Do not add comments to PBIR JSON.
Keep file names and object names stable unless the user asked for a rename.
For renames, search across report JSON, TMDL, DAX queries, culture files, and report extensions.
After edits, run scripts/hooks/power-bi-output-gate.cjs or equivalent validation before publishing.

Validation Focus

JSON syntax for PBIR files.
Required PBIR files and fields for touched report objects.
Folder names without problematic spaces for new human-authored pages or visuals.
definition.pbir binding shape and local by-path targets.
TMDL syntax via available tools when present.
No Power BI files written outside the intended project workspace.

Output Notes

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/

Escalation

Ask the user before:

Converting PBIX to PBIP.
Publishing to Fabric or Power BI Service.
Editing a shared semantic model.
Renaming model objects that can break downstream reports.
Storing or using tenant/workspace credentials.

Más de este repositorio

mismo repositorio

dv-cook

young-lillo/data-visualization-skills

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.

2026-06-1311

dv-data-visualize

young-lillo/data-visualization-skills

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.

2026-06-1311

dv-plan

young-lillo/data-visualization-skills

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.

2026-06-1311

dv-publish

young-lillo/data-visualization-skills

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.

2026-05-2611

power-bi

young-lillo/data-visualization-skills

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.

2026-05-2611

apache-superset

young-lillo/data-visualization-skills

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.

2026-04-2111

PBIP Skill

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.

When To Use

The project contains .pbip, .Report, .SemanticModel, .Dataset, .tmdl, definition.pbir, visual.json, page.json, or report.json.

The user asks to validate a Power BI project or diagnose a report that will not open.

The user asks to rename a table, measure, column, page, visual, report, or model.

The user asks about thick vs thin reports, by-path vs by-connection binding, or PBIP/PBIX conversion.

Core Concepts

.Report/ contains PBIR report metadata.

.SemanticModel/ or .Dataset/ contains model metadata, often TMDL.

definition.pbir tells a report which semantic model it binds to.

A thick project usually has report and semantic model folders together.

A thin report usually binds to a remote semantic model.

Direct Edit Rules

Prefer official tools or pbir CLI when available.

If editing JSON directly, parse it before and after changes.

Do not add comments to PBIR JSON.

Keep file names and object names stable unless the user asked for a rename.

For renames, search across report JSON, TMDL, DAX queries, culture files, and report extensions.

After edits, run scripts/hooks/power-bi-output-gate.cjs or equivalent validation before publishing.

Validation Focus

JSON syntax for PBIR files.

Required PBIR files and fields for touched report objects.

Folder names without problematic spaces for new human-authored pages or visuals.

definition.pbir binding shape and local by-path targets.

TMDL syntax via available tools when present.

No Power BI files written outside the intended project workspace.

Output Notes

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/

Escalation

Ask the user before:

Converting PBIX to PBIP.

Publishing to Fabric or Power BI Service.

Editing a shared semantic model.

Renaming model objects that can break downstream reports.

Storing or using tenant/workspace credentials.