activator-cli

1> **Telemetry — MANDATORY.** Every `api.fabric.microsoft.com` call must carry
2> `x-ms-fabric-skill: activator-cli` (`az rest`: `--headers "x-ms-fabric-skill=activator-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 `activator-cli` for every Fabric Activator / Reflex item — both authoring alert rules and inspecting existing alerts. The streaming topology that feeds an alert belongs to `eventstream-cli`, the KQL database behind it to `eventhouse-cli`, and Power BI report questions to `fabriciq`.
9 
10# Fabric Activator (Reflex) — CLI Skill
11 
12This one skill owns Fabric Activator / Reflex items: alert rules, their sources, their actions, and the `ReflexEntities.json` definition that holds them.
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, entity schemas, templates and gotchas; acting without it produces invalid `ReflexEntities.json` payloads and 400s.
15…