Skip to content
TrustedSkillsbeta
Back to all skills

Power Bi Performance Troubleshooting

Official
github·vlatest·data·MIT

Diagnose Power BI report slowness and errors by analyzing data model, queries, and gateway configurations.

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add github/awesome-copilot --skill power-bi-performance-troubleshooting -a claude-code
  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

github

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    No SKILL.md was found in the skill's directory.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned github/awesome-copilot at 6c4d33b9cf.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
0 files
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps identify and resolve performance issues in Power BI reports, such as slow query execution, high memory usage, or rendering delays. It provides actionable insights into optimizing data models, DAX expressions, and report configurations for better efficiency.

When to use it

  • Your Power BI report is taking too long to load or refresh.
  • You're experiencing high CPU or memory consumption in Power BI Desktop or Service.
  • Users are reporting slow performance when interacting with visualizations.
  • You want to optimize a complex data model for faster query responses.

Key capabilities

  • Analyzes DAX queries for inefficiencies and suggests optimizations.
  • Identifies large tables or unused columns that may be impacting performance.
  • Recommends best practices for data modeling, such as proper use of relationships and partitions.
  • Detects potential bottlenecks in report visuals and data sources.

Example prompts

  • "Why is my Power BI report slow to load?"
  • "How can I optimize this DAX formula for better performance?"
  • "What are the top 3 ways to improve Power BI memory usage?"

Tips & gotchas

  • Ensure your Power BI model is up to date and connected to accurate data sources before running diagnostics.
  • Performance issues may depend on external factors like dataset size or server configuration, so consider these when interpreting results.