fabric-capacity — Claude Code skill: Microsoft Fabric capacity monitoring
fabric-capacity — a skill that tracks utilization of Microsoft Fabric capacities in real time, identifies which workloads consume CU, and manages capacity state through the API.
GPL-3.0 ★ 1,104 updated 2026-10-28
/plugin marketplace add data-goblin/power-bi-agentic-development
/plugin install fabric-admin@power-bi-agentic-developmentWhat fabric-capacity does
The skill queries the Fabric Capacity Metrics semantic model via DirectQuery tables to answer questions about utilization, throttling, per-item CU consumption, and what is currently running. It can start or pause a capacity through the fab CLI and report its state from scripts or status bars.
Internally, it runs DAX queries against DirectQuery tables like CU Detail and Metrics By Item, and invokes fab commands for capacity management. The account must have capacity admin privileges for every capacity queried. DirectQuery tables require an M parameter with the capacity ID in uppercase, passed inside a DEFINE block; omitting it causes the connector to fail. The Metrics app lives in a Pro workspace (XMLA is unavailable), and its OAuth token expires after 90 days of disuse, requiring credential re-entry.
What it helps with
- check current capacity utilization percentage
- find which items and operations are consuming CU
- diagnose throttling and carry-forward issues
- start or stop a capacity from code
- monitor Fabric capacity state continuously
Example prompts for the agent
- What's the current utilization on the F2 capacity?
- Show me CU usage by Planning session for the last hour
- Start the
my-capacitycapacity and report its state
How to install fabric-capacity
1Plugin marketplace
/plugin marketplace add data-goblin/power-bi-agentic-development/plugin install fabric-admin@power-bi-agentic-developmentThis installs the whole fabric-admin plugin with all its skills
2Skills CLI (Vercel)
npx skills add data-goblin/power-bi-agentic-development --skill fabric-capacity -a claude-code3Manually: put the files in place
~/.claude/skills/fabric-capacity/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/fabric-capacity/
1Skills CLI (Vercel)
npx skills add data-goblin/power-bi-agentic-development --skill fabric-capacity -a codex2Manually: put the files in place
.agents/skills/fabric-capacity/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add data-goblin/power-bi-agentic-development --skill fabric-capacity -a cursor2Manually: put the files in place
.cursor/skills/fabric-capacity/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install data-goblin/power-bi-agentic-development plugins/fabric-admin/skills/fabric-capacity2Manually: put the files in place
.github/skills/fabric-capacity/SKILL.md1Skills CLI (Vercel)
npx skills add data-goblin/power-bi-agentic-development --skill fabric-capacity -a gemini-cli2Platform CLI
gemini skills install https://github.com/data-goblin/power-bi-agentic-development --path plugins/fabric-admin/skills/fabric-capacityManually: put the files in place
.devin/skills/fabric-capacity/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 fabric-capacity
How do I install fabric-capacity in Claude Code?
Run these in order: /plugin marketplace add data-goblin/power-bi-agentic-development, then /plugin install fabric-admin@power-bi-agentic-development, then npx skills add data-goblin/power-bi-agentic-development --skill fabric-capacity -a claude-code, and open ~/.claude/skills/fabric-capacity/SKILL.md.
What does fabric-capacity do?
It queries the Capacity Metrics semantic model to show real-time capacity utilization, breaks down CU consumption by workload and operation, and lets you start or pause capacities via the fab API.
Why does my DirectQuery fail with a credential error?
The account must be a capacity admin for every capacity you query. DirectQuery tables require an M parameter containing the capacity ID in uppercase, passed inside a DEFINE block; the connector cannot work without it.