microsoft/power-platform-skills is a plugin marketplace containing reusable skills, agents, and commands for developing with Microsoft Power Platform. Developers use it to build and deploy Power Pages sites, model-driven Power Apps, and related solutions through Claude Code or GitHub Copilot. The catalogue entries are the marketplace's included skills, agents, plugins, and other agent components.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/microsoft/power-platform-skills/create-flownpx skills add microsoft/power-platform-skills --skill create-flowgit clone --depth 1 https://github.com/microsoft/power-platform-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/microsoft/power-platform-skills/create-flow)<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/create-flow"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/create-flow.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00022 | $0.01141 |
| Opus 5 | $0.00011 | $0.00571 |
| Sonnet 5 | $0.00004 | $0.00228 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
create-flow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 51 lines · 22 tokens per session scan A 3b60bbf5610b
create-flow is a skill published in the GitHub repository microsoft/power-platform-skills (814 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 1,141 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
canvas-apps-ui-gen
Generates paste-ready Power Apps Canvas App YAML. Invoke when the user wants to replicate a UI mockup, improve an existing Canvas app screen, or build a new screen from a text description. Also invoke when the user asks to "improve", "redesign", or "generate YAML" for a Canvas app screen.
link-ticket-to-session
Link the current Claude Code session to a ticket (Linear, Jira, GitHub Issues, or GitHub Pull Requests) and cache its title/status in karma. Use when the user explicitly asks to link, attach, associate, or connect this session to a ticket, issue, or PR — e.g. "/link-ticket-to-session ABC-123", "link this session to…
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
outcome-roadmap
Transform an output-focused roadmap (feature list) into an outcome-focused one. Rewrites initiatives as outcome statements reflecting user and business impact. Use when a roadmap lists features instead of results, when making a roadmap more strategic, or when communicating what success looks like vs what will be built.