agentsclimarketplace
Sign in

Power automate run forensics

Skill Wals-pro/claude-power-automate/skills/power-automate-run-forensics

Diagnose Microsoft Power Automate cloud-flow incidents from run history, failed actions, trigger behavior, connection failures, missing runs, skipped branches, invalid expressions, throttling, retries, and action outputs before changing workflow code. Use with the power-automate CLI runs and run-detail commands for read-only evidence gathering.From its SKILL.md

Install
npx -y skills add Wals-pro/claude-power-automate --skill power-automate-run-forensics

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

2 things to look at

  • 10 stars10 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
  • runs commandsInstructs the agent to run 6 commands, including `power-automate status --profile <profile>` and 5 more.

SKILL.md

1.5 KB, 269 tokens by cl100k_base, as published. Nobody here has run it

Power Automate Run Forensics

Start read-only. Confirm what the flow actually did before changing JSON, connections, or production records.

Procedure

  1. Define boundary: profile, environment ID, flow ID/name, run ID(s), object IDs, and absolute time window.
  2. Run power-automate status --profile <profile> and power-automate runs --profile <profile> when API access is available.
  3. If the flow or environment is unknown, run power-automate environments, power-automate flows, or power-automate runs --all-environments --top <n> to discover what the signed-in Azure user can see.
  4. For a failed or suspicious run, inspect power-automate run-detail.
  5. Compare trigger data, action inputs, action outputs, branch status, skipped actions, and connector error codes.
  6. Read references/errors-limits.md for Microsoft error/limit guidance.
  7. Produce findings before proposing edits.

Output

Report:

  • Boundary checked.
  • Evidence reviewed.
  • Findings with run IDs and timestamps.
  • Impact.
  • Root cause or strongest hypothesis.
  • Fix target and validation plan.

If evidence is missing, name the missing source and why it matters.

What ships with it: 1 file

2.3 KB alongside SKILL.md

references/

Keep looking

Skills are one crate of 325,949. 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.