plugins/power-automate/skills/route-environments/SKILL.md
Manage environment resolution — check which environment you create flows in by default, list available environments, and set your working environment. Use when the user asks about environments, their default environment, where to create flows, or switching environments.
npx skillsauth add microsoft/power-platform-skills route-environmentsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are helping the user understand and manage which Power Automate environment they work in — where their flows are created, where they should build new ones, and how to switch between environments.
Uses the FlowAgent MCP tools (
resolve_environment,list_environments,set_current_env,get_current_env).
get_current_env or resolve_environmentlist_environmentsset_current_envCall list_environments and present a clear summary:
| Environment | Type | Location | Notes | |-------------|------|----------|-------| | ... | Default / Developer / Sandbox / Production | ... | ... |
Help the user identify:
If the user wants to create flows in a specific environment, call
set_current_env with that environment ID. This pins all subsequent
FlowAgent operations to that environment (no need to pass --env each time).
Recommendation for new users: If they have a Developer environment, suggest using that. If not, suggest they ask their admin to provision one, or use the default environment for simple personal automations.
resolve_environment shows how the environment resolves (routing → poll → fallback)set_current_env changes the session default — it does NOT change tenant-level routingadmin.powerplatform.microsoft.com — direct
admins there if they ask about changing org-wide routingUser asks about environments?
├── "Which environment am I in?" → get_current_env / resolve_environment
├── "What environments exist?" → list_environments with summary table
├── "Where should I build?" → Recommend Developer env; set_current_env
├── "Switch to X environment" → set_current_env
├── "How do I create a new environment?" → Direct to PPAC admin center
└── "What is environment routing?" → Explain: determines default for new makers
tools
Adds Work IQ (M365 Copilot Search) to a Power Apps code app via the Work IQ Copilot MCP connector (shared_a365copilotchatmcp), then wires up a production-ready McpSession wrapper for AI-powered, knowledge-grounded search and chat. Use when integrating Microsoft 365 Copilot search/chat. The CopilotChat tool searches internal Microsoft 365 content (documents, emails, chats, sites, files) across your organization — prefer workload-specific tools (SharePoint, OneDrive, Teams, Mail) when the workload is explicit; do not use it for general knowledge, news, public web, or external information.
tools
Use when the user wants to preview generated screens in a browser without starting Metro / a simulator — for example after /create-mobile-app finishes or after /edit-app regenerates a screen.
development
Use when the user wants to iterate on an existing generated Power Apps mobile app after /create-mobile-app: update the plan, data model, native capabilities, design, screens, generated app code, and preview without restarting the full project flow.
development
Creates and manages the brand design system for a Power Apps mobile app. Generates brand/design-system.md (source of truth), brand/tokens.ts (importable Tamagui tokens), and brand/design-system.html (visual gallery). Triggered at Step 6.5 of /create-mobile-app, or standalone via /design-system.