Activator Authoring Cli
Create alerts, notifications, and automated actions on Fabric data and events via Fabric REST API and `az rest` CLI. **Invoke this skill** whenever the user wants to: (1) create, update, or delete an alert or notification flow, (2) send a Teams message, email, or run a Fabric item when something happens, (3) connect alert logic to Eventhouse, Eventstream, Real-time Hub, or DTB / Ontology data, (4) adjust thresholds, filters, event triggers, or actions, (5) troubleshoot or change an existing Activator/Reflex definition. Invoke this skill **before** asking clarifying questions — clarification is part of this skill, not a preamble to it. Triggers: "create an alert", "create an activator", "create a reflex", "create an activator item", "create an alert item", "notify me when", "let me know when", "take action when", "send me an email when", "send a teams message when", "run a pipeline when", "update an alert", "delete an alert", "activator rule".
30-Second Summary
Activator Authoring Cli is an agent-readable workflow from microsoft/skills-for-fabric for activator authoring cli.
It gives the agent a trigger, ordered guidance, and source-backed checks instead of treating activator authoring cli as a generic tool.
Use it as a brief only while the linked SKILL.md remains available and the risk boundary is still accurate.
1-Minute Read
What it is
Activator Authoring Cli packages instructions from microsoft/skills-for-fabric into a reusable agent skill brief. The original source is a public SKILL.md file, so the brief can point readers back to the executable workflow instead of a product landing page.
When to use it
Use it when a user asks for help around activator authoring cli and the agent needs a repeatable workflow, checklist, or review path rather than broad background information.
How to test it first
Open the linked SKILL.md, confirm the trigger and procedure still match activator authoring cli, list the risk boundary, then ask the agent to apply the smallest read-only step to a sample task.
Watch out
Do not present this as a generic app or platform. Keep the scope tied to microsoft/skills-for-fabric. Risk boundary: CI/CD, deploy, release, rollback, and migration steps must start with read-only inspection and an approval gate; database, Fabric workspace, notebook, lakehouse, warehouse, or Power BI changes need credential and production-data approval; cloud resources, RBAC, credentials, tokens, and private keys must not be changed or exposed without a separate approval; Microsoft Fabric-specific workflow; do not describe it as a generic data engineering skill.