microsoft/power-platform-skills is a plugin marketplace containing reusable skills, agents, and commands for developing with Microsoft Power Platform. Developers use it to build and deploy Power Pages sites, model-driven Power Apps, and related solutions through Claude Code or GitHub Copilot. The catalogue entries are the marketplace's included skills, agents, plugins, and other agent components.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add microsoft/power-platform-skills --skill debug-flowgit clone --depth 1 https://github.com/microsoft/power-platform-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/microsoft/power-platform-skills/debug-flow)<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/debug-flow"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/debug-flow/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/microsoft/power-platform-skills/debug-flow"><img src="https://agentmods.dev/badge/skills/microsoft/power-platform-skills/debug-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 7 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00030 | $0.01821 |
| Opus 5.5 | $0.00012 | $0.00728 |
| Sonnet 5.5 | $0.00006 | $0.00364 |
| Haiku 4.5 | $0.00003 | $0.00182 |
Grade A, and why
debug-flow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug a Failed Flow Run
You are helping the user debug a failed Power Automate flow run.
Tools
This skill uses the FlowAgent MCP tools. Clients surface them with a
client-specific prefix — mcp__flowagent__<tool> (Claude Code) or
flowagent-<tool> (Copilot CLI) — so they're referred to by bare name below
(e.g. get_run_actions). Use CLI shell commands (local engine build only) for
CLI-only operations or when no MCP tools are present.
| Tool | Purpose |
|---|---|
list_flows |
Find flows by name (use name param for search) |
get_run_history |
Get recent runs for a flow |
diagnose_run |
One-shot: classify failed actions with remediations |
get_run_details |
Get details for a specific run |
get_run_actions |
Get action-level execution trace |
get_run_action_content |
Retrieve bounded recorded inputs or outputs for one action |
get_run_action_repetitions |
Iteration-level detail for a loop (which iteration failed — pass an action inside the loop) |
get_flow |
Get flow definition for context |
get_operation_details |
Confirm the correct action type / parameters |
edit_flow |
Apply a surgical fix to one action/parameter |
update_flow |
Replace the whole definition (large rewrites) |
run_flow |
Re-run after fix (use wait: true to see result) |
resubmit_run / cancel_run |
Resubmit a fixed run / cancel a stuck one |
Steps
-
Identify the flow and run
- Parse
$ARGUMENTSfor flow ID and optional run ID. - If no flow ID, call
list_flowswithnameparam to search. Ask user to pick if ambiguous. - If no run ID, call
get_run_historyand find the most recent failed run. - Present recent runs in a table: Run ID | Status | Start Time | Error
- Parse
-
Fast triage with
diagnose_run- Call
diagnose_runfor the run — it returns the failed/timed-out actions already classified with a remediation each. Use this as the starting point. - For deeper analysis, also fetch (in parallel):
get_run_actions(full trace) andget_flow(definition context). For a failed loop, callget_run_action_repetitionson an action inside the loop to find the failing iteration. - Repetition results are
{ action, count, truncated, repetitions };countis the returned count, not the total. Iftruncatedis true, do not infer absence from the returned subset. - When recorded payloads are needed, use
get_run_actionswithincludeSizes: true, thenget_run_action_contentwith the action name andwhich: "inputs"or"outputs". The default download cap is 256000 bytes; an oversized result is reported rather than dumped. Retrieve only what the diagnosis needs and avoid reproducing sensitive payloads in the report.
- Call
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago Changed · +3 lines a177f4eaffc4
- 27d ago Changed d9b684ebfd7c
- 1mo ago First seen · 87 lines · 30 tokens per session scan A 9efd940201df
debug-flow is a skill published in the GitHub repository microsoft/power-platform-skills (1,025 stars, last pushed today), licensed MIT. It adds 30 tokens to every session and 1,821 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
canvas-apps-ui-gen
Generates paste-ready Power Apps Canvas App YAML. Invoke when the user wants to replicate a UI mockup, improve an existing Canvas app screen, or build a new screen from a text description. Also invoke when the user asks to "improve", "redesign", or "generate YAML" for a Canvas app screen.
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
investigate
Find the root cause of Elixir/Phoenix bugs — crashes, exceptions, stack traces, compile errors, LiveView that won't update, silent failures. Use when something is broken or misbehaves. --parallel for 4 tracks.
narrow-bare-rescue
Narrow bare rescue in Elixir so real errors like KeyError and typos propagate instead of being swallowed. Use to audit rescues and refactor error handling.
perf
Use when anything in a Phoenix app is slow, times out, or uses too much memory, even if the cause looks obvious. Load it before analyzing or fixing: it runs measured Ecto, LiveView and OTP checks and ranks fixes.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.