Bridgepay Network Solutions
v1.0.0BridgePay Network Solutions integration. Manage data, records, and automate workflows. Use when the user wants to interact with BridgePay Network Solutions d...
⭐ 0· 92·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
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (BridgePay integration) match the instructions: they tell the user to install and use the Membrane CLI to connect to BridgePay and run actions. Required capabilities (network access, a Membrane account, and the Membrane CLI) are proportional and expected for this integration.
Instruction Scope
SKILL.md contains only concrete CLI steps: install Membrane CLI, login (browser flow or headless code), list/connect connections, run actions, and proxy requests. It does not instruct the agent to read unrelated local files, harvest environment variables, or call external endpoints other than Membrane/BridgePay documentation URLs. The guidance to avoid asking users for BridgePay API keys is appropriate and contained.
Install Mechanism
There is no formal install spec in the skill bundle (lowest static risk), but the doc recommends installing @membranehq/cli via npm (npm install -g or npx). Installing packages from the public npm registry is a normal pattern here but carries the usual supply-chain/trust considerations — verify the package source and publisher before installing global CLI tooling.
Credentials
The skill declares no required environment variables or local config paths. It relies on Membrane to manage BridgePay credentials server-side, which is coherent with the stated purpose. Note: delegating credentials to Membrane is a trust decision for the user/organization, but it is proportionate to the integration's needs.
Persistence & Privilege
The skill is not always-included and does not request special system persistence or modify other skills. It is user-invocable and can be invoked autonomously (platform default) but there are no additional privilege escalations or self-enabling behaviors in the instructions.
Assessment
This skill is instruction-only and appears coherent: it tells you to use Membrane's CLI to connect to BridgePay rather than embedding keys. Before installing or using it, verify the @membranehq/cli npm package (author, download counts, repository) and confirm you trust Membrane to manage your BridgePay credentials (they will be stored/used server-side). Prefer npx if you don't want a global install. During the browser auth flow, review the permissions requested for the connector. In corporate contexts, confirm this delegation meets compliance requirements. The skill itself does not ask for local secrets or read files.Like a lobster shell, security has layers — review code before you run it.
latestvk97ctj5h6pq25me307a2r0kpvn84gda9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.