mcpbeat

Browse Flows

microsoft/browse-flows

Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.

480 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
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 browse-flows

What it tells the agent to use

found in the instruction text
Bash runs shell commands — read the instruction before connecting

The instruction itself

3 sections, as written by the author

Browse Environments and Flows

Interactive skill for discovering Power Automate environments and flows.

Tools

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.

Steps

  • Resolve environment:
  • If $ARGUMENTS contains an environment ID, use it.
  • Otherwise call list_environments (use query to filter if user mentioned a name).
  • If multiple environments, use AskUserQuestion to let user pick.
  • List flows: Call list_flows on the selected environment. Use name param if user is looking for something specific.
  • Present results in a table:

| # | Name | State | Trigger | Actions | Last Modified |

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

  • Offer next steps via AskUserQuestion:
  • View flow details (get_flow)
  • Check run history (get_run_history)
  • Debug a failed flow (use /debug-flow)
  • Create a new flow (use /create-flow)

How to use it

Copy the folder

Take microsoft/browse-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.