agentleFS
santoshkanthetysantoshkanthety/powerbi-agent/skills/powerbi-report-authoring/SKILL.md

powerbi-report-authoring

Skill3 starsChanged 7 months agoMITView on GitHub

General report authoring patterns. Use when the user mentions: report, page, visual, chart, bar chart, line chart, matrix, table, slicer, filter, bookmark, tooltip, drill-through, navigation, layout, canvas, report design, visual formatting, conditional formatting, KPI, card, decomposition tree.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Place most important KPIs top-left

    line 27
  2. Distinctive:

    Use grey for context/comparison (prior period, budget)

    line 69
  3. Distinctive:

    Never use red/green together without a pattern alternative

    line 71
  4. Distinctive:

    Always include: current period value, prior period, % change

    line 119

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Power BI Report Authoring

Trigger

Activate when the user mentions: report, page, visual, chart, bar chart, line chart, matrix, table, slicer, filter, bookmark, tooltip, drill-through, navigation, layout, canvas, report design, visual formatting, conditional formatting, KPI, card, decomposition tree

What You Know

You are a report design expert who has built hundreds of Power BI reports for C-suite executives, operations teams, and analysts. You know the difference between a report users love and one they abandon after day 2.

Report Design Principles (The Foundation)

1. Define the audience before touching Power BI

Executive:    3–5 KPIs, trend, one insight per page, mobile-ready
Operational:  Tables with filters, drilldown, export capability
Analytical:   Self-service filters, custom visuals, decomposition trees

2. The F-Pattern and Z-Pattern layouts

  • Eye tracks top-left → right → down → left
  • Place most important KPIs top-left
  • Navigation always top or left panel
  • Filters and slicers: right panel or top bar (consistent)

3. Page Structure Template

┌─────────────────────────────────────────────────────┐
│ LOGO    │  Report Title               │  Date Range  │
│─────────────────────────────────────────────────────│
│ KPI 1   │  KPI 2   │  KPI 3   │  KPI 4   │  KPI 5  │
│─────────────────────────────────────────────────────│
│                                      │              │
│   Primary Chart (60% width)          │  Slicers     │
│                                      │  - Region    │
│                                      │  - Product   │
│──────────────────────────────────────│  - Customer  │
│  Secondary Chart   │ Supporting Info │              │
└─────────────────────────────────────────────────────┘

Visual Selection Guide

Data StoryBest Visual
Part of whole (< 5 categories)Donut or Pie
Part of whole (5+ categories)Stacked Bar
Trend over timeLine Chart
Comparison across categoriesBar/Column Chart
Correlation between two metricsScatter Plot
Hierarchy + proportionTreemap
Geographic dataMap / Filled Map
Detailed data with interactionsMatrix
Single metric vs targetKPI Card / Gauge
Decomposing a metricDecomposition Tree
Anomaly detectionAnomaly Detection (line chart)
Key influencersKey Influencers Visual

Formatting Standards

Colours

  • Max 4–5 colours in a report
  • One accent colour for highlights
  • Use grey for context/comparison (prior period, budget)
  • Semantic colours: red = bad, green = good, amber = warning (unless colour-blind mode needed)
  • Never use red/green together without a pattern alternative

Typography

  • Report title: 18–22pt, bold
  • Section headers: 14–16pt, bold
  • KPI values: 24–32pt, bold
  • Labels: 10–12pt, regular
  • Consistent font family throughout (Segoe UI or DM Sans)

Cards & KPIs

┌──────────────────┐
│  Total Sales     │  ← Label (small, grey)
│  $4.2M           │  ← Value (large, bold)
│  ▲ 12% vs LY    │  ← Trend indicator (colour-coded)
└──────────────────┘

Advanced Techniques

Bookmarks for Navigation

Use bookmarks for:
- Toggle between chart types (user preference)
- Show/hide filter panels
- "Reset filters" button
- Storytelling slides
Never use: More than 20 bookmarks (maintenance nightmare)

Drillthrough Pages

Setup: Right-click drill context → specific product, customer, region
Keep: Drillthrough pages as hidden pages
Add: Back button on every drillthrough page

Conditional Formatting

-- Colour scale based on performance vs target
Color Rule:
  If [Achievement %] < 0.8  → Red (#D32F2F)
  If [Achievement %] < 1.0  → Amber (#F57C00)
  Else                       → Green (#388E3C)

Tooltips

  • Report page tooltips: rich context on hover (mini-report)
  • Always include: current period value, prior period, % change
  • Max tooltip page size: 320×240px

CLI Commands

# List report pages
pbi-agent report pages myreport.pbix

# Add a new report page
pbi-agent report add-page "Executive Summary" myreport.pbix

# Show visual types used across all pages
pbi-agent report visuals myreport.pbix

# Validate report against design standards
pbi-agent report validate --check design-standards myreport.pbix

Report Quality Checklist

☐ Title matches workspace/app name
☐ Date of last refresh visible on every page
☐ All slicers synced across relevant pages
☐ Mobile layout configured for KPI pages
☐ Alt text on all visuals (accessibility)
☐ No cross-filter conflicts between visuals
☐ Drillthrough pages have Back buttons
☐ Tested on 1920x1080, 1366x768, and mobile
☐ No more than 15 visuals per page
☐ Export to PDF tested for critical reports

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.