activator-authoring-cli

Name: activator-authoring-cli
Availability: InStock
Author: Microsoft

Automates Fabric alerts and Reflex definitions via CLI-authored Activator items and Python payloads.

952|267|Updated Feb 17, 2026

Search Tags:#automation #cli #rules #fabric #reflex #activator

Ready to run

npx skills add https://github.com/microsoft/skills-for-fabric --skill activator-authoring-cli

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: activator-authoring-cli
Source: https://github.com/microsoft/skills-for-fabric/tree/main/plugins/fabric-authoring/skills/activator-authoring-cli
Command: npx skills add https://github.com/microsoft/skills-for-fabric --skill activator-authoring-cli

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Developers and operators need a CLI-driven way to author Activator items and Reflex definitions for Fabric workflows. This skill streamlines the creation, updating, and deletion of alerts, reflexes, and actions, and enables integration with Eventstream, Eventhouse, Real-time Hub, and Digital Twin / Ontology sources.

Core Features & Use Cases

Create, update, and delete Activator items and reflexes from the CLI, including rule templates and action bindings.
Wire rules to Fabric items and actions via standalone fabricItemAction-v1 entities, enabling pipelines, notebooks, dataflows, or UDFs to run in response to alerts.
Use source graphs (Eventstream, KQL/Eventhouse, Digital Twin Builder / Ontology, Real-Time Hub) and readbacks to assemble end-to-end automation pipelines.
Follow guidelines for REST API usage, authentication, LRO handling, and safe metadata updates when evolving definitions.

Quick Start

Install the activator-authoring-cli skill and begin by creating a new activator rule from a template.

Frequently Asked Questions about activator-authoring-cli

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create Activator rules and Reflex definitions from the CLI?▼

You can create Activator rules and Reflex definitions from the CLI by using command-line authoring to generate rule templates and action bindings for Fabric alerts. This approach streamlines creating, updating, and deleting alerts directly from your terminal environment.

What is a standalone fabricItemAction-v1 entity in Fabric Activator?▼

A standalone fabricItemAction-v1 entity is a binding mechanism used to wire Activator rules to Fabric items. It enables pipelines, notebooks, dataflows, or user-defined functions to execute automatically in response to triggered alerts.

Can I wire Fabric Activator alerts to Eventstream and KQL sources?▼

Yes, you can wire Fabric Activator alerts to Eventstream, KQL or Eventhouse, Real-time Hub, and Digital Twin Builder or Ontology sources. This allows you to assemble end-to-end automation pipelines using source graphs and readbacks.

Do I need to understand the ReflexEntities.json schema to author Activator items?▼

Yes, authoring Activator items requires a solid understanding of the ReflexEntities.json schema, Python payload assembly, and az rest authentication against the Fabric API with Long Running Operation handling.

What's the best way to automate Fabric alerts without using the portal?▼

The best way to automate Fabric alerts without the portal is using a CLI-driven approach to author Activator items and Reflex definitions. This allows you to apply REST API usage, authentication, and safe metadata updates when evolving definitions programmatically.

Why do I need LRO handling when updating Reflex definitions via the Fabric API?▼

LRO or Long Running Operation handling is required when updating Reflex definitions via the Fabric API because asynchronous operations need status polling. Proper LRO handling ensures safe metadata updates and successful completion of definition evolution.