What problem does it solve? Editing Power Automate cloud flows through the maker portal designer is unreliable — the expression editor silently discards hand-typed references, and the flow definition is a JSON string inside a JSON column with no version history, so a bad write is unrecoverable. This Skill provides a safe API-based workflow with enforced snapshots and validation before every write. ## Core Features & Use Cases - Snapshot-before-write enforcement: pa.py writes a timestamped rollback copy of the live definition before every PATCH, since clientdata has no version history. - Structural validation: Detects orphaned trigger-schema required entries at every nesting level, Terminate actions nested inside Apply to each loops, unresolved host.connectionName references, and broken runAfter links — refusing to PATCH until fixed. - Authentication guidance: Documents the exact token audience and scope derivation for Dataverse, BAP, Flow, and PowerApps endpoints, including device-code login, public client IDs, and SharePoint REST restrictions. - Use Case: You need to remove a dynamically-added trigger input from a solution-aware flow. Run pa.py get to snapshot, edit the parsed definition, run pa.py validate to confirm both properties and required are consistent, then pa.py patch to write it back with a rollback command printed. ## Quick Start Ask the assistant to read a Power Automate flow by its GUID from your Dataverse org, snapshot its definition, and validate it before making any edits.
