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+.
Profile →npx skills add github/awesome-copilot --skill flowstudio-power-automate-monitoring --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 `tool_search` rather than `tools/list` — > call with `query: "select:list_store_flows,get_store_flow_summary"` 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
- How Monitoring Works
- Tools
- Store vs Live
- Response Shapes
- liststoreflows
- getstoreflow
- getstoreflowsummary
- getstoreflowruns
- Trigger URL
- Starting / stopping a flow
- updatestoreflow
- liststoreenvironments
- liststoreconnections
- liststoremakers
What does the flowstudio-power-automate-monitoring skill do?
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+.
How do I install it?
Run `npx skills add github/awesome-copilot --skill flowstudio-power-automate-monitoring --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.