Agent skill · data analytics · github
flowstudio-power-automate-monitoring
Pro+ subscription required. Tenant-wide Power Automate monitoring using the FlowStudio MCP cached store: failure rates, run-health trends, maker/app inventory, inactive owners, and compliance/health reports. Use only for aggregated tenant views. For one environment, one flow, run control, or root-cause debugging, use flowstudio-power-automate-mcp, flowstudio-power-automate-debug, or the server monitor-flow bundle. Requires FlowStudio for Teams or MCP Pro+.
Why this skill is useful
Provides specific monitoring commands and governance metadata for Power Automate that the AI wouldn't reliably generate on its own.
What it needs
Requires flowstudio account access. About 6k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Power Automate Monitoring with FlowStudio MCP Monitor flow health, track failure rates, and inventory tenant assets through the FlowStudio MCP cached store — fast reads, no PA API rate limits, and enriched with governance metadata and remediation hints. ⚠️ Pro+ subscription required. This skill calls store tools that only work for FlowStudio for Teams or MCP Pro+ subscribers. If the user does not have Pro+ access: the first store tool call will return a 403/404 error. When that happens: 1. STOP calling store tools 2. Tell the user this feature requires a Pro+ subscription 3. Link them to https://mcp.flowstudio.app/pricing 4. If their question can be answered with live tools (e.g. "list flows in one environment"), offer to use the flowstudio-power-automate-mcp skill instead Discovery: load tool schemas via toolsearch rather than tools/list — call with query: "select:liststoreflows,getstoreflowsummary" for the common monitoring tools, or load the full set with query: "skill:governance" (the server's governance bundle covers most monitoring reads too — this skill and flowstudio-power-automate-governance share the underlying tool family). This skill covers response shapes, behavioral notes, and workflow patterns — things toolsearch cannot tell you. If this document disagrees with a real API response, the API wins. --- How Monitoring Works FlowStudio scans the Power Automate API daily for each subscriber and caches the results. There are two levels: All flows get metadata scanned: definition, connections, owners, trigger type, and aggregate run statistics (runPeriodTotal, runPeriodFailRate, etc.). Environments, apps, connections, and makers are also scanned. Monitored flows (monitor: true) additionally get per-run detail: individual run records with status, duration, failed action names, and remediation hints. This is what populates getstoreflowruns and getstoreflowsummary. Data freshness: Check the scanned field on getstoreflow to see when a flow was last scanned. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/flowstudio-power-automate-monitoring