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 skills add https://github.com/microsoft/power-platform-skills --skill route-environments
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 routingconfigured at the admin level in admin.powerplatform.microsoft.com — direct
admins there if they ask about changing org-wide routing
environment determines where new flows are created"
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
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.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
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.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
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.
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.
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.
Take microsoft/route-environments from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.