Published skills
code-review
Reviews code for correctness, naming conventions, style, error handling, security, and scaling concerns. Use this skill when reviewing code, checking a diff, auditing a function, or asking about code quality, covering Python, PySpark, SQL, KQL, DAX, and data-engineering patterns.
drift-audit
Audits the Microsoft Fabric and Power BI What's New docs source for drift since a prior commit SHA or date, detecting new GA/preview features, syntax additions, deprecations, and tooling changes. Use for monthly staleness checks or auditing what changed.
fabric-cli
This skill utilizes the Fabric CLI `fab`, a filesystem-style interface for Fabric and Power BI REST. It covers path syntax, authentication reuse from `az login`, and navigation commands.
fabric-data-agent
Configure Microsoft Fabric Data Agents (GA March 2026) for conversational Q&A, leveraging Azure OpenAI Assistant APIs. It supports up to five data sources like Lakehouse, Warehouse, and Microsoft Graph, covering four configuration layers including agent instructions and example queries.
fabric-eventhouse
This skill is for Microsoft Fabric Eventhouse / KQL Database, covering connection details like cluster URI via kqlDatabases REST and az rest patterns. It also includes authoring aspects such as safe schema evolution with .create-merge, various ingestion methods, streaming policies, data mappings, and management policies.
fabric-eventstream
This skill is for Microsoft Fabric Eventstream, routing CDC, Event Hubs, Kafka, IoT, HTTP, and MQTT events into Lakehouse, Eventhouse, Activator, or derived streams. It supports various source connectors like Azure SQL, PostgreSQL, MongoDB, Cosmos DB CDC, Event Hubs, IoT Hub, and Kafka.
fabric-gotchas
This skill assists in troubleshooting common Microsoft Fabric errors, including authentication issues (401, 403, login failed), entity not found errors (404, PowerBIEntityNotFound), snapshot conflicts, and data type errors (nvarchar/datetime/money) in Warehouse.
fabric-mlv
Utilize Fabric Materialized Lake Views (MLVs) with CREATE MATERIALIZED LAKE VIEW Spark SQL (GA March 2026) and the @fmlv.materialized_lake_view PySpark decorator on a schema-enabled lakehouse. It supports full syntax for managing MLVs, including data quality rules, partitioning, and optimal refresh.
fabric-monitoring
Monitor Fabric Warehouse queries using OPTION (LABEL = '...') for tracking and the queryinsights schema. Be aware of the 30-day retention, 15-minute data lag, and the 'Invalid object name' issue on new warehouses.
fabric-rest-api
This skill handles Microsoft Fabric REST API patterns, including listing and paginating workspaces/items, managing long-running operations with polling, understanding the distinction between runtime item IDs and platform logical IDs, and the 201-or-202 create pattern.
fabric-security
This skill covers the Fabric security and permission model, detailing its three layers: workspace roles (Admin, Member, Contributor, Viewer), item-level permissions (Read, ReadData, ReadAll), and SQL GRANT/DENY/REVOKE. It also explains how Admin, Member, and Contributor roles can bypass RLS/CLS/DDM.
fabric-semantic-model-ai-instructions
Use to configure AI instructions on a Power BI semantic model, the 10,000-character blob attached via "Prep data for AI" → "Add AI instructions". It applies wherever Copilot uses the model, covering business context, terminology, date rules, and more.
fabric-spark
This skill covers PySpark/Spark in Microsoft Fabric notebooks, addressing data ingestion constraints, OneLake URI formats, identity and session configuration, mssparkutils, lakehouse schema management, and table maintenance operations.
fabric-tmdl-api
This skill covers the Fabric Semantic Model Definition API (create, get, update), detailing the two-audience rule, the necessity of including all parts in updateDefinition payloads, the exclusion of .platform, base64 encoding, and LROs.
fabric-tmdl
TMDL (Tabular Model Definition Language) authoring rules for Fabric and Power BI semantic models. These rules guide editing .tmdl files, adding measures or columns, defining relationships, configuring Direct Lake partitions, and debugging validation errors, covering syntax like tabs, /// descriptions, and single-quoting.
fabric-variable-library
Manages the Microsoft Fabric Variable Library as config-as-code for parameterizing notebooks and pipelines across environments. It details definition files, supported variable types, and notebook consumption via `notebookutils.va`.
fabric-warehouse
For T-SQL against Fabric Warehouse (NOT Fabric SQL Database), this skill covers unsupported types and features like FOR XML and recursive CTEs, alongside schema evolution such as ADD nullable and DROP COLUMN.
pbid-tom-live
Script an open Power BI Desktop model using its localhost Analysis Services proxy, leveraging TOM for metadata and ADOMD.NET for DAX. This involves PowerShell setup with AMO/TOM + ADOMD NuGet DLLs, port discovery, and connecting to the model for operations like SaveChanges.
pbip-project-structure
This skill is for working with PBIP (Power BI Project) folders, the text-based developer format replacing binary .pbix files. It covers folder structure, entry-point files, report types (byPath vs byConnection), .pbism versioning, and PBIX-to-PBIP extraction.
pbir-bookmarks
Use this skill for creating, editing, or wiring Power BI PBIR bookmarks within bookmarks.json and individual bookmark.json files. It covers bookmark structure, options flags, and explorationState shape.
pbir-cli
This skill enables using the pbir CLI to inspect or edit local Power BI PBIR reports. It covers path syntax with type suffixes, glob patterns, and dot-notation, along with verb-noun groups for various report components and discovery verbs.
pbir-conditional-formatting
Use when adding conditional formatting to a Power BI visual, such as per-point bar/column colors, diverging gradients, line segment colors, marker transparency, data bars, or conditional icons. It supports three approaches: measure-based (using theme tokens), FillRule linear gradients, and rule-based Conditional.Cases.
pbir-filters
Used for authoring filter bodies in Power BI PBIR reports (report.json, page.json, visual.json filterConfig.filters). It covers scopes (Report, Page, Visual), filter types (Categorical, Advanced, TopN, etc.), and filter body shape (Version 2, From[] aliases, Where[] using SourceRef.Source).
pbir-pages
For authoring or editing page.json/pages.json within a Power BI PBIR report's definition/pages folder. It covers top-level page properties such as name, display options, dimensions, type, visibility, alignment, page order, active page, and canvas background.
pbir-report-workflow
This skill guides you through scaffolding and building new Power BI reports end-to-end from a published semantic model using the pbir CLI. It covers a 10-step workflow, including requirements, model field discovery, report scaffolding, page management, and visual hierarchy design.
pbir-themes
Use when authoring or editing a Power BI report theme JSON. It covers top-level theme properties such as name, dataColors palette, semantic colors, sentiment, text classes, visual styles, and inheritance.
pbir-visual-json
Use for editing visual.json files in Power BI PBIR report's visuals/ folder. It covers top-level structure, including visual vs visualGroup, filterConfig, and root-level isHidden, along with expression literal suffixes like 'text', 14D, 14L, 2.4M, '#FF0000', datetime, and null.
fabric-auth
This skill helps with authenticating to Microsoft Fabric APIs, resolving 401 Unauthorized errors, and setting token audience/scope for various Fabric services. It covers the token-audience table, OneLake's storage.azure.com/.default requirement, and az login variants.
fabric-database
This skill is for working with Fabric SQL Database, an Azure SQL Database within a Fabric workspace. It's a distinct engine from Fabric Warehouse, supporting advanced features like nvarchar, triggers, and recursive CTEs, and uses Entra ID authentication exclusively.
fabric-error-handling
Provides error handling conventions for Fabric notebooks, distinguishing Tier 1 (hard-fail) from Tier 2 (soft-fail with per-item tracking). It covers standard result structures, STRICT settings, and per-item metrics.
Category alert