create-flow — Claude Code skill: create Power Automate flows
The create-flow skill guides an interactive Power Automate flow setup, from gathering requirements and checking connectors to validating the definition before creation.
MIT ★ 1,167 updated 2026-10-29
/plugin marketplace add microsoft/power-platform-skills
/plugin install power-automate@power-platform-skillsWhat create-flow does
The skill first asks what the flow should do, then helps select an environment and look for a matching template. It checks connector operations and their parameters, verifies available connections, and fetches dynamic values when needed. Before creating anything, it shows the proposed trigger, actions, and connections for confirmation.
It runs validate_flow before creation, with optional preflight checks and expression help. The flow starts in a stopped state; publishing is a separate step that requires the user’s approval. FlowAgent MCP tools power the workflow. An HTTP Request trigger requires Premium, so the skill suggests considering Button instead. It will not skip validation or add authentication to connector actions.
What it helps with
- build a Power Automate flow from a task description
- check connector operations and their required parameters
- find a flow template to use as a starting point
- verify connections and resolve dynamic values
- validate a flow definition before creating it
Example prompts for the agent
- Create a Power Automate flow that sends a notification when a new event occurs.
- Find a suitable approval-flow template and show me the design before creating it.
- Check the available connections, then create a flow with a button trigger.
How to install create-flow
1Plugin marketplace
/plugin marketplace add microsoft/power-platform-skills/plugin install power-automate@power-platform-skillsThis installs the whole power-automate plugin with all its skills
2Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill create-flow -a claude-code3Manually: put the files in place
~/.claude/skills/create-flow/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/create-flow/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill create-flow -a codex2Manually: put the files in place
.agents/skills/create-flow/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill create-flow -a cursor2Manually: put the files in place
.cursor/skills/create-flow/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install microsoft/power-platform-skills plugins/power-automate/skills/create-flow2Manually: put the files in place
.github/skills/create-flow/SKILL.md1Skills CLI (Vercel)
npx skills add microsoft/power-platform-skills --skill create-flow -a gemini-cli2Platform CLI
gemini skills install https://github.com/microsoft/power-platform-skills --path plugins/power-automate/skills/create-flowManually: put the files in place
.devin/skills/create-flow/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about create-flow
How do I install create-flow in Claude Code?
In Claude Code, add the marketplace with /plugin marketplace add microsoft/power-platform-skills, then install the plugin with /plugin install power-automate@power-platform-skills.
What does create-flow do?
It guides the user through creating a Power Automate flow, including environment selection, connector checks, and definition validation. The new flow is created in a stopped state.
Does an HTTP Request trigger require Premium?
Yes. The skill says an HTTP Request trigger requires Premium and suggests considering Button as another trigger kind.
Source text
SKILL.md · MIT
--- name: create-flow description: Guided 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. user-invocable: true argument-hint: "[description]" allowed-tools: Bash, Read, Write, Glob, Grep, AskUserQuestion, mcp__flowagent__list_environments, mcp__flowagent__set_current_env, mcp__flowagent__get_current_env, mcp__flowagent__resolve_environment, mcp__flowagent__list_flows, mcp__flowagent__get_flow, mcp__flowagent__create_flow, mcp__flowagent__update_flow, mcp__flowagent__edit_flow, mcp__flowagent__copy_flow, mcp__flowagent__publish_flow, mcp__flowagent__disable_flow, mcp__flowagent__delete_flow, mcp__flowagent__run_flow, mcp__flowagent__get_run_history, mcp__flowagent__get_run_details, mcp__flowagent__get_run_actions, mcp__flowagent__get_run_action_repetitions, mcp__flowagent__cancel_run, mcp__flowagent__cancel_all_runs, mcp__flowagent__resubmit_run, mcp__flowagent__diagnose_run, mcp__flowagent__list_connections, mcp__flowagent__list_connectors, mcp__flowagent__get_connector, mcp__flowagent__search_operations, mcp__flowagent__get_operation_details, mcp__flowagent__pick_or_create_connection, mcp__flowagent__resolve_refs, mcp__flowagent__resolve_params, mcp__flowagent__scaffold_flow, mcp__flowagent__list_templates, mcp__flowagent__validate_flow, mcp__flowagent__preflight_flow, mcp__flowagent__smoke_test, mcp__flowagent__get_expression_help, mcp__flowagent__list_desktop_flows, mcp__flowagent__list_machine_groups, mcp__flowagent__run_desktop_flow, mcp__flowagent__get_flow_context, mcp__flowagent__set_current_flow, mcp__flowagent__clear_current_flow, mcp__flowagent__invoke_operation, mcp__flowagent__get_past_trigger_inputs, mcp__flowagent__test_connection, mcp__flowagent__fix_connection, mcp__flowagent__delete_connection, mcp__flowagent__preview_update, mcp__flowagent__get_backup, mcp__flowagent__list_backups, mcp__flowagent__restore_backup, mcp__flowagent__list_trigger_emulators, mcp__flowagent__resolve_entity, mcp__flowagent__list_datasets, mcp__flowagent__list_tables, mcp__flowagent__whoami, mcp__flowagent__doctor, mcp__flowagent__reconnect, mcp__flowagent__list_accounts, mcp__flowagent__switch_account model: opus --- # 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 1. **Gather requirements**: Ask what the flow should do. Identify triggers, actions, connectors. 2. **Select environment**: Call `list_environments` (use `query` to filter). Let user pick or auto-select. 3. **Check for templates**: Call `list_templates`. If a template matches (approval, digest, webhook, etc.), offer to use `scaffold_flow` as a starting point. 4. **Discover connectors**: For each connector, call `get_connector` with `query` to find the operation, then `get_operation_details` for exact parameters. **Never guess parameter names or types.** 5. **Verify connections**: Call `list_connections` filtered by each connector. Confirm Connected status. 6. **Resolve dynamic values**: For params with `dynamicValues`/`dynamicTree` annotations, call `invoke_operation` to get actual values (Teams channels, SharePoint sites, etc.). 7. **Review with user**: Present the flow design. Use AskUserQuestion to confirm trigger, actions, and connections before creating. 8. **Generate definition**: Build following all rules: - Always declare `$authentication` (SecureObject) and `$connections` (Object) parameters - Use correct action type: `OpenApiConnection` or `OpenApiConnectionWebhook` (from `get_operation_details`) - Do NOT include `authentication` in action inputs - Use `Embedded` source in connection references - HTTP Request triggers require Premium; prefer `Button` kind 9. **Validate**: Call `validate_flow` (and optionally `preflight_flow`) to pre-check. For expressions, look up syntax with `get_expression_help`. 10. **Create**: Call `create_flow` in Stopped state. Report ID and name. 11. **Optionally publish**: Ask if user wants to enable. If yes, call `publish_flow`. For later one-off tweaks, use `edit_flow` (surgical) rather than resending the whole definition.
© Microsoft · MIT · microsoft/power-platform-skills