fabric-activatorlisted

Use for Microsoft Fabric Activator — the `Reflex` item type (Reflex and Activator are the same item) that watches data and fires rules and alerts. Covers `ReflexEntities.json` as Git and REST see it: a flat JSON array of entities wired by `uniqueIdentifier`, with `definition.instance` an escaped JSON string and not a nested object; the `/reflexes` REST namespace and its permission split — List needs only a viewer role, but `getDefinition` needs read AND write; `displayName` not `name` on create; query sources (Power BI, KQL queryset, Real-Time Dashboard) versus streaming (Eventstream, Fabric events, Azure Blob events); actions and their silent parameter coercion (Copy job takes none, a bad number becomes 0); the preview remote MCP server; and the limits and costs that bite — 500 rules per item, 10,000 events/s stops a rule, stopping a rule does not stop its billed event listener, and a Blob-events source, Power BI source or User Data Function action makes a Git commit or a deployment fail.
wardawgmalvicious/agent-config · ★ 1 · AI & Automation · score 80

Install: claude install-skill wardawgmalvicious/agent-config

# Fabric Activator (the `Reflex` item) Activator watches data and takes an action when a condition is met. It is the **deterministic, non-LLM** half of Fabric's reactive story. **`Reflex` and `Activator` name the same item type.** Learn says so outright, and the split is consistent: `Activator` is the portal and product name, `Reflex` is what the REST API, the `ItemType` enum, the `.platform` file and the Git folder suffix all use. Expect both in the same sentence and do not treat a `Reflex` in a payload as a different thing. Three neighbours own adjacent ground, and **two of them cannot be reached by name from here** — their `paths:` globs do not match a `.Reflex` file, so naming them yields `Unknown skill`. Open the item's own definition file instead: | Adjacent work | How to get there | | --- | --- | | Wiring an Activator destination onto an Eventstream, or `Set alert` from one | Open the `.Eventstream` item's definition | | The KQL database a `kqlSource-v1` queries | Open the `.Eventhouse` / `.KQLDatabase` item's definition | | LRO polling, `continuationToken` pagination, token audiences | `fabric-rest-api`, `fabric-auth` — both reachable by name | | `fab` invocation and `fab api` passthrough | `fabric-cli` — reachable by name | ## 1. What is on disk A Git-synced Activator is a `<name>.Reflex/` directory holding exactly two files: | File | Required | What it is | | --- | --- | --- | | `ReflexEntities.json` | yes | The whole configuration — sources, objects, attribu