A collection of skills and MCP systems to enable users of CLI, VSCode, Claude to operate over Microsoft Fabric
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.
This repository also configures its own agents. See what skills-for-fabric tells them →
Agent Claude Code ✓ vendor
Manage Microsoft Fabric operational excellence across capacity planning, governance, security, cost optimization, and observability. Use when the request involves workspace administration, capacity monitoring, access control, compliance policies, cross-workload operational concerns, or workspace documentation and…
Agent Claude Code ✓ vendor
Build full-stack applications on top of Microsoft Fabric using Python, ODBC, XMLA, and REST APIs. Use when the request involves building applications connected to Fabric data. Delegates endpoint-specific implementation to specialized skills.
Agent Claude Code ✓ vendor
Orchestrate end-to-end Microsoft Fabric data engineering workflows that span multiple workloads and personas. Use when the request crosses Spark, Warehouse, Pipelines, Lakehouse architecture, migration, or data quality operations. Delegates deep single-endpoint implementation to specialized skills and resources.
Agent Claude Code ✓ vendor
Answer questions about Power BI artifacts — reports, and semantic models — by discovering artifacts, inspecting report metadata and semantic model schemas, resolving entity values, generating DAX queries, and executing them against the Fabric MCP endpoint. Use when the user asks data questions about Power BI reports…
Agent Claude Code ✓ vendor
Orchestrate end-to-end workload migration from Azure Synapse Analytics, Azure HDInsight, or Databricks to Microsoft Fabric. Handles migration assessment, phased execution planning, utility API porting (mssparkutils/dbutils → notebookutils), connectivity migration (Linked Services/mounts → Data Connections/OneLake…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: