Agent skill · data analytics · github
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
Why this skill is useful
Provides specific diagnostic patterns and API commands for troubleshooting Power Automate flows that the AI wouldn't reliably generate on its own.
What it needs
Requires flowstudio account access. About 10k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Power Automate Debugging with FlowStudio MCP A step-by-step diagnostic process for investigating failing Power Automate cloud flows through the FlowStudio MCP server. Real debugging examples: Expression error in child flow Data entry, not a flow bug Null value crashes child flow Prerequisite: A FlowStudio MCP server must be reachable with a valid JWT. See the flowstudio-power-automate-mcp skill for connection setup. Subscribe at https://mcp.flowstudio.app --- Source of Truth Always call listskills / toolsearch first to confirm available tool names and parameter schemas. Tool names and parameters may change between server versions. This skill covers response shapes, behavioral notes, and diagnostic patterns — things tool schemas cannot tell you. If this document disagrees with toolsearch or a real API response, the API wins. --- Python Helper --- Step 1 — Locate the Flow --- Step 2 — Find the Failing Run --- Step 3 — Get the Top-Level Error CRITICAL: getliveflowrunerror tells you which action failed. getliveflowrunactionoutputs tells you why. You must call BOTH. Never stop at the error alone — error codes like ActionFailed, NotSpecified, and InternalServerError are generic wrappers. The actual root cause (wrong field, null value, HTTP 500 body, stack trace) is only visible in the action's inputs and outputs. --- Step 4 — Inspect the Failing Action's Inputs and Outputs This is the most important step. getliveflowrunerror only gives you a generic error code. The actual error detail — HTTP status codes, response bodies, stack traces, null values — lives in the action's runtime inputs and outputs. Always inspect the failing action immediately after identifying it. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/flowstudio-power-automate-debug