github/awesome-copilot/skills/power-bi-report-design-consultation/SKILL.md
power-bi-report-design-consultation
Power BI report visualization design prompt for creating effective, user-friendly, and accessible reports with optimal chart selection and layout design.
- Source repository stars
- 37,126
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-07-28
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
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.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/github/awesome-copilot --skill "skills/power-bi-report-design-consultation"Inspect the Agent Skill "power-bi-report-design-consultation" from https://github.com/github/awesome-copilot/blob/9933dcad5be5caeb288cebcd370eeeb2fc2f1685/skills/power-bi-report-design-consultation/SKILL.md at commit 9933dcad5be5caeb288cebcd370eeeb2fc2f1685. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
Visualization Design Process
Review the “Visualization Design Process” section in the pinned source before continuing.
Review and apply the “Visualization Design Process” source section. - 02
Phase 1: Information Architecture
Review the “Phase 1: Information Architecture” section in the pinned source before continuing.
Review and apply the “Phase 1: Information Architecture” source section. - 03
Phase 2: Visual Design Specifications
Review the “Phase 2: Visual Design Specifications” section in the pinned source before continuing.
Review and apply the “Phase 2: Visual Design Specifications” source section. - 04
Phase 3: Interactive Design
Review the “Phase 3: Interactive Design” section in the pinned source before continuing.
Review and apply the “Phase 3: Interactive Design” source section. - 05
Phase 4: Mobile and Responsive Design
Review the “Phase 4: Mobile and Responsive Design” section in the pinned source before continuing.
Review and apply the “Phase 4: Mobile and Responsive Design” source section.
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 86/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 37,126 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- github/awesome-copilot
- Skill path
- skills/power-bi-report-design-consultation/SKILL.md
- Commit
- 9933dcad5be5caeb288cebcd370eeeb2fc2f1685
- License
- MIT
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
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) ││
│ └─────────────┘ └─────────────────────┘│
├─────────────────────────────────────────┤
│ Secondary Analysis (Details/Drill-down) │
├─────────────────────────────────────────┤
│ Filters & Navigation Controls │
└─────────────────────────────────────────┘
Phase 2: Visual Design Specifications
Color Strategy Design
Semantic Color Mapping:
- Green (#2E8B57): Positive performance, on-target, growth
- Red (#DC143C): Negative performance, alerts, below-target
- Blue (#4682B4): Neutral information, base metrics
- Orange (#FF8C00): Warnings, attention needed
- Gray (#708090): Inactive, reference, disabled states
Accessibility Compliance:
✅ Minimum 4.5:1 contrast ratio for text
✅ Colorblind-friendly palette (avoid red-green only distinctions)
✅ Pattern and shape alternatives to color coding
✅ High contrast mode compatibility
✅ Alternative text for screen readers
Brand Integration Guidelines:
- Primary brand color for key metrics and headers
- Secondary palette for data categorization
- Neutral grays for backgrounds and borders
- Accent colors for highlights and interactions
Typography Hierarchy
Text Size and Weight Guidelines:
- Report Title: 20-24pt, Bold, Brand Font
- Page Titles: 16-18pt, Semi-bold, Sans-serif
- Section Headers: 14-16pt, Semi-bold
- Visual Titles: 12-14pt, Medium weight
- Data Labels: 10-12pt, Regular
- Footnotes/Captions: 9-10pt, Light
Readability Optimization:
✅ Consistent font family (maximum 2 families)
✅ Sufficient line spacing and letter spacing
✅ Left-aligned text for body content
✅ Centered alignment only for titles
✅ Adequate white space around text elements
Phase 3: Interactive Design
Navigation Design Patterns
Tab Navigation:
Best for: Related content areas, different time periods
Implementation:
- Clear tab labels (max 7 tabs)
- Visual indication of active tab
- Consistent content layout across tabs
- Logical ordering by importance or workflow
Drill-through Design:
Best for: Detail exploration, context switching
Implementation:
- Clear visual cues for drill-through availability
- Contextual page design with proper filtering
- Back button for easy return navigation
- Consistent styling between levels
Button Navigation:
Best for: Guided workflows, external links
Implementation:
- Action-oriented button labels
- Consistent styling and sizing
- Appropriate visual hierarchy
- Touch-friendly sizing (minimum 44px)
Filter and Slicer Design
Slicer Optimization:
✅ Logical grouping and positioning
✅ Search functionality for high-cardinality fields
✅ Single vs. multi-select based on use case
✅ Clear visual indication of applied filters
✅ Reset/clear all options
Filter Strategy:
- Page-level filters for common scenarios
- Visual-level filters for specific needs
- Report-level filters for global constraints
- Drill-through filters for detailed analysis
Phase 4: Mobile and Responsive Design
Mobile Layout Strategy
Mobile-First Considerations:
- Portrait orientation as primary design
- Touch-friendly interaction targets (44px minimum)
- Simplified navigation with hamburger menus
- Stacked layout instead of side-by-side
- Larger fonts and increased spacing
Responsive Visual Selection:
Mobile-Friendly:
✅ Card visuals for KPIs
✅ Simple bar and column charts
✅ Line charts with minimal data points
✅ Large gauge and KPI visuals
Mobile-Challenging:
❌ Dense matrices and tables
❌ Complex scatter plots
❌ Multi-series area charts
❌ Small multiple visuals
Design Review and Validation
Design Quality Checklist
Visual Clarity:
□ Clear visual hierarchy with appropriate emphasis
□ Sufficient contrast and readability
□ Logical flow and eye movement patterns
□ Minimal cognitive load for interpretation
□ Appropriate use of white space
Functional Design:
□ All interactions work intuitively
□ Navigation is clear and consistent
□ Filtering behaves as expected
□ Mobile experience is usable
□ Performance is acceptable across devices
Accessibility Compliance:
□ Screen reader compatibility
□ Keyboard navigation support
□ High contrast compliance
□ Alternative text provided
□ Color is not the only information carrier
User Testing Framework
Usability Testing Protocol:
Pre-Test Setup:
- Define test scenarios and tasks
- Prepare realistic test data
- Set up observation and recording
- Brief participants on context
Test Scenarios:
1. Initial impression and orientation (30 seconds)
2. Finding specific information (2 minutes)
3. Comparing data points (3 minutes)
4. Drilling down for details (2 minutes)
5. Mobile usage simulation (5 minutes)
Success Criteria:
- Task completion rates >80%
- Time to insight <2 minutes
- User satisfaction scores >4/5
- No critical usability issues
- Accessibility validation passed
Visualization Recommendations Output
Design Specification Template
Visualization Design Recommendations
Executive Summary:
- Report purpose and target audience
- Key design principles applied
- Primary visual selections and rationale
- Expected user experience outcomes
Visual Architecture:
Page 1: Dashboard Overview
├─ Header KPI Cards (4-5 key metrics)
├─ Primary Chart: [Chart Type] showing [Data Story]
├─ Supporting Visuals: [2-3 context charts]
└─ Filter Panel: [Key filter controls]
Page 2: Detailed Analysis
├─ Comparative Analysis: [Chart selection]
├─ Trend Analysis: [Time-based visuals]
├─ Distribution Analysis: [Statistical charts]
└─ Navigation: Drill-through to operational data
Interaction Design:
- Cross-filtering strategy
- Drill-through implementation
- Navigation flow design
- Mobile optimization approach
Implementation Guidelines
Development Priority:
Phase 1 (Week 1): Core dashboard with KPIs and primary visual
Phase 2 (Week 2): Supporting visuals and basic interactions
Phase 3 (Week 3): Advanced interactions and drill-through
Phase 4 (Week 4): Mobile optimization and final polish
Quality Assurance:
□ Visual accuracy validation
□ Interaction testing across browsers
□ Mobile device testing
□ Accessibility compliance check
□ Performance validation
□ User acceptance testing
Success Metrics:
- User engagement and adoption rates
- Time to insight measurements
- Decision-making improvement indicators
- User satisfaction feedback
- Performance benchmarks achievement
Usage Instructions: To get visualization design recommendations, provide:
- Business context and report objectives
- Target audience and usage scenarios
- Data description and key metrics
- Technical constraints and requirements
- Brand guidelines and accessibility needs
- Specific design challenges or questions
I'll provide comprehensive design recommendations including chart selection, layout design, interaction patterns, and implementation guidance tailored to your specific needs and context.
Alternatives
Compare before choosing
coreyhaines31/marketingskills
ab-testing
When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program
event4u-app/agent-config
design-review
Use when the user says "review the design", "check the UI", or wants a comprehensive UI/UX review. Uses a 7-phase methodology covering interaction, responsiveness, accessibility, and more.
event4u-app/agent-config
mcp-builder
Use when building an MCP server in Python (FastMCP) or Node/TypeScript (MCP SDK) — agent-centric tool design, input schemas, error handling, and the 10-question evaluation harness.
affaan-m/ECC
browser-qa
Use this skill to automate visual testing and UI interaction verification using browser automation after deploying features.