feat: align FlowStudio Power Automate skills with MCP server v1.1.6

docs/README.skills.md

@@ -153,8 +153,8 @@ See [CONTRIBUTING.md](../CONTRIBUTING.md#adding-skills) for guidelines on how to
 | [flowstudio-power-automate-build](../skills/flowstudio-power-automate-build/SKILL.md)<br />`gh skills install github/awesome-copilot flowstudio-power-automate-build` | Build, scaffold, and deploy Power Automate cloud flows using the FlowStudio MCP server. Your agent constructs flow definitions, wires connections, deploys, and tests — all via MCP without opening the portal. Load this skill when asked to: create a flow, build a new flow, deploy a flow definition, scaffold a Power Automate workflow, construct a flow JSON, update an existing flow's actions, patch a flow definition, add actions to a flow, wire up connections, or generate a workflow definition from scratch. Requires a FlowStudio MCP subscription — see https://mcp.flowstudio.app | `references/action-patterns-connectors.md`<br />`references/action-patterns-core.md`<br />`references/action-patterns-data.md`<br />`references/build-patterns.md`<br />`references/flow-schema.md`<br />`references/trigger-types.md` |
 | [flowstudio-power-automate-debug](../skills/flowstudio-power-automate-debug/SKILL.md)<br />`gh skills install github/awesome-copilot flowstudio-power-automate-debug` | Debug failing Power Automate cloud flows using the FlowStudio MCP server. The Graph API only shows top-level status codes. This skill gives your agent action-level inputs and outputs to find the actual root cause. Load this skill when asked to: debug a flow, investigate a failed run, why is this flow failing, inspect action outputs, find the root cause of a flow error, fix a broken Power Automate flow, diagnose a timeout, trace a DynamicOperationRequestFailure, check connector auth errors, read error details from a run, or troubleshoot expression failures. Requires a FlowStudio MCP subscription — see https://mcp.flowstudio.app | `references/common-errors.md`<br />`references/debug-workflow.md` |
 | [flowstudio-power-automate-governance](../skills/flowstudio-power-automate-governance/SKILL.md)<br />`gh skills install github/awesome-copilot flowstudio-power-automate-governance` | Govern Power Automate flows and Power Apps at scale using the FlowStudio MCP cached store. Classify flows by business impact, detect orphaned resources, audit connector usage, enforce compliance standards, manage notification rules, and compute governance scores — all without Dataverse or the CoE Starter Kit. Load this skill when asked to: tag or classify flows, set business impact, assign ownership, detect orphans, audit connectors, check compliance, compute archive scores, manage notification rules, run a governance review, generate a compliance report, offboard a maker, or any task that involves writing governance metadata to flows. Requires a FlowStudio for Teams or MCP Pro+ subscription — see https://mcp.flowstudio.app | None |
-| [flowstudio-power-automate-mcp](../skills/flowstudio-power-automate-mcp/SKILL.md)<br />`gh skills install github/awesome-copilot flowstudio-power-automate-mcp` | Give your AI agent the same visibility you have in the Power Automate portal — plus a bit more. The Graph API only returns top-level run status. Flow Studio MCP exposes action-level inputs, outputs, loop iterations, and nested child flow failures. Use when asked to: list flows, read a flow definition, check run history, inspect action outputs, resubmit a run, cancel a running flow, view connections, get a trigger URL, validate a definition, monitor flow health, or any task that requires talking to the Power Automate API through an MCP tool. Also use for Power Platform environment discovery and connection management. Requires a FlowStudio MCP subscription or compatible server — see https://mcp.flowstudio.app | `references/MCP-BOOTSTRAP.md`<br />`references/action-types.md`<br />`references/connection-references.md`<br />`references/tool-reference.md` |
-| [flowstudio-power-automate-monitoring](../skills/flowstudio-power-automate-monitoring/SKILL.md)<br />`gh skills install github/awesome-copilot flowstudio-power-automate-monitoring` | Monitor Power Automate flow health, track failure rates, and inventory tenant assets using the FlowStudio MCP cached store. The live API only returns top-level run status. Store tools surface aggregated stats, per-run failure details with remediation hints, maker activity, and Power Apps inventory — all from a fast cache with no rate-limit pressure on the PA API. Load this skill when asked to: check flow health, find failing flows, get failure rates, review error trends, list all flows with monitoring enabled, check who built a flow, find inactive makers, inventory Power Apps, see environment or connection counts, get a flow summary, or any tenant-wide health overview. Requires a FlowStudio for Teams or MCP Pro+ subscription — see https://mcp.flowstudio.app | None |
+| [flowstudio-power-automate-mcp](../skills/flowstudio-power-automate-mcp/SKILL.md)<br />`gh skills install github/awesome-copilot flowstudio-power-automate-mcp` | Foundation skill for Power Automate via FlowStudio MCP — auth setup, the reusable MCP helper (Python + Node.js), tool discovery via `list_skills` / `tool_search`, and oversized-response handling. Load this skill first when connecting an agent to Power Automate. For specialized workflows, load `power-automate-build`, `power-automate-debug`, `power-automate-monitoring` (Pro+), or `power-automate-governance` (Pro+) — each contains the workflow narrative, this skill provides the plumbing they all rely on. Requires a FlowStudio MCP subscription or compatible server — see https://mcp.flowstudio.app | `references/MCP-BOOTSTRAP.md`<br />`references/action-types.md`<br />`references/connection-references.md`<br />`references/tool-reference.md` |
+| [flowstudio-power-automate-monitoring](../skills/flowstudio-power-automate-monitoring/SKILL.md)<br />`gh skills install github/awesome-copilot flowstudio-power-automate-monitoring` | **Pro+ subscription required.** Tenant-wide Power Automate flow health monitoring, failure rate analytics, and asset inventory using the FlowStudio MCP cached store. Load this skill ONLY for tenant-wide aggregated views — not for listing flows in a single environment or debugging a specific run (use power-automate-mcp or power-automate-debug for those). Not the same as the server's `monitor-flow` tool bundle (`tool_search query: "skill:monitor-flow"`) — that bundle is for runtime control of a single flow (start/stop/trigger/ cancel/resubmit); this skill is for tenant-wide health analytics over the cached store. Load when asked to: monitor tenant health, get aggregated failure rates over a time window, review tenant-wide error trends, find inactive makers across the tenant, inventory all Power Apps in the tenant, compute governance scores, generate a compliance report, or run a tenant-wide health overview. Requires a FlowStudio for Teams or MCP Pro+ subscription — see https://mcp.flowstudio.app | None |
 | [fluentui-blazor](../skills/fluentui-blazor/SKILL.md)<br />`gh skills install github/awesome-copilot fluentui-blazor` | Guide for using the Microsoft Fluent UI Blazor component library (Microsoft.FluentUI.AspNetCore.Components NuGet package) in Blazor applications. Use this when the user is building a Blazor app with Fluent UI components, setting up the library, using FluentUI components like FluentButton, FluentDataGrid, FluentDialog, FluentToast, FluentNavMenu, FluentTextField, FluentSelect, FluentAutocomplete, FluentDesignTheme, or any component prefixed with "Fluent". Also use when troubleshooting missing providers, JS interop issues, or theming. | `references/DATAGRID.md`<br />`references/LAYOUT-AND-NAVIGATION.md`<br />`references/SETUP.md`<br />`references/THEMING.md` |
 | [folder-structure-blueprint-generator](../skills/folder-structure-blueprint-generator/SKILL.md)<br />`gh skills install github/awesome-copilot folder-structure-blueprint-generator` | Comprehensive technology-agnostic prompt for analyzing and documenting project folder structures. Auto-detects project types (.NET, Java, React, Angular, Python, Node.js, Flutter), generates detailed blueprints with visualization options, naming conventions, file placement patterns, and extension templates for maintaining consistent code organization across diverse technology stacks. | None |
 | [foundry-agent-sync](../skills/foundry-agent-sync/SKILL.md)<br />`gh skills install github/awesome-copilot foundry-agent-sync` | Create and synchronize prompt-based AI agents directly within Azure AI Foundry via REST API, from a local JSON manifest. Unlike scaffolding skills that only generate local code, this skill registers agents in the Foundry service itself — making them immediately available for invocation. Use when the user asks to create agents in Foundry, sync, deploy, register, or push agents to Foundry, update agent instructions, or scaffold the manifest and sync script for a new repository. Triggers: 'create agent in foundry', 'sync foundry agents', 'deploy agents to foundry', 'register agents in foundry', 'push agents', 'create foundry agent manifest', 'scaffold agent sync'. | None |

plugins/flowstudio-power-automate/README.md

@@ -8,13 +8,13 @@ Requires a [FlowStudio MCP](https://mcp.flowstudio.app) subscription.
 
 ## What Agents Can't See Today
 
-| What you see in the portal | What agents see via Graph API |
-|---|---|
-| Action inputs and outputs | Run passed or failed (no detail) |
-| Loop iteration data | Nothing |
-| Child flow failures | Top-level error code only |
-| Flow health and failure rates | Nothing |
-| Who built a flow, what connectors it uses | Nothing |
+| What you see in the portal                | What agents see via Graph API    |
+| ----------------------------------------- | -------------------------------- |
+| Action inputs and outputs                 | Run passed or failed (no detail) |
+| Loop iteration data                       | Nothing                          |
+| Child flow failures                       | Top-level error code only        |
+| Flow health and failure rates             | Nothing                          |
+| Who built a flow, what connectors it uses | Nothing                          |
 
 Flow Studio MCP fills these gaps.
 
@@ -28,13 +28,13 @@ copilot plugin install flowstudio-power-automate@awesome-copilot
 
 ### Skills
 
-| Skill | Description |
-|-------|-------------|
-| `flowstudio-power-automate-mcp` | Core connection setup, tool discovery, and operations — list flows, read definitions, check runs, resubmit, cancel. |
-| `flowstudio-power-automate-debug` | Step-by-step diagnostic workflow — action-level inputs and outputs, not just error codes. Identifies root cause across nested child flows and loop iterations. |
-| `flowstudio-power-automate-build` | Build and deploy flow definitions from scratch — scaffold triggers, wire connections, deploy, and test via resubmit. |
-| `flowstudio-power-automate-monitoring` | Flow health from the cached store — failure rates, run history with remediation hints, maker inventory, Power Apps, environment and connection counts. |
-| `flowstudio-power-automate-governance` | Governance workflows — classify flows by business impact, detect orphaned resources, audit connectors, manage notification rules, compute archive scores. |
+| Skill                                  | Description                                                                                                                                                    |
+| -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `flowstudio-power-automate-mcp`        | Foundation skill — auth setup, the reusable MCP helper (Python + Node.js), tool discovery via `list_skills`/`tool_search`, oversized-response handling. Load first. |
+| `flowstudio-power-automate-debug`      | Step-by-step diagnostic workflow — action-level inputs and outputs, not just error codes. Identifies root cause across nested child flows and loop iterations. |
+| `flowstudio-power-automate-build`      | Build and deploy flow definitions from scratch — scaffold triggers, wire connections, deploy, and test via resubmit.                                           |
+| `flowstudio-power-automate-monitoring` | Flow health from the cached store — failure rates, run history with remediation hints, maker inventory, Power Apps, environment and connection counts.         |
+| `flowstudio-power-automate-governance` | Governance workflows — classify flows by business impact, detect orphaned resources, audit connectors, manage notification rules, compute archive scores.      |
 
 The first three skills call the live Power Automate API. The monitoring and governance skills read from a cached daily snapshot with aggregated stats and governance metadata.
 
@@ -49,6 +49,7 @@ The first three skills call the live Power Automate API. The monitoring and gove
 1. Install the plugin
 2. Get your API key at [mcp.flowstudio.app](https://mcp.flowstudio.app)
 3. Configure the MCP connection in VS Code (`.vscode/mcp.json`):
+
    ```json
    {
      "servers": {

skills/flowstudio-power-automate-build/SKILL.md

@@ -24,7 +24,7 @@ Step-by-step guide for constructing and deploying Power Automate cloud flows
 programmatically through the FlowStudio MCP server.
 
 **Prerequisite**: A FlowStudio MCP server must be reachable with a valid JWT.
-See the `flowstudio-power-automate-mcp` skill for connection setup.  
+See the `power-automate-mcp` skill for connection setup.  
 Subscribe at https://mcp.flowstudio.app
 
 ---
@@ -192,7 +192,7 @@ for connector in connectors_needed:
 > connection_references = ref_flow["properties"]["connectionReferences"]
 > ```
 
-See the `flowstudio-power-automate-mcp` skill's **connection-references.md** reference
+See the `power-automate-mcp` skill's **connection-references.md** reference
 for the full connection reference structure.
 
 ---
@@ -219,6 +219,59 @@ definition = {
 
 ---
 
+## Step 3a — Resolving Dynamic Connector Values
+
+When an action input needs a value picked from a connector dropdown (e.g. a
+SharePoint list ID, a Dataverse table name, a user's Azure AD UPN), use
+`get_live_dynamic_options` to resolve it via MCP rather than hardcoding GUIDs.
+
+```python
+# Resolve a SharePoint list by site
+opts = mcp("get_live_dynamic_options",
+    environmentName=ENV,
+    connectorName="shared_sharepointonline",
+    operationId="GetTables",
+    parameters={"dataset": "https://contoso.sharepoint.com/sites/HR"})
+# opts["value"] → [{"Name": "<list-guid>", "DisplayName": "Employees"}, ...]
+```
+
+> **Outer-parameter auto-bridge** (server v1.1.6+): you can pass arbitrary outer
+> parameters directly in `parameters` — the server now synthesizes the
+> `parameterReference` mapping that PA's listEnum requires. Before 1.1.6 you had
+> to declare `dynamicMetadata.parameters: {paramName: {parameterReference: "name"}}`
+> manually or get `IncorrectDynamicInvokeParameter`. This makes it practical to
+> invoke arbitrary connector operations through the dynamic-options pipeline
+> (e.g. `shared_office365users.SearchUserV2` for AAD user lookup).
+
+### AadGraph user-picker fallback
+
+For Outlook actions like `GetEmailsV3` (parameters `mailboxAddress`, `to`, `cc`,
+`from`), PA's listEnum uses `builtInOperation:AadGraph.GetUsers` — which is
+broken and returns `DynamicListValuesUndefinedOrInvalid` for every call.
+
+`describe_live_connector` (v1.1.6+) detects these parameters and returns a
+structured `fallback` field on each affected parameter pointing at a working
+alternative. **Use `shared_office365users.SearchUserV2`** to resolve the same
+AAD user shape `{value: [{id, displayName, mail, userPrincipalName, ...}]}`:
+
+```python
+# Borrow a shared_office365users connection (any active one will do)
+conn = next(c for c in conn_map if "office365users" in c)
+
+users = mcp("get_live_dynamic_options",
+    environmentName=ENV,
+    connectorName="shared_office365users",
+    connectionName=conn_map[conn],   # see Step 2a
+    operationId="SearchUserV2",
+    parameters={"searchTerm": "john", "top": 10})
+# users["value"] → [{"Id": "...", "DisplayName": "John Smith", "Mail": "..."}, ...]
+```
+
+Then plug the resolved `Mail` value into the Outlook action's parameter — no
+need to call `AadGraph.GetUsers` directly.
+
+---
+
 ## Step 4 — Deploy (Create or Update)
 
 `update_live_flow` handles both creation and updates in a single tool.
@@ -403,7 +456,7 @@ if run["status"] == "Failed":
     root = err["failedActions"][-1]
     print(f"Root cause: {root['actionName']} → {root.get('code')}")
     # Debug and fix the definition before proceeding
-    # See flowstudio-power-automate-debug skill for full diagnosis workflow
+    # See power-automate-debug skill for full diagnosis workflow
 ```
 
 #### 7c — Swap to the production trigger
@@ -475,5 +528,5 @@ The `body/recipient` parameter format depends on the `location` value:
 
 ## Related Skills
 
-- `flowstudio-power-automate-mcp` — Core connection setup and tool reference
-- `flowstudio-power-automate-debug` — Debug failing flows after deployment
+- `power-automate-mcp` — Foundation skill: connection setup, MCP helper, tool discovery
+- `power-automate-debug` — Debug failing flows after deployment

skills/flowstudio-power-automate-debug/SKILL.md

@@ -28,7 +28,7 @@ cloud flows through the FlowStudio MCP server.
 > [Null value crashes child flow](https://github.com/ninihen1/power-automate-mcp-skills/blob/main/examples/null-child-flow.md)
 
 **Prerequisite**: A FlowStudio MCP server must be reachable with a valid JWT.
-See the `flowstudio-power-automate-mcp` skill for connection setup.  
+See the `power-automate-mcp` skill for connection setup.  
 Subscribe at https://mcp.flowstudio.app
 
 ---
@@ -309,6 +309,18 @@ print(json.dumps(out['outputs']['body'], indent=2)[:500])
 Look for `ConnectionAuthorizationFailed` — the connection owner must match the
 service account running the flow. Cannot fix via API; fix in PA designer.
 
+### Outlook user-picker failures (`DynamicListValuesUndefinedOrInvalid`)
+Outlook actions like `GetEmailsV3` use parameters (`mailboxAddress`, `to`, `cc`,
+`from`) whose dropdown is backed by `builtInOperation:AadGraph.GetUsers` — which
+is broken at the PA listEnum layer and always returns
+`DynamicListValuesUndefinedOrInvalid`. This shows up when an agent rebuilds or
+modifies an Outlook action via `update_live_flow` and tries to resolve a user
+through dynamic options. **Don't fix it by retrying AadGraph** — switch to
+`shared_office365users.SearchUserV2` instead (returns the same AAD user shape).
+See the `power-automate-build` skill, **Step 3a — Resolving Dynamic Connector
+Values**, for the working pattern. `describe_live_connector` (v1.1.6+) returns
+this fallback as a structured `fallback` field on the affected parameter.
+
 ---
 
 ## Step 8 — Apply the Fix
@@ -421,5 +433,5 @@ print(f"Status: {result['responseStatus']}, Body: {result.get('responseBody')}")
 
 ## Related Skills
 
-- `flowstudio-power-automate-mcp` — Core connection setup and operation reference
-- `flowstudio-power-automate-build` — Build and deploy new flows
+- `power-automate-mcp` — Foundation skill: connection setup, MCP helper, tool discovery
+- `power-automate-build` — Build and deploy new flows