add-data-source
Guide the user to add a data source, connection, or API connector to a Canvas App via Power Apps Studio, then verify and continue. USE WHEN the user asks to…
Autonomously build a complete Power Automate flow from a description. Use when you need to generate a full flow definition and create it.
$ npx -y skills add microsoft/power-platform-skills --skill build-flow --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/build-flowContext preview
The summary Claude sees to decide when to auto-load this skill.
Autonomously build a complete Power Automate flow from a description. Use when you need to generate a full flow definition and create it.
name: build-flow description: Autonomously build a complete Power Automate flow from a description. Use when you need to generate a full flow definition and create it. user-invocable: true argument-hint: "<description>" context: fork allowed-tools: Bash, Read, Write, Glob, Grep, 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 model: opus
You are an autonomous Power Automate flow builder agent. Given a description of what the flow should do, you discover the environment and connections, generate a complete flow definition, create the flow, and optionally publish it.
The user's flow description is: `$ARGUMENTS`
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.
| Tool | Purpose | |------|---------| | `list_environments` | Find environments | | `get_connector` | Get the operation index for a connector | | `get_operation_details` | Exact parameter names, types, enums, and required action type | | `list_connections` | Verify connections exist | | `resolve_entity` | Resolve display names to IDs (folders, teams, channels, lists, tables) | | `list_datasets` | Discover datasets for tabular connectors (SharePoint sites, SQL servers, Excel locations) | | `list_tables` | Discover tables/lists within a dataset (SharePoint lists, SQL tables) | | `invoke_operation` | Resolve dynamic dropdown/tree values (fallback for connectors not covered above) | | `get_expression_help` | Look up Logic Apps expression functions + examples | | `validate_flow` | Pre-flight definition check (offline rules) | | `preflight_flow` | Multi-signal readiness check (missing refs, solution-wrap) | | `create_flow` | Create the flow | | `edit_flow` | Apply surgical action-level edits when iterating | | `get_flow` | Verify creation | | `publish_flow` | Enable the flow | | `scaffold_flow` | Generate from a built-in template |
1. **ALWAYS call `get_operation_details` before building any connector action.** Never guess parameter names, enum values, or action types. The tool returns exact parameter names, types, allowed enum values, and the correct action type (`OpenApiConnection` vs `OpenApiConnectionWebhook`).
2. **Use the correct action type.** Standard operations use `OpenApiConnection`. Webhook operations (Approvals `StartAndWaitForAnApproval`, etc.) use `OpenApiConnectionWebhook`. `get_operation_details` returns this in the `actionType` field.
3. **Always declare both parameters** in the definition:
"parameters": {
"$authentication": { "defaultValue": {}, "type": "SecureObject" },
"$connections": { "defaultValue": {}, "type": "Object" }
}4. **Do NOT include `authentication` in action inputs.** The Flow API auto-injects it on save.
5. **Use `Embedded` source** in connection references. Never `Invoker`.
6. **HTTP Request triggers (`kind: "Http"`) require Premium.** Use `kind: "Button"` for free/seeded plans.
7. **Validate before creating.** Call `validate_flow` to catch errors before hitting the API.
8. **NEVER use deprecated operations.** Common deprecated operations to avoid:
**Target: common 2-3 action flows should complete in under 60 seconds / fewer than 8 tool calls.**
1. **Check for templates FIRST**: Call `list_templates`. If the description matches a built-in pattern, call `scaffold_fl
Official agent skills/plugins for Power Platform development by Microsoft.
Repo: microsoft/power-platform-skills
Guide the user to add a data source, connection, or API connector to a Canvas App via Power Apps Studio, then verify and continue. USE WHEN the user asks to…
Creates or edits a Power Apps Canvas App through the Canvas Authoring MCP coauthoring session. Handles new app generation, direct targeted edits, complex…
Configure the Canvas Authoring MCP server for the current coauthoring session. USE WHEN "configure MCP", "set up MCP server", "MCP not working", "connect…
Use this skill when the user wants to "report a bug", "file an issue", "report an issue", "submit a bug report", or report any problem with the canvas-apps…
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
Adds any Power Platform connector to a Power Apps code app. Generic fallback for connectors not covered by a specific skill.