Microsoft Fabric Skills is a collection of reusable instructions and MCP systems that help AI assistants work with Microsoft Fabric workloads, APIs, queries, and operations. It is intended for users of GitHub Copilot CLI and compatible coding tools; the catalogue entries are the skills, agents, instructions, MCP systems, plugins, and rules distributed by the project.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add microsoft/skills-for-fabric --skill powerbi-report-planninggit clone --depth 1 https://github.com/microsoft/skills-for-fabricWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/microsoft/skills-for-fabric/powerbi-report-planning)<a href="https://agentmods.dev/skills/microsoft/skills-for-fabric/powerbi-report-planning"><img src="https://agentmods.dev/badge/skills/microsoft/skills-for-fabric/powerbi-report-planning/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/microsoft/skills-for-fabric/powerbi-report-planning"><img src="https://agentmods.dev/badge/skills/microsoft/skills-for-fabric/powerbi-report-planning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00150 | $0.04796 |
| Opus 5 | $0.00075 | $0.02398 |
| Sonnet 5 | $0.00030 | $0.00959 |
| Haiku 4.5 | $0.00015 | $0.00480 |
Grade A, and why
powerbi-report-planning scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 581 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Power BI Report Planning Skill
This skill orchestrates the full lifecycle for a new Power BI report:
Define -> Inspect -> Spec -> Approve -> Build -> Validate -> Publish
It is intentionally broader than a pure requirements-gathering flow: it captures the report spec and continues into implementation after the user approves.
Must/Prefer/Avoid
MUST
- Use this skill for broad report creation workflows that need requirements, dependency checks, approval, and build sequencing.
- Ask focused clarification questions one at a time and stop after the required decision is clear.
- Lock
_brief/report-spec.mdand get approval before implementation. - Route design decisions through
powerbi-report-designand file mechanics throughpowerbi-report-authoring.
PREFER
- Infer obvious answers from the prompt, model, existing PBIP files, or earlier rounds instead of re-asking.
- Inspect the semantic model before finalizing page scope or visual recommendations.
- Treat publishing as optional and only proceed when approved.
AVOID
- Do not use this skill for small, surgical edits to existing PBIR files.
- Do not build before the user approves the locked report spec.
- Do not duplicate detailed visual-design or PBIR-authoring guidance that belongs to companion skills.
Examples of When to Use
Use this skill when the user wants to create a new Power BI report and needs both:
- A guided requirements workflow.
- A path to implementation after approval.
Examples:
- "Let's create a new Power BI report from this semantic model."
- "Help me define and then build a Power BI report."
- "Use the report playbook to start a new report."
- "Create a reusable workflow for new Power BI reports."
Do not use this skill for a small edit to an existing report page. For
direct PBIR authoring tasks, use powerbi-report-authoring. For visual critique or
greenfield design guidance without the full guided workflow (a one-off
"redesign this" or "what should this look like?"), use
powerbi-report-design directly. This skill uses the design skill during
Rounds 3–4 — it does not replace it.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 581 lines · 150 tokens per session scan A 8ad6ecfe9512
powerbi-report-planning is a skill published in the GitHub repository microsoft/skills-for-fabric (1,140 stars, last pushed yesterday), licensed MIT. It adds 150 tokens to every session and 4,796 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…