Power Automate
v1.0.0Power Automate integration. Manage data, records, and automate workflows. Use when the user wants to interact with Power Automate data.
⭐ 0· 35·0 current·0 all-time
byVlad Ursul@gora050
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The skill declares Power Automate integration and all runtime instructions show use of the Membrane CLI to discover connectors, create connections, run actions, and proxy requests to Power Automate. There are no unrelated credentials, binaries, or config paths requested that would be inconsistent with this purpose.
Instruction Scope
The SKILL.md instructs the agent/user to install and run the Membrane CLI, perform browser-based login, discover actions, run actions, and use Membrane's proxy for raw API calls. This is within scope for a Power Automate integration, but it explicitly routes requests and authentication through Membrane's servers — meaning API calls and (potentially) data will transit a third-party service rather than going directly to Microsoft APIs. Users should be aware of that data flow.
Install Mechanism
There is no install spec in the registry (instruction-only), but the SKILL.md tells users to run `npm install -g @membranehq/cli` (and suggests `npx` for some commands). Global npm installation is a standard way to get a CLI but grants executable code on the host and may require elevated permissions. This is proportionate to the stated purpose but has the usual risks of installing third-party npm packages.
Credentials
The skill does not request environment variables, local config paths, or unrelated credentials. Authentication is handled via Membrane's browser-based OAuth flow and connections, which avoids local secrets but means credentials are managed server-side by Membrane (as documented). The set of requested accesses aligns with the integration role.
Persistence & Privilege
The skill is not forced-always, requires no persistent system modifications in the manifest, and relies on an external CLI invoked by the user. It does not request elevated platform privileges or system-wide config changes in the SKILL.md.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to interact with Power Automate. Before installing/using it, consider: (1) Data routing: requests and auth are proxied through Membrane's service — review Membrane's privacy/security policy and confirm you are comfortable sending the relevant data (and possibly tokens) to that third party. (2) Package trust: the SKILL.md recommends `npm install -g @membranehq/cli`; installing global npm packages runs third-party code on your machine. Verify the package on npm and the referenced GitHub repo, prefer `npx` for ad-hoc runs if you want to avoid a global install, and avoid running installs as root. (3) Org policy: if you operate in a corporate environment, get approval for third-party proxies and global installs. (4) Test first: try the workflow in a non-production account so you can validate behavior and scope of data sent through Membrane. If you need more assurance, ask the skill author for a security/privacy whitepaper or for details on what data Membrane logs/retains and where it is hosted.Like a lobster shell, security has layers — review code before you run it.
latestvk97253f5h7tar1qmx0xkcxyp9184680b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.