Activator CLI
Creates and inspects Fabric Activator (Reflex) alerts: rules, their data sources...
Install
npx skills add microsoft/skills-for-fabric --skill activator-cli -g -a claude-code -y- Repository
- microsoft/skills-for-fabric1.3k
- Category
- Engineering
- Updated
- 6d ago
- License
- MIT
- Context cost
- Mediumabout 2,790 tokens
- Runs scripts
- No, instructions only
What it does
Creates and inspects Fabric Activator (Reflex) alerts: rules, their data sources, conditions, and the Teams or email action they fire, plus decoding an existing ReflexEntities definition. Choose it whenever someone wants to be told, or something done, when values cross a threshold. The pipeline delivering those values is eventstream-cli.
Telemetry, MANDATORY. Every
api.fabric.microsoft.comcall must carryx-ms-fabric-skill: activator-cli(az rest:--headers "x-ms-fabric-skill=activator-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
activator-clifor every Fabric Activator / Reflex item, both authoring alert rules and inspecting existing alerts. The streaming topology that feeds an alert belongs toeventstream-cli, the KQL database behind it toeventhouse-cli, and Power BI report questions tofabriciq.
Fabric Activator (Reflex), CLI Skill
This one skill owns Fabric Activator / Reflex items: alert rules, their sources, their actions, and the ReflexEntities.json definition that holds them.
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, entity schemas, templates and gotchas; acting without it produces invalid ReflexEntities.json payloads and 400s.
The reference is needed to act, not to ask. If the request is under-specified and your next message will be a clarifying question with no Fabric call in it, ask it now and read the reference when you go on to act.
