agentsclimarketplace

Diagnose flow

Skill microsoft/power-platform-skills/plugins/power-automate/skills/diagnose-flow

A plugin marketplace for Claude Code/GitHub Copilot that provides Power Platform development plugins, including reusable skills, agents, and commands for building and deploying solutions.

Install
npx -y skills add microsoft/power-platform-skills --skill diagnose-flow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

4.1 KB, as published. Nobody here has run it

Deep Flow Diagnostic Agent

You are an autonomous diagnostic agent. Given environment, flow, and run IDs, perform a comprehensive failure analysis.

Input

Parse $ARGUMENTS for: environment ID, flow ID, run ID.

Tools

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 MCP tools aren't available, run /setup to wire the FlowAgent MCP server.

Workflow

  1. 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 status
    • get_run_actions for the full action-level execution trace
    • get_flow for definition context
    • For a failed loop, get_run_action_repetitions on an action inside the loop (the container returns none) to find the failing iteration

  2. Build execution graph: Map each action's runAfter dependencies. Identify parallel branches.

  3. Identify failed actions: Filter for status != Succeeded. Classify each as:

    • Root failure: dependencies all Succeeded but this action failed
    • Cascading skip: skipped because a dependency failed

  4. Analyze each root failure against common patterns:

    • Authorization/Connection errors
    • Expression evaluation failures
    • HTTP 4xx/5xx from external services
    • Timeout errors
    • Parameter validation failures (empty required fields, wrong enum values)
    • Action type mismatches (OpenApiConnection vs OpenApiConnectionWebhook)

  5. Cross-reference with definition: Check if the action's parameters, connection references, or expressions have issues visible in the definition.

  6. Write diagnosis report with:

    • Execution timeline
    • Root cause identification
    • Specific fix with code changes
    • Confidence level (high/medium/low)

  7. 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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.