Guide · Agent skill
How to use the Power Automate Governance via FlowStudio agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
This guide explains how to install and use the flowstudio-power-automate-governance agent skill, a set of instructions that lets an AI agent help you govern Power Automate flows across many environments. It is written for admins and makers who have never used agent skills before. By the end you will know what the skill does, how to add it to your agent, how to ask for governance work in plain language, and what it needs to run.
Power Automate Governance via FlowStudiogithub/awesome-copilot · MIT Download the skill Quick start
- 1Confirm your access. Make sure you have a FlowStudio for Teams or MCP Pro+ subscription and that the FlowStudio MCP server is connected to your agent.
- 2Download and unzip the skill. Download the ZIP from this page and unzip it so that SKILL.md sits in a skill folder.
- 3Place the skill folder. Put the folder in ~/.claude/skills/ for personal use or .claude/skills/ inside your project, or upload it under Settings → Capabilities → Skills in the Claude apps.
- 4Ask for a governance task. Describe the outcome in plain language, such as running a governance review or finding flows owned by deleted accounts.
- 5Review proposed writes. Check the fields and flows the agent plans to change before you approve any update_store_flow or stop action.
- 6Confirm the scope of changes. Remember that writes change only FlowStudio metadata; make real ownership or deletion changes in the admin center or PowerShell.
What is this skill and what does it make the agent do?
The skill lets an agent help an admin or maker govern Power Automate flows at scale. Its listed tasks are marking business impact and ownership contacts, finding flows owned by deleted accounts, auditing connectors, checking compliance metadata, setting failure notification rules, and scoring flows for archiving.
The skill works by reading and writing metadata in the FlowStudio cache. It does not change the flows themselves in Power Automate. Fields such as ownerTeam, supportEmail and businessImpact exist only in FlowStudio and are not visible in the Power Automate portal.
- Classify flows by business impact and mark them critical
- Detect flows owned by deleted or disabled accounts
- Audit which connectors monitored flows use
- Check flows against your compliance fields
- Compute archive scores (0-7) to find cleanup candidates
- Manage failure and missing-run notification rules
Before you install: what the skill requires
The skill needs a paid FlowStudio for Teams or MCP Pro+ subscription. Its store tools return 403 or 404 errors without one. The skill also needs the FlowStudio MCP server with the store_* tools, including list_store_flows, get_store_flow, update_store_flow and list_store_makers.
If you do not have that access, the skill tells the agent to stop calling store tools and link you to https://mcp.flowstudio.app/pricing.
Install the skill by downloading the ZIP
Download the ZIP for this skill from this page and unzip it. The skill is a single file named SKILL.md. Place the unzipped skill folder in one of these locations:
Personal skills folder: ~/.claude/skills/
Project skills folder: .claude/skills/ inside your project. Use this if you want the skill available only to one project.
You can also upload the skill in the Claude apps under Settings → Capabilities → Skills.
- Personal: ~/.claude/skills/
- Project: .claude/skills/ in your project folder
- Claude apps: Settings → Capabilities → Skills
Trigger the skill with natural requests
You do not need to name the skill. The skill's description lists the kinds of requests that load it, so ask for the outcome you want. Requests that match the skill include tagging or classifying flows, setting business impact, detecting orphans, auditing connectors, checking compliance, computing archive scores, managing notification rules, running a governance review, generating a compliance report, and offboarding a maker.
Be specific about scope. Say which environment, which team, or which set of flows you mean, and say which fields your policy requires, because the skill asks for your compliance policy before flagging flows.
- Run a governance review and list flows missing businessImpact or ownerTeam
- Find flows owned by makers whose accounts were deleted and suggest a governance contact for each
- Audit connectors across monitored flows and flag premium and HTTP connectors
- Score flows for archiving and tag the borderline ones #archive-review
- Offboard a maker: find their flows and set a new support contact
Understand what the skill can and cannot change
The write tool, update_store_flow, changes only the FlowStudio cache. Setting ownerTeam does not change the real Power Automate owner. Setting rule_notify_email does not change Microsoft's built-in failure alerts. Transferring real ownership is done in the admin center or with PowerShell.
Archiving through the skill means stopping the flow and tagging it with #archived. Deleting a flow requires the portal or admin PowerShell.
The skill is not for health checks or failure-rate dashboards. The skill itself directs those requests to the separate flowstudio-power-automate-monitoring skill.
- Governance metadata writes: FlowStudio cache only
- Real owner changes: admin center or PowerShell
- Archive: stop and tag, not delete
- Health checks: use flowstudio-power-automate-monitoring
Safety notes: scripts and network access
This skill does not run scripts. It does use the network, because it calls the FlowStudio MCP store tools to read and write data. Review the tool calls the agent proposes, especially update_store_flow and set_live_flow_state, before approving them on production flows.
The skill also notes that store coverage is only as fresh as the latest scan, so results may lag behind recent changes in Power Automate.
- Runs scripts: no
- Uses network: yes (FlowStudio MCP store tools)
- Check proposed writes before approving them
What people use it for
- Centre of Excellence teams tagging flows with business impact and ownership contacts without Dataverse or the CoE Starter Kit
- IT staff offboarding a maker by finding their flows and reassigning the governance contact
- Admins running a compliance review that lists flows missing required metadata
- Reviewing connector usage across monitored flows before DLP or premium licence planning
- Scoring stale flows for archiving and tagging borderline ones for human review
Frequently asked questions
How do I install the Power Automate governance FlowStudio skill?
Download the ZIP from this page and unzip it. Put the skill folder in ~/.claude/skills/ for personal use or in .claude/skills/ inside a project, or upload it in the Claude apps under Settings → Capabilities → Skills.
Is this skill free?
The skill's listed licence is MIT. It requires a paid FlowStudio for Teams or MCP Pro+ subscription, because its store tools return 403 or 404 errors without one. Check https://mcp.flowstudio.app/pricing for plan details.
What do I need to use the skill?
You need a FlowStudio for Teams or MCP Pro+ subscription and the FlowStudio MCP server with store_* tools such as list_store_flows, get_store_flow, update_store_flow and list_store_makers.
Does the skill change flows in Power Automate?
No. It reads and writes metadata in the FlowStudio cache only. Fields like ownerTeam and businessImpact are not visible in Power Automate, and changing them does not change the real flow owner.
Can it monitor flow failures or build a health dashboard?
Not as its main job. The skill says health checks and failure-rate dashboards belong to the separate flowstudio-power-automate-monitoring skill, though it can set failure notification rules.
Does this skill work without Dataverse or the CoE Starter Kit?
Yes. The skill's description says it works without Dataverse or the CoE Starter Kit, using the FlowStudio MCP cached store instead.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits Power Platform admins, Centre of Excellence teams and IT staff who run governance reviews across many flows and have a FlowStudio Pro+ subscription. It is a poor fit if you need real ownership changes in Power Automate, built-in failure alerts, or health dashboards, or if you do not have a paid FlowStudio plan.
Download the skill