feat: add monitoring + governance skills, strengthen debug + build

New skills:
- flowstudio-power-automate-monitoring: flow health, failure rates,
  maker inventory, Power Apps, cached store tools
- flowstudio-power-automate-governance: 10 CoE-aligned workflows —
  compliance review, orphan detection, archive scoring, connector audit,
  notification management, tagging, offboarding, security review,
  environment governance, dashboard

Updated skills:
- flowstudio-power-automate-debug: mandatory action output inspection
  (not just error codes), resubmit works for ALL trigger types
- flowstudio-power-automate-build: resubmit promoted as first testing
  option, trigger_live_flow demoted to custom-payload only
- flowstudio-power-automate-mcp: trigger_live_flow content-type note,
  branch URLs updated to main

All response shapes verified against real API calls. All 10 governance
workflows validated by agent simulation (10/10 PASS).

Author: ninihen1

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

@@ -2,11 +2,20 @@
 name: flowstudio-power-automate-build
 description: >-
   Build, scaffold, and deploy Power Automate cloud flows using the FlowStudio
-  MCP server. Load this skill when asked to: create a flow, build a new flow,
+  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
+metadata:
+  openclaw:
+    requires:
+      env:
+        - FLOWSTUDIO_MCP_TOKEN
+    primaryEnv: FLOWSTUDIO_MCP_TOKEN
+    homepage: https://mcp.flowstudio.app
 ---
 
 # Build & Deploy Power Automate Flows with FlowStudio MCP
@@ -15,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
 
 ---
@@ -278,6 +287,8 @@ check = mcp("get_live_flow", environmentName=ENV, flowName=FLOW_ID)
 
 # Confirm state
 print("State:", check["properties"]["state"])  # Should be "Started"
+# If state is "Stopped", use set_live_flow_state — NOT update_live_flow
+# mcp("set_live_flow_state", environmentName=ENV, flowName=FLOW_ID, state="Started")
 
 # Confirm the action we added is there
 acts = check["properties"]["definition"]["actions"]
@@ -294,38 +305,45 @@ print("Actions:", list(acts.keys()))
 > flow will do and wait for explicit approval before calling `trigger_live_flow`
 > or `resubmit_live_flow_run`.
 
-### Updated flows (have prior runs)
+### Updated flows (have prior runs) — ANY trigger type
 
-The fastest path — resubmit the most recent run:
+> **Use `resubmit_live_flow_run` first.** It works for EVERY trigger type —
+> Recurrence, SharePoint, connector webhooks, Button, and HTTP. It replays
+> the original trigger payload. Do NOT ask the user to manually trigger the
+> flow or wait for the next scheduled run.
 
 ```python
 runs = mcp("get_live_flow_runs", environmentName=ENV, flowName=FLOW_ID, top=1)
 if runs:
+    # Works for Recurrence, SharePoint, connector triggers — not just HTTP
     result = mcp("resubmit_live_flow_run",
         environmentName=ENV, flowName=FLOW_ID, runName=runs[0]["name"])
-    print(result)
+    print(result)   # {"resubmitted": true, "triggerName": "..."}
 ```
 
-### Flows already using an HTTP trigger
+### HTTP-triggered flows — custom test payload
 
-Fire directly with a test payload:
+Only use `trigger_live_flow` when you need to send a **different** payload
+than the original run. For verifying a fix, `resubmit_live_flow_run` is
+better because it uses the exact data that caused the failure.
 
 ```python
 schema = mcp("get_live_flow_http_schema",
     environmentName=ENV, flowName=FLOW_ID)
-print("Expected body:", schema.get("triggerSchema"))
+print("Expected body:", schema.get("requestSchema"))
 
 result = mcp("trigger_live_flow",
     environmentName=ENV, flowName=FLOW_ID,
     body={"name": "Test", "value": 1})
-print(f"Status: {result['status']}")
+print(f"Status: {result['responseStatus']}")
 ```
 
 ### Brand-new non-HTTP flows (Recurrence, connector triggers, etc.)
 
-A brand-new Recurrence or connector-triggered flow has no runs to resubmit
-and no HTTP endpoint to call. **Deploy with a temporary HTTP trigger first,
-test the actions, then swap to the production trigger.**
+A brand-new Recurrence or connector-triggered flow has **no prior runs** to
+resubmit and no HTTP endpoint to call. This is the ONLY scenario where you
+need the temporary HTTP trigger approach below. **Deploy with a temporary
+HTTP trigger first, test the actions, then swap to the production trigger.**
 
 #### 7a — Save the real trigger, deploy with a temporary HTTP trigger
 
@@ -428,7 +446,7 @@ else:
 | `union(old_data, new_data)` | Old values override new (first-wins) | Use `union(new_data, old_data)` |
 | `split()` on potentially-null string | `InvalidTemplate` crash | Wrap with `coalesce(field, '')` |
 | 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 | Check connection auth; re-enable |
+| 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) |
 
 ### Teams `PostMessageToConversation` — Recipient Formats
@@ -456,5 +474,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` — Core connection setup and tool reference
+- `power-automate-debug` — Debug failing flows after deployment