powerbi-navigator

Route Power BI report inquiries to pre-configured prompts or navigators.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/JinLee794/L.C.G --skill powerbi-navigator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: powerbi-navigator
Source: https://github.com/JinLee794/L.C.G/tree/main/.github/skills/powerbi-navigator
Command: npx skills add https://github.com/JinLee794/L.C.G --skill powerbi-navigator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing and remembering exact Power BI report names and corresponding prompts slows down analysis workflows. This navigator routes natural-language requests to the correct pre-configured Power BI prompts or reports, reducing cognitive overhead and speeding up discovery.

Core Features & Use Cases

  • Automatic routing: maps user questions to the appropriate powerbi-*.prompt.md file or legacy prompt when available.
  • Catalog-driven discovery: presents a concise catalog of available Power BI prompts/reports when the user is unsure what to ask.
  • Fallback builder workflow: if no match exists, chains to dev-powerbi-prompt-builder to create a new prompt.

Quick Start

Ask a Power BI question by name or description and I will route you to the correct pre-configured prompt.

Frequently Asked Questions about powerbi-navigator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find the right Power BI report when I only know the general topic?

To find the right Power BI report, this navigator uses a catalog-driven discovery mechanism that presents a concise list of available pre-configured prompts based on your general description. It maps your natural-language request to the correct report automatically.

Can I use natural language to route queries to specific Power BI reports?

Yes, you can use natural language to route queries to specific Power BI reports by mentioning the report by name or alias. The navigator applies direct-match triggers to map your inquiry to the appropriate pre-configured prompt.

What happens if no pre-configured Power BI prompt matches my query?

When no pre-configured Power BI prompt matches your query, the navigator applies a fallback workflow that chains to the dev-powerbi-prompt-builder to create a new prompt for your specific analytical needs.

How does the navigator handle heavy DAX queries and report rendering?

The navigator delegates all heavy DAX queries, report discovery, and rendering tasks to the pbi-analyst subagent. This ensures the routing mechanism remains lightweight while complex analysis is handled by the dedicated subagent.

Do I need to remember exact Power BI report names to use this routing tool?

No, you do not need to remember exact Power BI report names. The routing tool uses catalog-driven discovery and alias matching to map your natural-language requests to the correct pre-configured prompts, reducing cognitive overhead.

What are the limitations of using a catalog-driven navigator for Power BI report discovery?

The navigator relies on pre-configured prompts and direct-match triggers to determine the route, meaning it requires existing catalog entries. If no match exists, it must fall back to a prompt builder rather than executing the query directly.