OpenParable
Skip to content
← Back to skills

Browse Flows

Apps & Automation
browse-flows

Browse Flows is an Agent Skill for apps & automation published in the microsoft/power-platform-skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/microsoft/power-platform-skills/blob/HEAD/plugins/power-automate/skills/browse-flows/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/browse-flows, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

  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)