$ loading_
List, inspect, and validate Microsoft Fabric Eventstream topology and configuration.
The material indicates an open-source prompt/documentation-style CLI skill focused on inspecting Microsoft Fabric Eventstream resources, with no built-in secret requirement or fixed third-party egress endpoint declared. Overall risk is low, but the README contains session-level instructional/update-check language, and real use would still involve Fabric/Azure control-plane access and resource enumeration, so execution boundaries should be verified under least privilege.
Metadata says no keys are required, but the README explicitly references authentication, token acquisition, `az login`, and `az rest`, indicating practical use typically relies on Azure/Fabric login state or access tokens. There is no evidence that the skill collects or uploads credentials; the main risk is misuse of the local CLI session rather than the skill itself.
No unrelated third-party endpoint is declared; the functionality points to the Microsoft Fabric Items REST API, which is consistent with the stated purpose and an expected service endpoint. The README also mandates a per-session update check, which may contact a remote version source, but there is no evidence of user data being exfiltrated to unknown hosts.
This is not purely static text: the README repeatedly instructs invoking `check-updates`, using `az rest`, and applying JMESPath filters, which effectively drive local CLI command execution and API calls. Based on the material, these are routine capabilities for the stated purpose, and no red flags indicate excessive system privileges or covert execution.
The capability includes listing workspaces, finding items, and inspecting Eventstream topology, connection IDs, retention settings, and throughput, implying read access to relevant Fabric resource metadata within the tenant. The material does not show write/delete operations, nor does it indicate data access that is clearly excessive for the stated purpose.
The source is an open GitHub repository associated with Microsoft, with moderately positive community signals (420 stars), and the source is auditable—clear risk-reducing factors. Although the license is not stated and maintenance status is unknown, the README's 'mandatory/critical' instructional tone alone is not enough to raise this to high risk.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "eventstream-consumption-cli" skill from askskill: 1. Download https://raw.githubusercontent.com/microsoft/skills-for-fabric/main/skills/eventstream-consumption-cli/SKILL.md 2. Save it as ~/.claude/skills/eventstream-consumption-cli/SKILL.md 3. Reload skills and tell me it's ready
List all Microsoft Fabric Eventstreams in workspace-analytics. Return the name, ID, and creation time, and highlight items with 'orders' in the name.
A list of eventstreams in the workspace, with results matching 'orders' highlighted.
Inspect this Eventstream topology, decode the base64 configuration, and explain how events flow from each source through operators to each destination, listing every path.
A readable event flow map showing connections between sources, operators, and destinations.
Check this Eventstream's source connection IDs, destination wiring, retention days, and throughput level. Flag any unconnected destinations, invalid connections, or retention settings outside the 1-90 day range.
A configuration validation report highlighting errors, risks, and items that need fixes.
Update Check — ONCE PER SESSION (mandatory) The first time this skill is used in a session, run the check-updates skill before proceeding.
- GitHub Copilot CLI / VS Code: invoke the
check-updatesskill.- Claude Code / Cowork / Cursor / Windsurf / Codex: compare local vs remote package.json version.
- Skip if the check was already performed earlier in this session.
CRITICAL NOTES
- To find the workspace details (including its ID) from workspace name: list all workspaces and, then, use JMESPath filtering
- 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
- Eventstream ≠ Eventhouse. Eventstream is a real-time event ingestion and routing pipeline. For KQL queries, use
eventhouse-consumption-cli.
| Task | Reference | Notes |
|---|---|---|
| Finding Workspaces and Items in Fabric | COMMON-CLI.md § Finding Workspaces and Items in Fabric | Mandatory — READ link first [needed for finding workspace id by its name or item id by its name, item type, and workspace id] |
| Fabric Topology & Key Concepts | COMMON-CORE.md § Fabric Topology & Key Concepts | |
| Environment URLs | COMMON-CORE.md § Environment URLs | |
| Authentication & Token Acquisition | COMMON-CORE.md § Authentication & Token Acquisition | Wrong audience = 401; read before any auth issue |
| Core Control-Plane REST APIs | COMMON-CORE.md § Core Control-Plane REST APIs | Includes pagination, LRO polling, and rate-limiting patterns |
| Gotchas, Best Practices & Troubleshooting | COMMON-CORE.md § Gotchas, Best Practices & Troubleshooting | |
| Tool Selection Rationale | COMMON-CLI.md § Tool Selection Rationale | |
| Authentication Recipes | COMMON-CLI.md § Authentication Recipes | az login flows and token acquisition |
Fabric Control-Plane API via az rest | COMMON-CLI.md § Fabric Control-Plane API via az rest | Always pass --resource; includes pagination and LRO helpers |
| Gotchas & Troubleshooting (CLI-Specific) | COMMON-CLI.md § Gotchas & Troubleshooting (CLI-Specific) | az rest audience, shell escaping, token expiry |
| Quick Reference | COMMON-CLI.md § Quick Reference | az rest template + token audience/tool matrix |
| Listing and Discovering Eventstreams | EVENTSTREAM-CONSUMPTION-CORE.md § Listing and Discovering Eventstreams | List, Get, Search across workspaces |
| Inspecting Eventstream Topology | EVENTSTREAM-CONSUMPTION-CORE.md § Inspecting Eventstream Topology | Decode base64 definition → trace graph flow |
| Monitoring Eventstream Health | EVENTSTREAM-CONSUMPTION-CORE.md § Monitoring Eventstream Health | Retention and throughput checks |
| Source and Destination Status | EVENTSTREAM-CONSUMPTION-CORE.md § Source and Destination Status | Validation checklist for sources and destinations |
…
Build end-to-end Bronze, Silver, and Gold lakehouse pipelines in Microsoft Fabric.
Create, update, and publish Microsoft Fabric Eventstream topologies via REST APIs.
Migrate HDInsight Spark, Hive, and Oozie workloads to Microsoft Fabric.
Search Microsoft Fabric items across workspaces and return locations and IDs.
Create, edit, deploy, and optimize Power BI semantic models and DAX.
Scan, assess, and upgrade Power BI Gen1 dataflows into Gen2.1 copies.
Query Fabric Eventhouse data, analyze time series, and monitor ingestion health.
Run read-only T-SQL queries on Fabric warehouse and lakehouse data.
Monitor, inspect, and query Fabric Dataflows Gen2 through a read-only CLI.
Inspect Fabric alerts, notifications, and automated actions via read-only API calls.
Run DAX queries and inspect Fabric Power BI semantic model metadata.
Create Fabric alerts, notifications, and event-driven automated actions.