- 01
/plugin marketplace add microsoft/power-platform-skills - 02
/plugin install power-automate@power-platform-skills
A guided wizard for making a new Power Automate flow. It asks what the flow should do, suggests a template when one matches, checks your connections and the real values each step needs, shows you the design to confirm, then creates the flow switched off and offers to turn it on.
WHEN TO USE
USE FOR
- Build a first flow with help at each step.
- Start from a template for approvals, digests or webhooks.
- Check the flow for errors before it's created.
NOT FOR
- Hands-off builds from a single description: /build-flow does that.
This is a saved copy of the skill's SKILL.md instructions. It may differ from the upstream file or the version you install.
Guided Flow Creation Wizard
Walk the user through creating a Power Automate flow step by step.
Tools
This skill uses the FlowAgent MCP tools. Clients surface them with a
client-specific prefix — mcp__flowagent__<tool> (Claude Code) or
flowagent-<tool> (Copilot CLI) — so they're referred to by bare name below
(e.g. create_flow). Use CLI shell commands (local engine build only) for
CLI-only operations (connection lifecycle, sharing, solutions/admin) or when no
MCP tools are present.
Steps
-
Gather requirements: Ask what the flow should do. Identify triggers, actions, connectors.
-
Select environment: Call
list_environments(usequeryto filter). Let user pick or auto-select. -
Check for templates: Call
list_templates. If a template matches (approval, digest, webhook, etc.), offer to usescaffold_flowas a starting point. -
Discover connectors: For each connector, call
get_connectorwithqueryto find the operation, thenget_operation_detailsfor exact parameters. Never guess parameter names or types. -
Verify connections: Call
list_connectionsfiltered by each connector. Confirm Connected status. -
Resolve dynamic values: For params with
dynamicValues/dynamicTreeannotations, callinvoke_operationto get actual values (Teams channels, SharePoint sites, etc.). -
Review with user: Present the flow design. Use AskUserQuestion to confirm trigger, actions, and connections before creating.
-
Generate definition: Build following all rules:
- Always declare
$authentication(SecureObject) and$connections(Object) parameters - Use correct action type:
OpenApiConnectionorOpenApiConnectionWebhook(fromget_operation_details) - Do NOT include
authenticationin action inputs - Use
Embeddedsource in connection references - HTTP Request triggers require Premium; prefer
Buttonkind
- Always declare
-
Validate: Call
validate_flow(and optionallypreflight_flow) to pre-check. For expressions, look up syntax withget_expression_help. -
Create: Call
create_flowin Stopped state. Report ID and name. -
Optionally publish: Ask if user wants to enable. If yes, call
publish_flow. For later one-off tweaks, useedit_flow(surgical) rather than resending the whole definition.
Account or credentials required
2 FOR YOUAll items below are required.
- 01Install with the power-automate plugin, for its FlowAgent server
Install it with Microsoft's power-automate plugin. Its steps run through the plugin's FlowAgent MCP server, which comes only with the plugin. The plugin sends usage data to Microsoft by default; /power-automate:telemetry off stops sending it.
- 02Node.js 18+ and the Azure CLI signed in
Node.js 18 or newer and the Azure CLI signed in (az login). The first time, run the plugin's setup skill.
This skill ships inside the Power Platform Skills plugin. Listed package contents include 25 agents, hooks and an MCP server. Installed components and skill versions may vary by AI tool.
Install as a Claude Code plugin
Typed inside the agent's own prompt, not in a terminal.
The repository is licensed under MIT — use, modification, and redistribution are allowed under that license’s terms.
View the repository’s license file on GitHub →