Power Automate Run Forensics
>
Install
$ agentstack add skill-wals-pro-claude-power-automate-power-automate-run-forensics ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo 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.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-wals-pro-claude-power-automate-power-automate-run-forensics) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →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 --profileand
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.mdfor 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.