When a Power Automate flow fails, the Graph API gives you a generic error code like ActionFailed or NotSpecified, which tells you almost nothing. This skill walks Claude through the FlowStudio MCP server's debugging workflow: list flows, pull the failed run, identify which action broke, then inspect that action's actual inputs and outputs to see the HTTP response body, expression error, or null value that caused the failure. The Python helpers and step-by-step examples make it clear you need both the error endpoint and the outputs endpoint because the root cause lives in the runtime data, not the top-level status. If you're tired of guessing why a flow died at 3am, this is the systematic approach you want.
npx -y skills add github/awesome-copilot --skill flowstudio-power-automate-debug --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
github/awesome-copilot
alirezarezvani/claude-skills
microsoft/win-dev-skills
github/awesome-copilot