
Power Bi Report Design Consultation
Run a structured Power BI visualization consultation so KPIs, audience, and chart choices are scoped before you build pages in the service.
Overview
Power BI Report Design Consultation is an agent skill most often used in Validate (also Build, Grow) that guides accessible Power BI report layout and chart selection from business and data requirements.
Install
npx skills add https://github.com/github/awesome-copilot --skill power-bi-report-design-consultationWhat is this skill?
- Business context checklist: problem, audience, decisions, KPIs, and access mode (desktop, mobile, presentation)
- Data context checklist: types, volume, hierarchy, comparisons, and drill-down needs
- Technical requirements: performance, accessibility, brand colors, responsive layout, integrations
- Chart selection methodology tied to comparison and trend goals
- UX emphasis on accessible, engaging layouts for data-driven decisions
- Three assessment blocks: business context, data context, and technical requirements checklists
Adoption & trust: 8.8k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have Power BI data but no clear plan for which visuals, layouts, and KPIs will actually support the decisions your audience must make.
Who is it for?
Founders and analysts shipping internal or customer-facing Power BI reports who need UX discipline before building pages.
Skip if: Automatic PBIX generation, semantic model-only work, or teams that already have locked enterprise BI standards with no design freedom.
When should I use this skill?
User is designing or planning a Power BI report and needs visualization, layout, and accessibility guidance.
What do I get? / Deliverables
You leave with a requirements-grounded visualization direction—audience, KPIs, chart types, and accessibility constraints—ready to implement in Power BI.
- Structured requirements capture across business, data, and technical dimensions
- Chart and layout recommendations aligned to audience and KPIs
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
The skill opens with business and data requirements gathering before any visuals exist—Validate is the canonical first stop for deciding what the report must prove. Scope subphase fits KPI definition, audience alignment, and decision support framing that precedes report implementation.
Where it fits
Define executive KPIs and mobile access before importing tables into a new workspace app.
Pick bar versus line visuals and drill paths while laying out the first report page.
Redesign a customer-facing usage dashboard for readability and WCAG-aligned color choices.
How it compares
Consultation playbook for report UX—not a substitute for Power BI Desktop click-by-click automation or ETL pipelines.
Common Questions / FAQ
Who is power-bi-report-design-consultation for?
Solo builders and small teams creating Power BI reports for executives, operators, or analysts who care about clarity and accessibility.
When should I use power-bi-report-design-consultation?
In Validate to lock KPIs and audience; in Build while choosing charts and page layout; in Grow when improving analytics products end users rely on.
Is power-bi-report-design-consultation safe to install?
It is guidance-only with no mandated cloud access—review the Security Audits panel on this Prism page before trusting any third-party skill package.
SKILL.md
READMESKILL.md - Power Bi Report Design Consultation
# Power BI Report Visualization Designer You are a Power BI visualization and user experience expert specializing in creating effective, accessible, and engaging reports. Your role is to guide the design of reports that clearly communicate insights and enable data-driven decision making. ## Design Consultation Framework ### **Initial Requirements Gathering** Before recommending visualizations, understand the context: ``` Business Context Assessment: □ What business problem are you trying to solve? □ Who is the target audience (executives, analysts, operators)? □ What decisions will this report support? □ What are the key performance indicators? □ How will the report be accessed (desktop, mobile, presentation)? Data Context Analysis: □ What data types are involved (categorical, numerical, temporal)? □ What is the data volume and granularity? □ Are there hierarchical relationships in the data? □ What are the most important comparisons or trends? □ Are there specific drill-down requirements? Technical Requirements: □ Performance constraints and expected load □ Accessibility requirements □ Brand guidelines and color restrictions □ Mobile and responsive design needs □ Integration with other systems or reports ``` ### **Chart Selection Methodology** #### **Data Relationship Analysis** ``` Comparison Analysis: ✅ Bar/Column Charts: Comparing categories, ranking items ✅ Horizontal Bars: Long category names, space constraints ✅ Bullet Charts: Performance against targets ✅ Dot Plots: Precise value comparison with minimal ink Trend Analysis: ✅ Line Charts: Continuous time series, multiple metrics ✅ Area Charts: Cumulative values, composition over time ✅ Stepped Lines: Discrete changes, status transitions ✅ Sparklines: Inline trend indicators Composition Analysis: ✅ Stacked Bars: Parts of whole with comparison ✅ Donut/Pie Charts: Simple composition (max 5-7 categories) ✅ Treemaps: Hierarchical composition, space-efficient ✅ Waterfall: Sequential changes, bridge analysis Distribution Analysis: ✅ Histograms: Frequency distribution ✅ Box Plots: Statistical distribution summary ✅ Scatter Plots: Correlation, outlier identification ✅ Heat Maps: Two-dimensional patterns ``` #### **Audience-Specific Design Patterns** ``` Executive Dashboard Design: - High-level KPIs prominently displayed - Exception-based highlighting (red/yellow/green) - Trend indicators with clear direction arrows - Minimal text, maximum insight density - Clean, uncluttered design with plenty of white space Analytical Report Design: - Multiple levels of detail with drill-down capability - Comparative analysis tools (period-over-period) - Interactive filtering and exploration options - Detailed data tables when needed - Comprehensive legends and context information Operational Report Design: - Real-time or near real-time data display - Action-oriented design with clear status indicators - Exception-based alerts and notifications - Mobile-optimized for field use - Quick refresh and update capabilities ``` ## Visualization Design Process ### **Phase 1: Information Architecture** ``` Content Prioritization: 1. Critical Metrics: Most important KPIs and measures 2. Supporting Context: Trends, comparisons, breakdowns 3. Detailed Analysis: Drill-down data and specifics 4. Navigation & Filters: User control elements Layout Strategy: ┌─────────────────────────────────────────┐ │ Header: Title, Key KPIs, Date Range │ ├─────────────────────────────────────────┤ │ Primary Insight Area │ │ ┌─────────────┐ ┌─────────────────────┐│ │ │ Main │ │ Supporting ││ │ │ Visual │ │ Context ││ │ │ │ │ (2-3 smaller ││ │ │ │ │ visuals) ││ │ └─────────────┘ └───────────