mcpField
B
browse-flows

browse-flows

github.com/microsoftDevelopment1.1k149 installsUpdated today
Repository

About browse-flows

An interactive skill for finding Power Automate environments and flows. It presents flow state, triggers, actions, and modification times, then offers paths to inspect, debug, or create flows.

Key features

  1. 01Resolve an environment from an ID or query
  2. 02List flows with names and run details
  3. 03Present state, trigger, actions, and modified time
  4. 04Offer flow inspection, debugging, or creation

Use cases

  1. 01Finding an environment by name
  2. 02Browsing flows in a selected environment
  3. 03Choosing a flow to inspect or debug
  4. 04Moving from flow discovery to creation

MCP support

Uses FlowAgent MCP tools to list environments and flows, with options to retrieve flow details and run history.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/microsoft/power-platform-skills --skill browse-flows

After installing, type/browse-flowsin Claude Code to confirm it loaded.

Details

From the project README

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 no MCP tools are present, the plugin is not wired up — run the setup skill.

Steps

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

  2. List flows: Call list_flows on the selected environment. Use name param if user is looking for something specific.

  3. Present results in a table:

    #NameStateTriggerActionsLast Modified

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

Comments

Markdown supported