Update FlowStudio Power Automate skills

docs/README.skills.md

@@ -162,8 +162,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` | 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 |
+| [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 `flowstudio-power-automate-build`, `flowstudio-power-automate-debug`, `flowstudio-power-automate-monitoring` (Pro+), or `flowstudio-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 monitoring using the FlowStudio MCP cached store: failure rates, run-health trends, maker/app inventory, inactive owners, and compliance/health reports. Use only for aggregated tenant views. For one environment, one flow, run control, or root-cause debugging, use flowstudio-power-automate-mcp, flowstudio-power-automate-debug, or the server monitor-flow bundle. Requires FlowStudio for Teams or MCP Pro+. | 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/.github/plugin/plugin.json

@@ -19,10 +19,10 @@
     "governance"
   ],
   "skills": [
-    "./skills/flowstudio-power-automate-build/",
-    "./skills/flowstudio-power-automate-debug/",
-    "./skills/flowstudio-power-automate-governance/",
-    "./skills/flowstudio-power-automate-mcp/",
-    "./skills/flowstudio-power-automate-monitoring/"
+    "./skills/flowstudio-power-automate-mcp",
+    "./skills/flowstudio-power-automate-debug",
+    "./skills/flowstudio-power-automate-build",
+    "./skills/flowstudio-power-automate-monitoring",
+    "./skills/flowstudio-power-automate-governance"
   ]
 }

plugins/flowstudio-power-automate/README.md

@@ -49,7 +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 `power-automate-mcp` skill for connection setup.  
+See the `flowstudio-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 `power-automate-mcp` skill's **connection-references.md** reference
+See the `flowstudio-power-automate-mcp` skill's **connection-references.md** reference
 for the full connection reference structure.
 
 ---
@@ -219,59 +219,6 @@ 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.
@@ -456,7 +403,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 power-automate-debug skill for full diagnosis workflow
+    # See flowstudio-power-automate-debug skill for full diagnosis workflow
 ```
 
 #### 7c — Swap to the production trigger
@@ -502,6 +449,12 @@ else:
 | Checking `result["error"]` exists | Always present; true error is `!= null` | Use `result.get("error") is not None` |
 | Flow deployed but state is "Stopped" | Flow won't run on schedule | Call `set_live_flow_state` with `state: "Started"` — do **not** use `update_live_flow` for state changes |
 | Teams "Chat with Flow bot" recipient as object | 400 `GraphUserDetailNotFound` | Use plain string with trailing semicolon (see below) |
+| Copilot/Skills flow not in a solution | Copilot Studio may not discover it as an agent tool | After deploy, call `add_live_flow_to_solution` with the target `solutionId` |
+| Button/Skills trigger used for MCP testing | MCP cannot directly fire the production trigger | Test the same actions through a temporary HTTP twin, then swap the trigger back |
+| Connector action missing `metadata.operationMetadataId` | Designer/run-only UI can behave inconsistently | Preserve existing IDs; add stable GUIDs for new connector actions |
+| Placeholder Excel `scriptId` | Dynamic validation fails at save time | Resolve the real Office Script ID before deploying |
+| SharePoint `PatchItem` omits required fields | Save can fail even if the field is not changing | Echo unchanged required fields such as `item/Title` |
+| Copilot Studio connector calls a draft agent | Connector invocation can fail or hit stale behavior | Publish the agent before testing/resubmitting the flow |
 
 ### Teams `PostMessageToConversation` — Recipient Formats
 
@@ -528,5 +481,5 @@ The `body/recipient` parameter format depends on the `location` value:
 
 ## Related Skills
 
-- `power-automate-mcp` — Foundation skill: connection setup, MCP helper, tool discovery
-- `power-automate-debug` — Debug failing flows after deployment
+- `flowstudio-power-automate-mcp` — Core connection setup and tool reference
+- `flowstudio-power-automate-debug` — Debug failing flows after deployment

skills/flowstudio-power-automate-build/references/action-patterns-connectors.md

