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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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 iteration{ action, count, truncated, repetitions }; count is the returned count, not the total. Treat truncated: true as incomplete evidence.get_run_actions with includeSizes: true, then get_run_action_content for one action with which: "inputs" or "outputs". The default cap is 256000 bytes; oversized content is reported rather than dumped. Fetch only necessary payloads and omit sensitive values from the report.Build 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.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Activates and provisions a Power Pages website in a Power Platform environment via the Power Platform REST API. Use when the user wants to activate, provision, turn on, or enable a Power Pages website or portal.
The English summary is being prepared. Showing the original description.
Integrates Power Pages generative-AI summarization APIs (PREVIEW) into a Single Page Application (SPA) site — the Search Summary API and the Data Summarization API — on any record-detail or list page. Generates per-target service code (CSRF-handled) and AI site settings; delegates Web API settings, table permissions, and web roles to `/integrate-webapi` and `/create-webroles`. Use whenever a user wants AI/Copilot output that condenses Dataverse content on a Power Pages site — an AI summary, AI-generated overview or "key insights" across a record or list, a search-results summary, a case/incident summary, or recommendation-chip refinement — even when phrased as "AI-generated paragraph", "insights", or "overview". Do NOT use for: generative pages in model-driven apps (use the model-apps `genpage` skill), Copilot Studio agents/chatbots, summarizing documents or PDFs, Power BI dashboards, plain keyword search with no AI summary, or plain Dataverse CRUD (use `/integrate-webapi`).
The English summary is being prepared. Showing the original description.
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
The English summary is being prepared. Showing the original description.
Internal implementation skill invoked by /add-native for camera, image picker, barcode scanner, QR scanner, and camera/gallery Dataverse artifact workflows.
The English summary is being prepared. Showing the original description.
Integrates Power Automate cloud flows into a Power Pages site. Lists available flows, suggests relevant ones based on intent, identifies scenarios and web roles, creates metadata files, and generates client-side code to call flows. Handles both new flow registration and adding already-registered flows to additional pages without re-creating metadata. Use when the user wants to add, connect, register, or link a Power Automate cloud flow to their site.
The English summary is being prepared. Showing the original description.
Use when adding a Power Platform connector to an Expo/React Native Power Apps mobile app and no dedicated mobile connector skill exists.
The English summary is being prepared. Showing the original description.