Salt Edge
v1.0.0Salt Edge integration. Manage data, records, and automate workflows. Use when the user wants to interact with Salt Edge data.
⭐ 0· 73·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description: Salt Edge integration. The SKILL.md exclusively uses the Membrane CLI to discover connectors, create connections, run actions, and proxy Salt Edge API calls. No unrelated credentials, binaries, or config paths are requested; the need for a Membrane account and network access is explicitly stated and appropriate.
Instruction Scope
Instructions are limited to installing and using the @membranehq/cli, performing OAuth login, discovering connectors/actions, running actions, and proxying API requests through Membrane. The document does not instruct reading unrelated files, accessing other credentials, or exfiltrating data outside the Membrane/Salt Edge flow.
Install Mechanism
There is no formal install spec in metadata, but SKILL.md directs users to run `npm install -g @membranehq/cli`. Installing a global npm package is a standard approach for CLIs but does download and execute third-party code from the npm registry; verify package provenance and trust the @membranehq package before installing globally.
Credentials
The skill requests no environment variables or local config paths; authentication is delegated to Membrane (OAuth/browser flows). This is proportionate for a connector integration and avoids asking for direct API keys or secrets.
Persistence & Privilege
Skill is not forced-always and is user-invocable; model invocation is permitted (the platform default). The skill does not request persistent system-wide privileges or modify other skills. Note: as with any CLI-based integration, the installed Membrane CLI will persist on the host until uninstalled.
Assessment
This SKILL.md is coherent for a Salt Edge integration via Membrane, but before installing: 1) verify the @membranehq/cli package identity on npm/GitHub and confirm you trust Membrane; 2) prefer installing the CLI in a controlled environment (container or user scope) rather than system-wide if you are cautious about global npm packages; 3) expect OAuth browser-based login (or copy/paste flow for headless environments); 4) no local secrets are requested by the skill itself, but using the CLI will grant it the ability to access and proxy Salt Edge data for any connections you create—ensure you trust the Membrane service and the account you authenticate with.Like a lobster shell, security has layers — review code before you run it.
latestvk97avtzvpxwxkfmtzd6yv82frn844nvz
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
