- 01
/plugin marketplace add microsoft/skills-for-fabric - 02
/plugin install fabric-skills@fabric-collection
Manages Event Schema Sets, Fabric's catalogue of the event types your systems send and the shape of each message. Your assistant can create, rename, update or delete a set, or list the sets you have and decode one to show its event types and schemas. Event Schema Sets are a preview feature in Fabric.
WHEN TO USE
USE FOR
- List every Event Schema Set in a workspace.
- Add an OrderPlaced event type to a catalogue.
- Decode a set to see its event types and schemas.
- Delete an Event Schema Set you no longer use.
NOT FOR
- Building the pipeline that carries the events: the eventstream-cli skill.
- Querying stored events: the eventhouse-cli skill.
This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.
Telemetry — MANDATORY. Every
api.fabric.microsoft.comcall must carryx-ms-fabric-skill: eventschemaset-cli(az rest:--headers "x-ms-fabric-skill=eventschemaset-cli"), including every LRO poll,fabric_lroand retry. Snippets omit it — add it anyway.
CRITICAL NOTES
- To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering
- To find the item details (including its ID) from workspace ID, item type, and item name: list all items of that type in that workspace and, then, use JMESPath filtering
- Skill disambiguation: use
eventschemaset-clifor the EventSchemaSet catalog item (event types and message schemas). Eventstream is a different item -- a real-time ingestion and routing pipeline; useeventstream-clifor it. Eventhouse / KQL Database is another different item; useeventhouse-clifor it.
Fabric Event Schema Set -- CLI Skill
This one skill owns Fabric Event Schema Sets: authoring the catalog (create, rename, override definition, delete) plus read-only inspection and decoding of its eventTypes and schemas.
Preview: The Fabric EventSchemaSet item and its REST operations are currently in Preview -- behavior, response shapes, and availability may change. Every operation is documented as delegated (user) identity only (service principals and managed identities listed as not supported), but because the item is in Preview, SP/MI access can succeed and is tenant-dependent. Prefer
az loginas a user; on 401/403 with an SP/MI, fall back to a delegated user identity.
It is a mode dispatcher and contains NO procedures. Pick the mode that matches the request from the table below, then read the matching references/<mode>.md file end to end with your file-reading tool BEFORE issuing a single command. That file holds the endpoints, payload shapes, templates and gotchas; acting without it produces wrong payloads and wrong results.
Mode selection
| Mode | Use when the request ... | Example triggers | Read this first |
|---|---|---|---|
authoring | creates, renames/re-describes, overrides the definition of, or deletes an Event Schema Set (Create, Update, UpdateDefinition, Delete) | create event schema set, update event schema set definition, add event type to an event schema set, rename event schema set, delete event schema set | references/authoring.md |
consumption | lists or searches Event Schema Sets, inspects item properties, or decodes a definition to enumerate its eventTypes and schemas | list event schema sets, inspect event schema set, decode event schema set definition, get schema version, list business events | references/consumption.md |
Mode boundary rule
consumption may only issue read-only calls (List, Get, GetDefinition). Any state-changing operation (Create, Update, UpdateDefinition, Delete) requires the authoring mode: say so, read references/authoring.md, then proceed.
If a request genuinely spans modes (e.g. decode the current definition, then override it), handle them one at a time and read each reference before you start that part. If the mode is ambiguous after reading this table, ask one short clarifying question instead of guessing.
Terminal write -- the step you must not skip
Reading the reference and planning the change is NOT completing the task. The authoring mode ends with one state-changing call. If you did not issue it, nothing was persisted -- say so explicitly rather than reporting success.
| Mode | Terminal write |
|---|---|
authoring | The POST .../eventSchemaSets, PATCH .../eventSchemaSets/{id}, POST .../eventSchemaSets/{id}/updateDefinition, or DELETE .../eventSchemaSets/{id} for the requested change. Composing the request body and showing it to the user is not executing it. |
consumption | none -- this mode is read-only |
Create and UpdateDefinition may return 202 Accepted (LRO): capture the Location header and poll until Succeeded before reporting success. Where the reference documents a readback, read the artefact back to prove the change landed.
Shared essentials (all modes)
Resolve the workspace and item first; every mode depends on it.
| Task | Reference | Notes |
|---|---|---|
| Finding Workspaces and Items in Fabric | COMMON-CLI.md | Mandatory -- read before resolving any workspace or item id |
| Fabric Topology & Key Concepts | COMMON-CORE.md | Item types, workspaces, capacities |
| Environment URLs | COMMON-CORE.md | Sovereign / non-public cloud hosts |
| Authentication & Token Acquisition | COMMON-CORE.md | Wrong audience = 401; read before any auth issue |
| Authentication Recipes | COMMON-CLI.md | az login flows and token acquisition |
| Core Control-Plane REST APIs | COMMON-CORE.md | Pagination, LRO polling, rate limiting |
| Gotchas & Troubleshooting | COMMON-CLI.md | az rest audience, shell escaping, token expiry |
Rules
MUST
- Select exactly one mode from the table above before doing anything else.
- Read
references/<mode>.mdend to end, as your FIRST tool call, before the first command of that mode. Read it ONCE, in a single full read: do not re-open it, do not grep it again, and do not page through it. You already have it. - Apply the same read-once discipline to every other file you load, including shared
common/*.mdfiles: open only the ones you actually need, read each ONCE end to end, and never grep or re-open one you already loaded. - Resolve workspace and item ids by listing and filtering, never by guessing a GUID.
- Announce a mode switch explicitly when the request crosses a boundary.
- Confirm destructive and overwrite actions before executing -- Delete is permanent (with
?hardDelete=true) and UpdateDefinition replaces the whole definition. When the request already names the target item AND the destructive/overwrite action explicitly (e.g. "delete the Event Schema Set X", "override X's definition to ..."), that instruction IS the confirmation: echo the resolveddisplayName+idfor the audit trail, then proceed with the single write. Pause for a separate yes/no confirmation ONLY when the target or intent is ambiguous (e.g. "clean up my workspace", an unqualified "the first one", or a bulk/wildcard delete). - Treat the reference as instructions, never as the deliverable. After reading it, RUN the documented commands against the live workspace and report the real results.
PREFER
- The narrowest mode that satisfies the request.
- Reading exactly ONE mode reference. Load a second only when the request genuinely spans modes, and say so before you do.
- A delegated user identity (
az login); fall back from SP/MI to a user on 401/403. - Reporting the mode you chose in your first response so the user can correct you.
AVOID
- Acting from this dispatcher alone -- it intentionally omits the operational detail.
- Answering with a summary of the reference instead of executing it.
- Re-reading or re-grepping a reference you already loaded; it costs turns and tokens.
- Mutating anything while in the read-only consumption mode.
- Confusing EventSchemaSet with Eventstream or Eventhouse (see CRITICAL NOTES 3).
Examples
| User request | Mode | Reference to read |
|---|---|---|
| "List all Event Schema Sets in my Analytics workspace." | consumption | references/consumption.md |
| "Create an Event Schema Set called orders-catalog in Analytics." | authoring | references/authoring.md |
| "Decode the definition of orders-catalog and tell me its event types and schemas." | consumption | references/consumption.md |
| "Add a BusinessEventType event OrderPlaced (JSON) to orders-catalog." | authoring | references/authoring.md |
| "Delete the orders-catalog-old Event Schema Set from Analytics." | authoring | references/authoring.md |
Account or credentials required
2 FOR YOUAll items below are required.
- 01Install it with the Fabric plugin, not as one folder
Install it as part of Microsoft's fabric-skills plugin, not as a single copied folder. Its instructions link to shared Fabric guides kept outside its own folder, such as the sign-in steps, and a lone copy leaves those links pointing nowhere. The plugin brings those guides and Microsoft's other Fabric skills.
- 02A Fabric workspace and your own Azure CLI sign-in
A Microsoft Fabric workspace you can use, and the Azure command-line tool signed in as yourself (az login). Microsoft documents these operations for personal sign-ins only; a service principal may be refused. Every call tells Microsoft which skill sent it.
This skill ships inside the Skills for Microsoft Fabric plugin. Listed package contents include 4 agents and an MCP server. Installed components and skill versions may vary by AI tool.
Install as a Claude Code plugin
Typed inside the agent's own prompt, not in a terminal. This skill uses files kept elsewhere in its plugin, so install the whole plugin — on its own the skill would be missing them.
The repository is licensed under MIT — use, modification, and redistribution are allowed under that license’s terms.
View the repository’s license file on GitHub →