Agent skill · Security

flowstudio-power-automate-governance

Govern Power Automate flows and Power Apps at scale using the FlowStudio MCP cached store. Classify flows by business impact, detect orphaned resources, audit connector usage, enforce compliance standards, manage notification rules, and compute governance scores — all without Dataverse or the CoE Starter Kit. Load this skill when asked to: tag or classify flows, set business impact, assign ownership, detect orphans, audit connectors, check compliance, compute archive scores, manage notification rules, run a governance review, generate a compliance report, offboard a maker, or any task that inv

GitHub68,948★ · +463/wk · 2 repos on radarProfile →
copilotMIT
Install
npx skills add github/awesome-copilot --skill flowstudio-power-automate-governance --agent copilot

Same command for any agent — swap --agent for claude-code, codex, cursor.

Facts
Files in the skill folder: 1
SKILL.md size: 14 KB
Bundled scripts: none
Path: skills/flowstudio-power-automate-governance/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 37,432 · +281 this week
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Power Automate Governance with FlowStudio MCP Classify, tag, and govern Power Automate flows at scale through the FlowStudio MCP **cached store** — without Dataverse, without the CoE Starter Kit, and without the Power Automate portal. This skill uses the same `store_*` tool family as `flowstudio-power-automate-monitoring`, but with a different *intent*: governance writes metadata (`update_store_flow`) and reads for *audit and classification* outcomes. Monitoring reads the same tools for *operational health* outcomes. Don't try to memorize which skill "owns" which tool — pick by what the user is doing. For health checks and failure-rate dashboards, load `flowstudio-power-automate-monitoring` instead. > **⚠️ 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 governance features require a Pro+ subscription > 3. Link them to https://mcp.flowstudio.app/pricing > > **Discovery:** load tool schemas via the meta-tools rather than `tools/

What's inside
Steps it walks through
  1. Critical: How to Extract Flow IDs
  2. The Write Tool: updatestoreflow
  3. Settable Fields
  4. Governance Workflows
  5. 1. Compliance Detail Review
  6. 2. Orphaned Resource Detection
  7. 3. Archive Score Calculation
  8. 4. Connector Audit
  9. 5. Notification Rule Management
  10. 6. Classification and Tagging
  11. 7. Maker Offboarding
  12. 8. Security Review
  13. 9. Environment Governance
  14. 10. Governance Dashboard
More from awesome-copilot
All skills →
About this skill
What does the flowstudio-power-automate-governance skill do?

Govern Power Automate flows and Power Apps at scale using the FlowStudio MCP cached store. Classify flows by business impact, detect orphaned resources, audit connector usage, enforce compliance standards, manage notification rules, and compute governance scores — all without Dataverse or the CoE Starter Kit. Load this skill when asked to: tag or classify flows, set business impact, assign ownership, detect orphans, audit connectors, check compliance, compute archive scores, manage notification rules, run a governance review, generate a compliance report, offboard a maker, or any task that inv

How do I install it?

Run `npx skills add github/awesome-copilot --skill flowstudio-power-automate-governance --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.

Keep going