Check Power Platform environment routing status and understand default environment resolution. Use when the user asks about environment routing, developer environments, or new maker landing. Routing is configured in the admin center, not here. NOT for listing flows or managing connections.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
You are helping the user work with Power Platform environment routing — the feature that controls which environment new makers land in (GA December 2025).
Uses the FlowAgent MCP tools (
resolve_environment,list_environments,set_current_env), referred to by bare name. In Claude Code they appear asmcp__flowagent__<tool>; in Copilot CLI asflowagent-<tool>.
Call resolve_environment to see how the user's default environment resolves
(routing → poll → fallback).
Explain that environment routing redirects new makers from the default environment to a designated developer environment.
Key facts:
specificGroups rather than tenant-wideCall list_environments (use the query param to filter by name).
Show environment types and help the user identify:
Help the user understand which environment they'd land in by calling
resolve_environment.
admin.powerplatform.microsoft.com > Environments > Environment routingresolve_environment tool can check the current routing state but cannot modify itUser asks about environment routing?
├── "What is it?" → Explain: redirects new makers from default to dev env
├── "Is it enabled?" → resolve_environment to check
├── "How do I enable it?" → Direct to PPAC admin center
├── "Which environment am I in?" → list_environments + resolve_environment
└── "What environments exist?" → list_environments with details
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.
The English summary is being prepared. Showing the original description.
Integrates Power Pages generative-AI summarization APIs (PREVIEW) into a Single Page Application (SPA) site — the Search Summary API and the Data Summarization API — on any record-detail or list page. Generates per-target service code (CSRF-handled) and AI site settings; delegates Web API settings, table permissions, and web roles to `/integrate-webapi` and `/create-webroles`. Use whenever a user wants AI/Copilot output that condenses Dataverse content on a Power Pages site — an AI summary, AI-generated overview or "key insights" across a record or list, a search-results summary, a case/incident summary, or recommendation-chip refinement — even when phrased as "AI-generated paragraph", "insights", or "overview". Do NOT use for: generative pages in model-driven apps (use the model-apps `genpage` skill), Copilot Studio agents/chatbots, summarizing documents or PDFs, Power BI dashboards, plain keyword search with no AI summary, or plain Dataverse CRUD (use `/integrate-webapi`).
The English summary is being prepared. Showing the original description.
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
The English summary is being prepared. Showing the original description.
Internal implementation skill invoked by /add-native for camera, image picker, barcode scanner, QR scanner, and camera/gallery Dataverse artifact workflows.
The English summary is being prepared. Showing the original description.
Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flows to additional pages without re-creating metadata. Use when the user wants to add, connect, register, or link a Power Automate cloud flow to their site.
The English summary is being prepared. Showing the original description.
Use when adding a Power Platform connector to an Expo/React Native Power Apps mobile app and no dedicated mobile connector skill exists.
The English summary is being prepared. Showing the original description.