Official agent skill

Build Flow

by microsoft in microsoft/power-platform-skills

Autonomously build a complete Power Automate flow from a description.

OfficialMITAuto-check: notesAI & LLM Engineering

Install Build Flow

skills CLI

$ npx skills add microsoft/power-platform-skills --skill build-flow -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install microsoft/power-platform-skills build-flow --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/power-automate/skills/build-flow .claude/skills/build-flow && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "build-flow" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-automate/skills/build-flow into .claude/skills/build-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-flow", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-automate/skills/build-flow

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add microsoft/power-platform-skills --skill build-flow -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install microsoft/power-platform-skills build-flow --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/power-automate/skills/build-flow .agents/skills/build-flow && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "build-flow" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-automate/skills/build-flow into .agents/skills/build-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-flow", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add microsoft/power-platform-skills --skill build-flow -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install microsoft/power-platform-skills build-flow --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/power-automate/skills/build-flow .cursor/skills/build-flow && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "build-flow" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-automate/skills/build-flow into .cursor/skills/build-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-flow", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/microsoft/power-platform-skills.git --path plugins/power-automate/skills/build-flow

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add microsoft/power-platform-skills --skill build-flow -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install microsoft/power-platform-skills build-flow --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/power-automate/skills/build-flow .gemini/skills/build-flow && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "build-flow" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-automate/skills/build-flow into .gemini/skills/build-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-flow", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install microsoft/power-platform-skills build-flow

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add microsoft/power-platform-skills --skill build-flow -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/power-automate/skills/build-flow .github/skills/build-flow && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "build-flow" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-automate/skills/build-flow into .github/skills/build-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-flow", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add microsoft/power-platform-skills --skill build-flow -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install microsoft/power-platform-skills build-flow --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/power-platform-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/power-automate/skills/build-flow .opencode/skills/build-flow && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "build-flow" agent skill from https://github.com/microsoft/power-platform-skills/tree/main/plugins/power-automate/skills/build-flow into .opencode/skills/build-flow/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "build-flow", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: build-flow
GitHub stars: 967
Token cost: ~2.5k tokens
SKILL.md length: 813 words
Files: 1
Skills in repo: 87
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Autonomously build a complete Power Automate flow from a description.

Works in 8 steps: ALWAYS call get_operation_details before… → Use the correct action type. Standard… → Always declare both parameters in the… → …
You need to generate a full flow definition and create it
SKILL.md covers Input, Tools, Critical Rules and Workflow, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Build Flow is an agent skill from microsoft/power-platform-skills, published by the product's own GitHub organization. Autonomously build a complete Power Automate flow from a description. Use when you need to generate a full flow definition and create it.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in AI & LLM Engineering. It works with Power Automate, Microsoft SharePoint and Microsoft Excel. The repository describes itself as: A plugin marketplace for GitHub Copilot and other AI agents that provides Power Platform development plugins, including reusable skills, agents, and commands for building and… The licence is MIT.

When your agent uses it

You need to generate a full flow definition and create it

Example prompts

“/build-flow”

Requirements

