# Activator CLI

Creates and inspects Fabric Activator (Reflex) alerts: rules, their data sources...

- Repository: https://github.com/microsoft/skills-for-fabric (1306 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-10-29
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add microsoft/skills-for-fabric --skill activator-cli -g -a claude-code -y`
Codex: `npx skills add microsoft/skills-for-fabric --skill activator-cli -g -a codex -y`
Cursor: `npx skills add microsoft/skills-for-fabric --skill activator-cli -g -a cursor -y`
Gemini CLI: `npx skills add microsoft/skills-for-fabric --skill activator-cli -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add microsoft/skills-for-fabric`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

> **Telemetry, MANDATORY.** Every `api.fabric.microsoft.com` call must carry
> `x-ms-fabric-skill: activator-cli` (`az rest`: `--headers "x-ms-fabric-skill=activator-cli"`),
> including every LRO poll, `fabric_lro` and retry. Snippets omit it, add it anyway.

> **CRITICAL NOTES**
> 1. To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering
> 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
> 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`.

# 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.

## Mode selection

The rest: https://github.com/microsoft/skills-for-fabric/blob/HEAD/plugins/fabric-skills/skills/activator-cli/SKILL.md