How to use the Build Power Automate Flows agent skill

What is an agent skill, and what does this one do?

An agent skill is a folder containing a SKILL.md file and reference files that an AI agent can load when a task matches the skill's description. This skill, flowstudio-power-automate-build, gives the agent a detailed playbook for building Power Automate cloud flows through tools on the FlowStudio MCP server.

Following the playbook, the agent checks whether a flow already exists, finds the connections the flow needs (such as SharePoint or Outlook), writes the flow's JSON definition, deploys it, and tests it. Reference files add copy-paste patterns for triggers, actions, data handling and the flow schema.

• Checks for an existing flow before creating a new one to avoid duplicates
• Lists active connections and builds the connectionReferences block
• Writes the flow definition JSON, using the included action patterns
• Deploys the flow and verifies it, then tests it

Before you install: what you need

The skill cannot run without a FlowStudio MCP server. FlowStudio is a paid third-party service, not a Microsoft product. You need a subscription and a valid JWT, which you can get at https://mcp.flowstudio.app.

You also need a Microsoft Power Automate environment, and an active authenticated connection for every connector a flow uses (for example SharePoint, Outlook or Teams). Connections are created through browser OAuth consent. The included helper script uses Python 3 and only the standard library.

• FlowStudio MCP server subscription and valid JWT
• A Microsoft Power Automate environment
• Connected connections for each connector used, created via browser OAuth consent
• Python 3

Install the skill

Download the ZIP for this skill from this page and unzip it. You can install it in one of two ways.

For Claude Code, unzip it into your user skills folder ~/.claude/skills/, or into a project's .claude/skills/ folder for a single project.

In the Claude apps, upload the ZIP under Settings → Capabilities → Skills.

• Personal install: ~/.claude/skills/
• Project install: .claude/skills/ inside your project
• Claude apps: Settings → Capabilities → Skills, then upload the ZIP

Trigger the skill with a natural request

The skill loads when your request matches its description. Ask for a flow to be created, built, scaffolded or changed in plain language. The description names tasks such as creating a flow, deploying a flow definition, adding actions to a flow, patching a flow definition, and wiring up connections.

Name the environment and the connectors involved. The agent will still check for an existing flow and look up connections itself, so you do not need to supply connection GUIDs.

• "Create a flow that posts new SharePoint list items to a Teams channel."
• "Add an approval step to my existing expense flow."
• "Scaffold a Recurrence flow that calls an HTTP endpoint and stores the result in a variable."

Understand the build workflow

The skill sets a fixed order: load the current build tools, check for an existing flow, resolve connection references, build the definition, deploy, verify, and test. The skill tells the agent to call tool_search or list_skills first so it uses the server's current tool names and parameters.

If a required connection is missing, the agent should stop and ask you to create it in the selected environment, rather than guessing connection names.

• Load current build tools
• Check for an existing flow
• Resolve connection references
• Build the definition
• Deploy
• Verify
• Test

Safety notes: scripts, network and review

This skill runs scripts and uses the network. The included Python helper sends requests to https://mcp.flowstudio.app/mcp with your JWT. Review the helper and the generated definition before you let it deploy.

The skill is not meant for production tenants where unreviewed deployments could break business processes or expose data. A human should review every definition before deployment. Keep your JWT out of shared files, since the helper places it in a variable.

• The helper makes network calls to the FlowStudio MCP server
• A human should review definitions before deployment
• Avoid production tenants for unreviewed changes
• Do not share your JWT

Tips for better results

The skill's reference files are most useful when you point the agent at them by pattern. Good requests name the trigger, the actions and the connectors. If you edit many similar flows, reuse the same connection references and build patterns each time.

Use the flow name to let the agent find an existing flow. For very large environments, the server may return a continuation URL, which the skill says to pass back to get the next batch.

• Name the trigger type, such as Recurrence or an HTTP request
• List the connectors and the environment you want to use
• Use the existing flow's name so the agent edits instead of duplicating
• Ask the agent to show the definition before deploying