review-report — Claude Code skill: auditing Power BI reports
review-report — a skill that runs a structured check on a Power BI report, telling you whether people actually open it and giving ranked recommendations.
GPL-3.0 ★ 1,104 updated 2026-10-28
/plugin marketplace add data-goblin/power-bi-agentic-development
/plugin install reports@power-bi-agentic-developmentWhat review-report does
The skill looks at a report across six areas, but a given review doesn't have to cover all of them — scope follows what's asked. It also adjusts priorities by stage: a report still in development gets judged mainly on structure and content, while a live report gets judged mainly on whether anyone opens it.
Usage data comes from Python scripts in scripts/: one pulls a workspace-level view of report ranking and load times, another drills into daily views and per-viewer breakdowns for a single report, and a third audits who has access and through which channel. For cross-workspace last-visited timestamps without a tenant admin role, it falls back to an undocumented DataHub V2 endpoint, and the skill calls out that this path isn't officially supported and can break.
When calculating adoption, the skill filters out service accounts, developers and support staff so they don't inflate reach numbers, and it tracks trends using a rolling 7-day average instead of raw daily counts. Layout and visual design checks are handed off to a separate pbi-report-design skill.
What it helps with
- check whether a Power BI report is actually being viewed
- find reports in a workspace that nobody opens anymore
- diagnose a drop in report views
- review page layout and structure before a release
- audit who has access to a report and how they got it
Example prompts for the agent
- Review the Sales Overview report's usage over the last 28 days
- Check if this report is actually being used and show audience reach
- Audit distribution and subscriptions for this report's workspace
How to install review-report
1Plugin marketplace
/plugin marketplace add data-goblin/power-bi-agentic-development/plugin install reports@power-bi-agentic-developmentThis installs the whole reports plugin with all its skills
2Skills CLI (Vercel)
npx skills add data-goblin/power-bi-agentic-development --skill review-report -a claude-code3Manually: put the files in place
~/.claude/skills/review-report/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/review-report/
1Skills CLI (Vercel)
npx skills add data-goblin/power-bi-agentic-development --skill review-report -a codex2Manually: put the files in place
.agents/skills/review-report/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add data-goblin/power-bi-agentic-development --skill review-report -a cursor2Manually: put the files in place
.cursor/skills/review-report/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install data-goblin/power-bi-agentic-development plugins/reports/skills/review-report2Manually: put the files in place
.github/skills/review-report/SKILL.md1Skills CLI (Vercel)
npx skills add data-goblin/power-bi-agentic-development --skill review-report -a gemini-cli2Platform CLI
gemini skills install https://github.com/data-goblin/power-bi-agentic-development --path plugins/reports/skills/review-reportManually: put the files in place
.devin/skills/review-report/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about review-report
How do I install review-report in Claude Code?
Run /plugin marketplace add data-goblin/power-bi-agentic-development, then /plugin install reports@power-bi-agentic-development.
What does review-report do?
It runs a structured audit of a Power BI report — covering usage, design, structure and performance — and produces a ranked list of findings with concrete fixes.
What permissions does review-report need to pull usage data?
Basic view data needs any workspace role, model-level checks need Contributor access or higher, and distribution or subscription audits need a tenant-level Fabric Admin role.