browse-flows Skill
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments. Published by microsoft in power-platform-skills.
Decision snapshot
Is this a fit?
Developers using power-platform-skills, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Filesystem access, Shell access
Copy skill directory
2 months ago · MIT license
Access note: Local files. Access note: Shell access.
What is browse-flows Skill?
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments. Published by microsoft in power-platform-skills. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Developers using power-platform-skills
Declared skill metadata
- Source file: plugins/power-automate/skills/browse-flows/SKILL.md
Allowed tools declared by source
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
- Local files
- Shell access
Requirements and access
Security and permissions
Review permissions before connecting any MCP server to an agent. Pay special attention to whether it can read local files, write data, call external services, or perform destructive actions.
When to use browse-flows Skill
- Use it for developers using power-platform-skills.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/power-platform-skills
- Skill file: plugins/power-automate/skills/browse-flows/SKILL.md
What it does
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
Skill instructions
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 mcpflowagent<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 listenvironments (use query to filter if user mentioned a name). - If multiple environments, use AskUserQuestion to let user pick. 2. List flows: Call listflows on the selected environment. Use name param if user is looking for something specific. 3. Present results in a table: | | Name | State | Trigger | Actions | Last Modified | |---|------|-------|---------|---------|---------------| 4. Offer next steps via AskUserQuestion: - View flow details (getflow) - Check run history (getrunhistory) - Debug a failed flow (use /debug-flow) - Create a new
Verified compatibility and discovery
Frequently asked questions
What is browse-flows?
browse-flows is a open-source AI agent skill with Copy skill directory. Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
Who is browse-flows best for?
browse-flows is best for reusing agent instructions, scripts, and references.
How do I install browse-flows?
Install or run browse-flows using Copy skill directory. Check browse-flows for the latest setup command.
Is browse-flows actively maintained?
browse-flows may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
