plugins/power-automate/skills/diagnose-flow/SKILL.md
Deep autonomous diagnosis of a failed flow run. Provide environment, flow, and run IDs. Use when the user asks to diagnose or deeply investigate a specific failed flow run.
npx skillsauth add microsoft/power-platform-skills diagnose-flowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
You are an autonomous diagnostic agent. Given environment, flow, and run IDs, perform a comprehensive failure analysis.
Parse $ARGUMENTS for: environment ID, flow ID, run ID.
This skill uses the FlowAgent MCP tools, referred to by bare name (clients
surface them as mcp__flowagent__<tool> in Claude Code or flowagent-<tool> in
Copilot CLI). If no MCP tools are present, the plugin is not wired up — run the setup skill.
Triage with diagnose_run, then gather full context in parallel:
diagnose_run — classified failed/timed-out actions with a remediation each (start here)get_run_details for overall run statusget_run_actions for the full action-level execution traceget_flow for definition contextget_run_action_repetitions on an action inside the loop (the container returns none) to find the failing iterationBuild execution graph: Map each action's runAfter dependencies. Identify parallel branches.
Identify failed actions: Filter for status != Succeeded. Classify each as:
Analyze each root failure against common patterns:
Cross-reference with definition: Check if the action's parameters, connection references, or expressions have issues visible in the definition.
Write diagnosis report with:
Optionally generate fixed definition: If the fix is a definition change, apply it with edit_flow (surgical, one action/parameter) — fall back to update_flow only for large rewrites.
development
(Preview) Builds and edits a model-driven Power Apps app from a natural-language intent — tables, columns, relationships, adaptive forms with sub-grids, views, Choice-column charts, generative page intents for overview/dashboard surfaces (page `.tsx` generated in generate-pages after plan approval), and an app module + sitemap — via the headless cds-maker-sdk. Runs an interactive, multi-turn authoring flow (env selection, jobs-to-be-done first, then design-only App Spec authoring across confirmed levels, guardrail lint, plan-mode approval, generate-pages, full build) and a narrated build, and can download a deployed app back into an editable spec to change it. Use when the user says "build an app for X", "create a model-driven app", "make me an app to manage Y", or "edit/add to my app". This skill stands alone and does not require /genpage — but for a standalone generative page added to an app that already exists, use /genpage instead.
data-ai
Use when the user wants to enable offline mode for a Power Apps mobile app and create a Mobile Offline Profile in Dataverse — designs per-table row scope, relationships, columns, and sync frequency through a 3-gate approval flow.
data-ai
Use when the user wants to design or redesign the Dataverse schema and connector plan for an existing mobile app, or has an ER diagram (image, Mermaid, or text) to apply. Skip when the user is creating a brand-new app — /create-mobile-app handles the data model inline.
tools
Use when the user wants to report a bug, file an issue, submit a bug report, or report any problem with the mobile-app plugin.