Pre-approved tools (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, mcp__flowagent__whoami, mcp__flowagent__doctor, mcp__flowagent__reconnect, mcp__flowagent__list_accounts, mcp__flowagent__switch_account

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

ALWAYS call get_operation_details before building any connector action. Never guess parameter names, enum values, or action types. The…
Use the correct action type. Standard operations use OpenApiConnection. Webhook operations (Approvals StartAndWaitForAnApproval, etc.) use…
Always declare both parameters in the definition
Do NOT include authentication in action inputs. The Flow API auto-injects it on save.
Use Embedded source in connection references. Never Invoker.
HTTP Request triggers (kind: "Http") require Premium. Use kind: "Button" for free/seeded plans.
Validate before creating. Call validate_flow to catch errors before hitting the API.
NEVER use deprecated operations. Common deprecated operations to avoid

What it can do on your machine

Read from SKILL.md and the folder at commit 5ef4e4f. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
- 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
…and 55 more on the same allowed-tools line.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Build Flow loads about 2.5k tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 813 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~37
When it runs · the whole SKILL.md, loaded when a task matches: ~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

allowed-tools: Bash, Read, Write, Glob, Grep, mcp__flowagent__list_environments, mcp__flowagent__set_current_env, m

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from microsoft/power-platform-skills at commit 5ef4e4f, republished under its MIT licence (© microsoft). 813 words, ~2,500 tokens.

Download SKILL.mdSave it as .claude/skills/build-flow/SKILL.md (or your agent's skills folder).

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.
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, mcp__flowagent__whoami, mcp__flowagent__doctor, mcp__flowagent__reconnect, mcp__flowagent__list_accounts, mcp__flowagent__switch_account
user-invocable: true
argument-hint: <description>
context: fork
model: opus

Flow Builder Agent

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.

Input

The user's flow description is: $ARGUMENTS

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.

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

Critical Rules

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).
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.

Always declare both parameters in the definition:

json

"parameters": {
  "$authentication": { "defaultValue": {}, "type": "SecureObject" },
  "$connections": { "defaultValue": {}, "type": "Object" }
}

Do NOT include authentication in action inputs. The Flow API auto-injects it on save.
Use Embedded source in connection references. Never Invoker.
HTTP Request triggers (kind: "Http") require Premium. Use kind: "Button" for free/seeded plans.
Validate before creating. Call validate_flow to catch errors before hitting the API.
NEVER use deprecated operations. Common deprecated operations to avoid:
- Teams: PostUserNotification, PostChannelNotification, PostMessageToChannel, PostMessageToChannelV2, PostMessageToChannelV3 → use PostMessageToConversation
- Teams: PostUserAdaptiveCard, PostChannelAdaptiveCard → use PostCardToConversation
- Outlook: SendEmail → use SendEmailV2; OnNewEmail/OnNewEmailV2 → use OnNewEmailV3
- Approvals: approvalSubscribeV2 → use StartAndWaitForAnApproval
- Planner: CreateTask/CreateTask_V2 → use CreateTask_V3
- Forms: GetFormResponses (polling) → use CreateFormWebhook (webhook)

Show full SKILL.md (432 more words)Show less

Workflow

Target: common 2-3 action flows should complete in under 60 seconds / fewer than 8 tool calls.

Check for templates FIRST: Call list_templates. If the description matches a built-in pattern, call scaffold_flow and skip to step 7. This is the fastest path.
Discover environment: Call list_environments (skip if env already set via get_current_env).
Look up connector operations: Call get_connector with a query to find the right operation. Verify the operation is NOT deprecated (see rule 8).
Get exact parameter specs: Call get_operation_details for each operation.
Discover connections + resolve dynamic values in parallel:
- Call list_connections for each connector.
- Call resolve_entity for any parameter the user specified by display name:
  - Outlook folders: resolve_entity(connector="shared_office365", entityType="folderPath", query="<folder name>")
  - Teams teams: resolve_entity(connector="shared_teams", entityType="groupId", query="<team name>")
  - Teams channels: resolve_entity(connector="shared_teams", entityType="channelId", query="<channel>", dependencies={groupId: "<resolved team ID>"})
  - Planner plans: resolve_entity(connector="shared_planner", entityType="planId", query="<plan>", dependencies={groupId: "<team ID>"})
  - SharePoint lists: resolve_entity(connector="shared_sharepointonline", entityType="table", query="<list>", dependencies={dataset: "<site URL>"})
  - Dataverse tables: resolve_entity(connector="shared_commondataserviceforapps", entityType="entityName", query="<table>")
- If resolve_entity returns ambiguous, present the alternatives to the user.
- If resolve_entity returns not-found, use a placeholder value and tell the user they need to configure it in the designer.
- Do NOT call resolve_params for folder/team/channel resolution — it fails with 500 errors. resolve_entity uses the API Hub directly and works.
Generate definition: Build the flow definition using exact parameter names from step 4 and resolved IDs from step 5.
Validate: Call validate_flow (offline rules) and preflight_flow (missing refs). Fix errors.
Create flow: Call create_flow in Stopped state.
Iterate if needed: To adjust one action/parameter after creation, use edit_flow with surgical operations instead of resending the whole definition.
Report: Output flow ID, name, and state.

Expression Syntax Reference

Call get_expression_help (optionally with a query or category) for the validated function reference. Common patterns:

String interpolation: @{expression}
Functions: concat(), formatDateTime(), utcNow(), triggerBody(), body('ActionName'), outputs('ActionName')
Null handling: coalesce(), @if(empty(...), 'default', ...)
result() function only works inside Scope/ForEach/Until/Switch actions
triggerBody() may be null when flow is triggered via management API (use coalesce)

AI Builder Prompt Actions

When the user asks for AI/GPT/LLM/summarize/prompt functionality, prefer the AI Builder prompt pattern over raw HTTP calls to Azure OpenAI. It uses Copilot credits and requires no API keys.

Two approaches:

"Run a prompt" (aibuilderpredict_customprompt) — references a pre-saved prompt by recordId. Simpler, but requires the prompt to already exist in AI Builder. Use template ai-builder-prompt.
Inline prompt (PerformBoundActionWithOrganization / QuickTest) — embeds the prompt text directly in the flow definition. More complex but self-contained.

Both use the Dataverse connector (shared_commondataserviceforapps). See definition-reference.md for the full action JSON shapes.

To discover the recordId for an existing prompt, query Dataverse:

GET <org-url>/api/data/v9.2/msdyn_aiconfigurations?$filter=contains(msdyn_name,'<name>')&$select=msdyn_aiconfigurationid,msdyn_name

Output expression: outputs('Run_a_prompt')?['body/responsev2/predictionOutput/text']

Files

Just SKILL.md in plugins/power-automate/skills/build-flow of microsoft/power-platform-skills.

Open the folder on GitHubat commit 5ef4e4f

Compare with similar skills

Build Flow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Build Flow compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Build Flow this skillmicrosoft/power-platform-skills	967	—	~2.5k	Automated safety check: Notes	MIT	today
Collaboration Platform Advisor Scott Margettslawve-ai/awesome-legal-skills	826	—	~5.8k	Automated safety check: Pass	Apache-2.0	4 days ago
CLI Microsoft365pnp/cli-microsoft365-mcp-server	131	—	~3.5k	Automated safety check: Pass	MIT	yesterday
Dv Adminmicrosoft/Dataverse-skills	241	—	~5.1k	Automated safety check: Pass	MIT	yesterday
aai-cli Microsoft 365aai-labs/agent-barn	109	—	~1.2k	Automated safety check: Pass	Apache-2.0	today
Erp Xppmicrosoft/Dataverse-skills	241	—	~3.8k	Automated safety check: Pass	MIT	yesterday

Similar skills

Collaboration Platform Advisor Scott Margetts
lawve-ai/awesome-legal-skills
Collaboration platform configuration methodology for legal matter sites.
826 GitHub stars~5.8k tokensUpdated 4 days ago
Data & AnalyticsAuto-check passed
CLI Microsoft365
pnp/cli-microsoft365-mcp-server
Use CLI for Microsoft 365 to manage Microsoft 365 tenants from the terminal.
131 GitHub stars~3.5k tokensUpdated yesterday
Documents & OfficeAuto-check passed
Dv Admin
microsoft/Dataverse-skills
Official
Environment-level Dataverse administration — bulk delete, retention/archival, organization settings, OrgDB settings, recycle bin, audit, and the 37 allowlisted PPAC toggles.
241 GitHub stars~5.1k tokensUpdated yesterday
Backend & APIsAuto-check passed
aai-cli Microsoft 365
aai-labs/agent-barn
Guides work with Outlook, OneDrive, SharePoint, Teams, Excel, To Do and Planner through aai-cli's Microsoft Graph commands, starting from which service owns the data.
109 GitHub stars~1.2k tokensUpdated today
Documents & OfficeAuto-check passed
Erp Xpp
microsoft/Dataverse-skills
Official
X++ code development lifecycle for Finance and Operations — scaffold models, author classes, custom services/APIs, and data entities, install matching SDKs, compile deployable packages, deploy…
241 GitHub stars~3.8k tokensUpdated yesterday
AI & LLM EngineeringAuto-check passed
Dv Metadata
microsoft/Dataverse-skills
Official
Dataverse schema authoring and inspection — tables, columns, relationships, forms, and views.
241 GitHub stars~5.4k tokensUpdated yesterday
AI & LLM EngineeringAuto-check: notes

More from microsoft/power-platform-skills

All 87 skills in this repo

Manage Firewall
microsoft/power-platform-skills
Official
Inspects and configures the web application firewall (WAF) in front of a Power Pages production site.
967 GitHub stars~4.5k tokensUpdated today
Auto-check: notes
Manage Headers
microsoft/power-platform-skills
Official
Inspects and configures the security headers a Power Pages site sends to browsers — Content Security Policy, frame and clickjacking protection, cross-origin sharing, cookie behavior, and related…
967 GitHub stars~3k tokensUpdated today
Auto-check: notes
Scan Code
microsoft/power-platform-skills
Official
Scans a Power Pages site project for security issues in source code and dependencies.
967 GitHub stars~3.4k tokensUpdated today
Auto-check: notes
Scan Site
microsoft/power-platform-skills
Official
Runs a security scan on a deployed Power Pages site, fetches the latest scan report, and produces a plain-language summary.
967 GitHub stars~3.2k tokensUpdated today
Auto-check: notes
Setup Datamodel
microsoft/power-platform-skills
Official
Creates Dataverse tables, columns, and relationships for a Power Pages site based on a data model proposal.
967 GitHub stars~4k tokensUpdated today
Auto-check: notes
Add Server Logic
microsoft/power-platform-skills
Official
Creates, edits, and manages Power Pages Server Logic files — server-side JavaScript that runs securely on the Power Pages runtime.
967 GitHub stars~18k tokensUpdated today
Auto-check: notes

Works with

Questions about Build Flow

What does Build Flow do?

Autonomously build a complete Power Automate flow from a description. Build Flow is an agent skill from microsoft/power-platform-skills, published by the product's own GitHub organization. Autonomously build a complete Power Automate flow from a description.

When should I use Build Flow?

Build Flow fits situations like: you need to generate a full flow definition and create it.

How do I install Build Flow in Claude Code?

Run `npx skills add microsoft/power-platform-skills --skill build-flow -a claude-code`. Or copy the skill folder (plugins/power-automate/skills/build-flow in microsoft/power-platform-skills) into .claude/skills/build-flow in your project. Claude Code loads it when a task matches its description.

How do I install Build Flow in Codex?

Run `npx skills add microsoft/power-platform-skills --skill build-flow -a codex`. Or copy the skill folder (plugins/power-automate/skills/build-flow in microsoft/power-platform-skills) into .agents/skills/build-flow in your project. Codex loads it when a task matches its description.

Can I use Build Flow in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/power-platform-skills --skill build-flow -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/build-flow, .gemini/skills/build-flow, .github/skills/build-flow and .opencode/skills/build-flow in your project.

What does Build Flow need to run?

SKILL.md names no scripts, command-line tools or credentials: Build Flow is instructions for the agent only. Its frontmatter pre-approves these 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, mcp__flowagent__whoami, mcp__flowagent__doctor, mcp__flowagent__reconnect, mcp__flowagent__list_accounts, mcp__flowagent__switch_account.

Does Build Flow access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Build Flow safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Build Flow use?

Build Flow is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Build Flow use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Build Flow?

Skills that share tags, products or a category with Build Flow: Collaboration Platform Advisor Scott Margetts (lawve-ai/awesome-legal-skills, 826 stars), CLI Microsoft365 (pnp/cli-microsoft365-mcp-server, 131 stars), Dv Admin (microsoft/Dataverse-skills, 241 stars) and aai-cli Microsoft 365 (aai-labs/agent-barn, 109 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Build Flow?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/power-platform-skills, which has 967 GitHub stars. The repository holds 87 skills in this directory. The repository was last updated on October 6, 2026.

Source: microsoft/power-platform-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Build Flow

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Flow Builder Agent

Input

Tools

Critical Rules

Workflow

Expression Syntax Reference

AI Builder Prompt Actions

Files

Compare with similar skills

Similar skills

More from microsoft/power-platform-skills

Related

Questions about Build Flow