What problem does it solve? Setting up alerts, notifications, and automated actions on Microsoft Fabric data requires hand-crafting complex ReflexEntities.json definitions with nested entity graphs, stringified templates, and Base64-encoded payloads, which is error-prone and poorly documented. ## Core Features & Use Cases - Activator Item CRUD: Create, update, and delete Reflex items through the Fabric /reflexes REST API using az rest with correct token audience and LRO polling. - Rule Authoring: Build AttributeTrigger and EventTrigger rule templates with detection conditions, aggregations, occurrence options, and dimensional filters. - Multi-Source Support: Connect rules to Eventstream, KQL/Eventhouse, Real-time Hub, and Digital Twin Builder / Ontology sources. - Action Bindings: Wire Teams messages, emails, and Fabric item invocations (Pipelines, Notebooks, Spark jobs, Dataflows, UDFs) to rule triggers. - Use Case: A user asks to be notified on Teams when sensor temperature exceeds 30 degrees; the skill resolves the workspace and KQL database, validates the query, assembles the entity graph, and publishes a running alert rule. ## Quick Start Ask the assistant to create an alert that sends you a Teams message when a value in your Fabric Eventhouse table crosses a threshold.