@@ -132,6 +132,10 @@ Result reference: `@body('Get_SP_Item')?['FieldName']`
 }
 ```
 
+> `PatchItem` can validate required SharePoint columns even when you are not
+> changing those fields. Echo unchanged required fields from the trigger or a
+> prior Get Item action, for example `item/Title`, and use internal field names.
+
 ---
 
 ### SharePoint — File Upsert (Create or Overwrite in Document Library)
@@ -286,6 +290,10 @@ SharePoint REST API via the `HttpRequest` operation:
 > The `HttpRequest` operation reuses the existing SharePoint connection — no extra
 > authentication needed. Use this when the standard Update Item connector can't
 > reach the target list (different site collection, or you need raw REST control).
+> Keep the connector-specific parameter names exactly as shown:
+> `parameters/method`, `parameters/uri`, `parameters/headers`, and
+> `parameters/body`. The body is a JSON string, and `parameters/uri` is relative
+> to the SharePoint `dataset`.
 
 ---
 
@@ -340,6 +348,22 @@ the file; the flow downloads and filters it for before/after comparisons.
 
 ---
 
+## Excel Online
+
+### Excel — Run Office Script
+
+Office Script actions require real workbook and script identifiers at save time.
+Do not deploy placeholder `scriptId` values; `update_live_flow` can fail during
+dynamic operation validation even before a test run exists.
+
+Use `describe_live_connector` or `get_live_dynamic_options` when available, or
+ask the user for the workbook and script if they are not discoverable. If a real
+`scriptId` still cannot be resolved, ask the user to add the Run script action
+once in the designer, then read the flow definition and preserve the resolved
+parameters.
+
+---
+
 ## Outlook
 
 ### Outlook — Send Email
@@ -479,6 +503,20 @@ For 1:1 ("Chat with Flow bot"), use `"location": "Chat with Flow bot"` and set
 
 ---
 
+## Copilot Studio
+
+### Copilot Studio — Invoke Agent
+
+When using the Copilot Studio connector, publish the agent before running the
+flow. Draft/test agents can exist in the studio canvas but still be unavailable
+or stale through the flow connector endpoint.
+
+If a connector action fails with an unavailable-agent or endpoint-style error,
+publish the agent, wait briefly for propagation, then resubmit the same flow run
+before changing the flow definition.
+
+---
+
 ## Approvals
 
 ### Split Approval (Create → Wait)

skills/flowstudio-power-automate-build/references/action-patterns-core.md

@@ -337,6 +337,23 @@ walking a time range, polling until a status changes).
 
 ---
 
+### Agent Retry Loop
+
+When a flow calls an AI or Copilot-style agent until it reaches a terminal
+outcome, keep the loop state explicit:
+
+- Initialize variables such as `agentStatus`, `attempt`, and `finalPayload`
+  before the `Until`.
+- Inside the loop, call the agent, validate the response, update the status, and
+  delay/retry only when the status is non-terminal.
+- Put final dispatch actions such as email, SharePoint update, or Teams post
+  after the loop so retries do not duplicate side effects.
+- If the platform rejects a complex `Switch` nested inside `Until`, keep the
+  loop body to simple validation and state updates, then route with `Switch`
+  after the loop.
+
+---
+
 ### Async Polling with RequestId Correlation
 
 When an API starts a long-running job asynchronously (e.g. Power BI dataset refresh,
@@ -486,6 +503,19 @@ Normalize before compare:  @replace(coalesce(outputs('Value'),''),'_',' ')
 Robust non-empty check:    @greater(length(trim(coalesce(string(outputs('Val')), ''))), 0)
 ```
 
+### Unsupported / Risky Expression Assumptions
+
+Power Automate expressions are Workflow Definition Language, not JavaScript.
+These patterns often look plausible but do not deploy or do not behave as agents
+expect:
+
+| Goal | Avoid | Use instead |
+|---|---|---|
+| Build an object inline | `createObject(...)` | A Compose action with a JSON object literal |
+| Transform an array inline | `select(...)` inside an expression | Data Operations `Select` action |
+| Filter an array inline | `filter(...)` inside an expression | Data Operations `Filter array` action |
+| Find an array item index | `indexOf(array, item)` | Foreach with a counter variable, or build a keyed object map |
+
 ### Newlines in Expressions
 
 > **`\n` does NOT produce a newline inside Power Automate expressions.** It is