create-pbi-report
Step-by-step workflow for creating complete Power BI reports from scratch using pbir CLI. Covers model discovery, report creation, page layout, theme setup, visual placement, field binding, filtering, formatting, validation, and publishing. Automatically invoke when the user asks to "create a new report", "build a report from scratch", "make a dashboard", "set up a report with KPIs", "create an executive dashboard", "add pages and visuals to a new report".
npx skills add data-goblin/power-bi-agentic-development --skill create-pbi-report --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Creating Power BI Reports Create and scaffold Power BI reports using `pbir` CLI. Install with `uv tool install pbir-cli` or `pip install pbir-cli`. Load the `pbir-cli` and `pbi-report-design` skills alongside this one. ## Vague or Underspecified Prompts When the user's request lacks specific measures, audience context, structural preferences, or formatting direction (e.g., "make me a dashboard", "create something with KPIs"), consult **`references/vague-prompts.md`** before proceeding. Close the gap between intent and specification with targeted questions; then apply sensible defaults (sqlbi theme, executive dashboard pattern, model-driven KPI selection) for anything the user can't or won't specify. ## Rules - Visuals must not overlap one another - Favor theme changes over visual overrides for static formatting - Favor extension measures with theme colors (like "bad") for conditional formatting - Always create reports inside a named project folder (e.g., `sales-dashboard/Sales.Report`) - Run `pbir validate` after every mutation - New reports already include the **sqlbi** theme -- do NOT run `pbir theme apply-template` unless the user explicitly asks for a different theme - New re
- Vague or Underspecified Prompts
- Rules
- Quick Reference
- Step-by-Step Process
- Step 1: Understand the Business Process
- Step 1b: Assemble and Lock the Design Brief
- Step 2: Identify Location and Connection
- Step 3: Create the Report
- Step 4: Rename Default Page and Add More Pages
- Step 5: Configure Theme (only if user requests)
- Step 6: Add Visuals to Pages
- Step 7: Configure Query Reduction
- Step 8: Wire Interactions and Navigation
- Step 9: Add Filters and Slicers
mkdir -p /path/to/report-name cd /path/to/report-name pbir new report "Name.Report" -c "Workspace/Model.SemanticModel" pbir model # List all known reports/models pbir connect MyWorkspace MyReport # Set active connection mkdir -p sales-dashboard && cd sales-dashboard pbir new report "Sales.Report" -c "MyWorkspace/Sales.SemanticModel" pbir pages rename "Sales.Report/Page 1.Page" --to "Overview" -f # Rename default page pbir add page "Sales.Report/Detail.Page" -n "Detail" # Add extra pages only if needed pbir pages active-page "Sales.Report" "Overview"
What does the create-pbi-report skill do?
Step-by-step workflow for creating complete Power BI reports from scratch using pbir CLI. Covers model discovery, report creation, page layout, theme setup, visual placement, field binding, filtering, formatting, validation, and publishing. Automatically invoke when the user asks to "create a new report", "build a report from scratch", "make a dashboard", "set up a report with KPIs", "create an executive dashboard", "add pages and visuals to a new report".
How do I install it?
Run `npx skills add data-goblin/power-bi-agentic-development --skill create-pbi-report --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From data-goblin/power-bi-agentic-development, a repository with 833 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
