Agent skill · marketing growth · github
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 involves writing governance metadata to flows. Requires a FlowStudio for Teams or MCP Pro+ subscription — see https://mcp.flowstudio.app
Why this skill is useful
Provides specific governance metadata management commands for Power Automate flows that the AI wouldn't reliably generate on its own.
What it needs
Requires flowstudio account access. About 8k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
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 (updatestoreflow) 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/list — call toolsearch with query: "skill:governance" for the canonical bundle, or query: "select:updatestoreflow" for a single tool. This skill covers workflow patterns and field semantics — things toolsearch cannot tell you. If this document disagrees with a real API response, the API wins. --- Critical: How to Extract Flow IDs liststoreflows returns id in format <environmentId>.<flowId>. You must split on the first . to get environmentName and flowName for all other tools: Also: skip entries that have no displayName or have state=Deleted — these are sparse records or flows that no longer exist in Power Automate. If a deleted flow has monitor=true, suggest disabling monitoring (updatestoreflow with monitor=false) to free up a monitoring slot (standard plan includes 20). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/flowstudio-power-automate-governance