mcpbeat Sign in

Route Environments Agent Skill

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.

823 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 route-environments

What it tells the agent to use

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

The instruction itself

6 sections, as written by the author

Environment Resolution

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

Step 1: Understand what the user needs

  • "Which environment am I in?" → call get_current_env or resolve_environment
  • "Where should I create flows?" → help them pick the right environment
  • "What environments do I have?" → call list_environments
  • "Switch my environment" → call set_current_env

Step 2: List and explain environments

Call list_environments and present a clear summary:

| Environment | Type | Location | Notes |

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

| ... | Default / Developer / Sandbox / Production | ... | ... |

Help the user identify:

  • Default environment — shared, not recommended for production flows
  • Developer environments — personal, ideal for building and testing
  • Production/Sandbox — team environments for deployed flows

Step 3: Set the working environment

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.

Guidance

  • resolve_environment shows how the environment resolves (routing → poll → fallback)
  • set_current_env changes the session default — it does NOT change tenant-level routing
  • Tenant-level environment routing (which env new makers land in by default) is

configured at the admin level in admin.powerplatform.microsoft.com — direct

admins there if they ask about changing org-wide routing

  • For maker-facing questions: "When you open make.powerautomate.com, your default

environment determines where new flows are created"

Decision Tree

User 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

Other skills for the same job

different authors, same section of the catalogue
Protocolsio Integration
by christophacham
×4

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.

16k tokens
Tailored Resume Generator
by frostant
×4

Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances

3k tokens
Excalidraw Diagram Generator
by github
vendor ×3

Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.

36k tokens scripts
Expo Dev Client
by openai
vendor ×3

Build and distribute Expo development clients locally or via TestFlight

961 tokens
Executing Plans
by ZhanlinCui
×3

Use when you have a written implementation plan to execute in a separate session with review checkpoints

542 tokens
Anndata
by christophacham
×3

Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.

16k tokens
Benchling Integration
by christophacham
×3

Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.

14k tokens
Biopython
by christophacham
×3

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

24k tokens

How to use it

Copy the folder

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