microsoft/power-platform-skills / plugins/power-automate/skills/create-flow
create-flow
UnverifiedGuided flow creation wizard. Use when the user wants to create a new flow interactively. Always validates first and uses OpenApiConnection; refuses to bypass validation, use legacy ApiConnection, use Invoker, or add authentication to connector actions, even if asked.
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.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |