Sign in Publish

MCP servers Skills Toolkits Why AgentStack Sell Docs

SKILL verified MIT Self-run

Power Automate Run Forensics

skill-wals-pro-claude-power-automate-power-automate-run-forensics · by Wals-pro

>

— No reviews yet

0 installs

9 views

0.0% view→install

Install

$ agentstack add skill-wals-pro-claude-power-automate-power-automate-run-forensics

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

✓ Prompt-injection patterns
✓ Secret / credential exfiltration
✓ Dangerous shell & filesystem operations
✓ Untrusted network calls
✓ Known-malicious package signatures

What it can access

✓ Network access No
✓ Filesystem access No
✓ Shell / process execution No
✓ Environment & secrets No
✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Power Automate Run Forensics? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.

Sign up to claim

About

Power Automate Run Forensics

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

Procedure

Define boundary: profile, environment ID, flow ID/name, run ID(s), object IDs,

and absolute time window.

Run power-automate status --profile and

power-automate runs --profile when API access is available.

If the flow or environment is unknown, run power-automate environments,

power-automate flows, or power-automate runs --all-environments --top to discover what the signed-in Azure user can see.

For a failed or suspicious run, inspect power-automate run-detail.
Compare trigger data, action inputs, action outputs, branch status, skipped

actions, and connector error codes.

Read references/errors-limits.md for Microsoft error/limit guidance.
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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Author: Wals-pro
Source: Wals-pro/claude-power-automate
License: MIT

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Write a review

Versions

v0.1.0 Imported from the upstream source.