
Flowstudio power automate monitoring
Tenant-wide Power Automate health monitoring via FlowStudio's cached store data
- Scripts
- None
- Platforms
- Claude Code, Codex, Cursor
- GitHub stars
- 41.3K
- Last commit
- today
- License
- MIT
- Listing updated
- 1 day ago
Similar skills
About Flowstudio power automate monitoring
Flowstudio power automate monitoring is an open-source agent skill for e-commerce. It is available on Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose.
This skill guides an agent through tenant-level monitoring of Power Automate using the FlowStudio MCP cached store. It covers failure rates and run-health trends across flows, inventories of environments, connections, makers and canvas apps, and checks for inactive owners and deleted makers who still own flows. Reads come from a daily-scanned cache, so queries return quickly without hitting Power Automate API rate limits.
The skill explains how monitoring is switched on per flow with a monitor flag, how to read scan freshness, and when empty results point to a flow that is not monitored or has not been scanned recently. It also describes which store tools to call for summaries, per-run failure history with remediation hints, and governance metadata updates such as critical-flow designation and failure alerts.
It requires a FlowStudio for Teams or MCP Pro+ subscription. For single-flow diagnosis, live run control, or environment-level work, the skill points the agent to the related FlowStudio MCP, debug and monitor-flow skills.
When your agent uses it
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+.
From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.
What it can access
From a static check of its 1 file (13 KB) on GitHub on 19 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.
Check another skill before you install it.
Install
Copy the skill folder to ~/.claude/skills/flowstudio-power-automate-monitoring to use it in all your projects:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/flowstudio-power-automate-monitoring &&
cp -R "$tmp/skills/flowstudio-power-automate-monitoring" ~/.claude/skills/flowstudio-power-automate-monitoring &&
rm -rf "$tmp"For one project only, put the folder in .claude/skills/flowstudio-power-automate-monitoring inside it instead.
Copy the skill folder to ~/.agents/skills/flowstudio-power-automate-monitoring to use it in every repository:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/flowstudio-power-automate-monitoring &&
cp -R "$tmp/skills/flowstudio-power-automate-monitoring" ~/.agents/skills/flowstudio-power-automate-monitoring &&
rm -rf "$tmp"For one repository only, put the folder in .agents/skills/flowstudio-power-automate-monitoring inside it instead.
Copy the skill folder to ~/.cursor/skills/flowstudio-power-automate-monitoring to use it in every project:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/flowstudio-power-automate-monitoring &&
cp -R "$tmp/skills/flowstudio-power-automate-monitoring" ~/.cursor/skills/flowstudio-power-automate-monitoring &&
rm -rf "$tmp"For one project only, put the folder in .cursor/skills/flowstudio-power-automate-monitoring inside it instead.
Run in a terminal (add --scope workspace to install it for the current workspace only):
gemini skills install https://github.com/github/awesome-copilot.git --path skills/flowstudio-power-automate-monitoringOr copy the folder to ~/.gemini/skills/flowstudio-power-automate-monitoring yourself.
For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/flowstudio-power-automate-monitoring:
tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/github/awesome-copilot.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/flowstudio-power-automate-monitoring &&
cp -R "$tmp/skills/flowstudio-power-automate-monitoring" ~/.copilot/skills/flowstudio-power-automate-monitoring &&
rm -rf "$tmp"For one project only, put the folder in .github/skills/flowstudio-power-automate-monitoring inside it instead.
Get the folder:
git clone --depth 1 https://github.com/github/awesome-copilot.gitThen copy awesome-copilot/skills/flowstudio-power-automate-monitoring into your agent's skills folder as flowstudio-power-automate-monitoring. Agents that support SKILL.md read one folder per skill.
What it does
- Failure rate triage
- Finds flows with high recent failure rates and ranks them for follow-up.
- Run history summaries
- Provides success and failure counts, rates and duration statistics over a chosen time window.
- Monitoring enablement
- Turns on per-flow monitoring and failure notification rules through governance metadata updates.
- Maker and owner audit
- Identifies deleted makers who still own flows and reviews maker account details.
- Tenant inventory
- Counts environments, flows, canvas apps and connections across the tenant.
- Data freshness checks
- Uses scan timestamps to confirm cached monitoring data is current.
Good for
- Show which flows in the tenant have the highest failure rates this week
- Review the failed runs of a monitored flow and their remediation hints
- Find deleted makers who still own active flows
- Turn on failure alerts for business-critical flows
- Count canvas apps and connections across all environments
Flowstudio power automate monitoring FAQ
What subscription does this skill need?
It requires FlowStudio for Teams or MCP Pro+. Without it, store tool calls return a 403 or 404 error, and the skill tells the agent to stop and link to the pricing page.
Why does a flow return no run history?
Run data only exists for flows with monitor set to true, and the flow must have been scanned recently. The skill recommends checking both fields with get_store_flow.
Does this skill change flows?
It can update governance metadata such as the monitor flag, notification rules and critical designation. Start and stop actions are delegated to a separate monitor-flow bundle tool.
When should I use a different skill?
For one environment, one flow, run control or root-cause debugging, the skill directs you to the flowstudio-power-automate-mcp, flowstudio-power-automate-debug or monitor-flow tools.
How do I install Flowstudio power automate monitoring in Claude Code?
Copy the skill folder from GitHub to ~/.claude/skills/flowstudio-power-automate-monitoring to use it in all your projects, or to .claude/skills/flowstudio-power-automate-monitoring in one project.
Does Flowstudio power automate monitoring run scripts?
No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.
Which AI agents can use Flowstudio power automate monitoring?
Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.
What are the best alternatives to Flowstudio power automate monitoring?
The closest alternatives to Flowstudio power automate monitoring are Flowstudio power automate debug, Flowstudio power automate governance, Ask matt, Flowstudio power automate build and Assess observability health.
Where this comes from
- Description: from the skill's own SKILL.md.
More from github/awesome-copilot

A DevOps checklist for deploys, Docker, Kubernetes, CI/CD, rollback and mobile releases
- Open source
- 41.3K GitHub stars
- Cloud and infrastructure

Guides Qdrant scaling when data outgrows a node: tenants, time windows or sharding
- Open source
- 41.3K GitHub stars
- Knowledge and memory

Explains Qdrant's per-shard query subsampling for large limits across many auto-shards
- Open source
- 41.3K GitHub stars
- Knowledge and memory

Creates, exports and appends to Arize evaluation datasets using the ax command line
- Open source
- 41.3K GitHub stars
- AI models and LLM tooling

Creates Arize LLM-as-judge evaluators and runs them on traces or experiment results
- Open source
- 41.3K GitHub stars
- AI models and LLM tooling

Runs a model over an Arize dataset, saves the results as an experiment and compares runs
- Open source
- 41.3K GitHub stars
- AI models and LLM tooling

