Manage Desktop Flows

microsoft/manage-desktop-flows

Manage and run Power Automate Desktop (RPA) flows and machine groups. Use when the user asks about desktop flows, RPA, or machine groups.

792 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

601

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/microsoft/power-platform-skills --skill manage-desktop-flows

found in the instruction text

Bash runs shell commands — read the instruction before connecting

6 sections, as written by the author

Manage Power Automate Desktop (RPA) flows, machine groups, and run sessions.

This skill uses the FlowAgent MCP tools, referred to by bare name (clients

surface them as mcp__flowagent__<tool> in Claude Code or flowagent-<tool> in

Copilot CLI). If MCP tools aren't available, run /setup to wire the FlowAgent

MCP server.

| Tool | Purpose |

|------|---------|

| list_desktop_flows | Browse RPA flows (filter by name) |

| run_desktop_flow | Trigger with optional machineGroup, body, timeout |

| list_machine_groups | Browse machine infrastructure |

Call list_desktop_flows. Present in table: Name | Status | Created | Modified

Call list_desktop_flows to find the flow (if name given, use name filter)
Optionally call list_machine_groups to target a specific group
Call run_desktop_flow with optional machineGroup, body (input data), timeout
Report: session status (Waiting/InProgress/Failed/Cancelled/Succeeded), outputs

Call list_machine_groups. Present: Name | Type | Status | Machines

Copy the folder

Take microsoft/manage-desktop-flows from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.