eventhouse-cli

1> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry
2> `x-ms-fabric-skill: eventhouse-cli` (`az rest`: `--headers "x-ms-fabric-skill=eventhouse-cli"`),
3> including every LRO poll, `fabric_lro` and retry. Snippets omit it — add it anyway.
4 
5> **CRITICAL NOTES**
6> 1. To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering
7> 2. 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
8> 3. **Skill disambiguation**: use `eventhouse-cli` for anything expressed in KQL or stored in a KQL Database. Use the matching `eventstream-cli` mode for streaming topology, and the matching `sqldw-*` skill for T-SQL against a Warehouse or Lakehouse SQL endpoint.
9 
10# Fabric Eventhouse / KQL Database -- CLI Skill
11 
12This one skill owns Fabric Eventhouse and KQL Database: schema and ingestion management plus read-only KQL analytics.
13 
14It 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.
15 
16## Mode selection
17 
18| Mode | Use when the request ... | Example triggers | Read this first |
19…