review-report
Actionable feedback on the quality, usage, and effectiveness of Power BI reports. Automatically invoke when the user asks to "review a report", "audit a report", "report usage analysis", "report health check", "find unused reports", "check if a report is being used", "assess report performance", "evaluate report quality".
npx skills add data-goblin/power-bi-agentic-development --skill review-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.
# Reviewing Power BI Reports Structured evaluation of Power BI reports to produce actionable feedback for developers and consultants. A report review assesses whether a report is effective, well-built, and actually being used. The output is a prioritized list of findings with concrete recommendations. Note that the skill works on one of three scenarios: 1. Report under development: In this scenario, the focus is more on the report content, structure, organization, and performance based on accurately gathered requirements. 2. Report in testing: In this scenario, the focus might incorporate user feedback or check basic information about the deployed report in Power BI / Fabric. 3. Report in use: This is the ideal scenario, where the focus is usage; the ultimate definition of success is whether the report is being used; what percentage of the people who have access to the report have accessed it in the last 28 days, and how much? Bad reports aren't used, or have declining usage. In scenario 2-3 you may still provide feedback on the report content / structure, but prioritizing other things first. ## When to Use Activate when conducting a report review, audit, or health check. Common tr
- When to Use
- Review Dimensions
- 1. Usage and Adoption
- 2. Design and Layout
- 3. Data Model Binding
- 4. Performance
- 5. Report Metadata and Governance
- 6. Accessibility, Standards, and Documentation
- Review Workflow
- Step 1: Scope
- Step 1a: Determine Scope and Access
- Step 1b: Determine Report Lifecycle Stage
- Step 2: Gather Data
- Step 3: Evaluate
Workspace overview (views, rank, page views, load times) python3 scripts/get_report_usage.py -w <workspace-id> Add Tier 3 cross-workspace last-visited timestamps via the undocumented DataHub V2 API Useful for the "is this report being used at all" question without tenant admin role python3 scripts/get_report_usage.py -w <workspace-id> --include-datahub Single report deep-dive (daily views, per-viewer breakdown, page views by day) python3 scripts/get_report_detail.py -w <workspace-id> -r <report-id> Distribution audit (who has access, through what channels) python3 scripts/get_report_distribution.py -w <workspace-id> -r <report-id> python3 scripts/performance_audit.py -w <workspace-id> -r <report-id>
What does the review-report skill do?
Actionable feedback on the quality, usage, and effectiveness of Power BI reports. Automatically invoke when the user asks to "review a report", "audit a report", "report usage analysis", "report health check", "find unused reports", "check if a report is being used", "assess report performance", "evaluate report quality".
How do I install it?
Run `npx skills add data-goblin/power-bi-agentic-development --skill review-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.