Brightpay Uk
v1.0.2BrightPay UK integration. Manage data, records, and automate workflows. Use when the user wants to interact with BrightPay UK data.
⭐ 0· 70·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
The name/description (BrightPay UK integration) matches the instructions (use Membrane CLI to create a connection, list actions, run actions, and proxy requests). Minor inconsistency: the skill registry lists an unknown source, while SKILL.md includes a GitHub repository URL and a homepage (getmembrane.com); this is not fatal but worth verifying the publisher.
Instruction Scope
SKILL.md confines the agent to installing/using the Membrane CLI, performing login, creating connections, listing/running actions, and proxying API requests through Membrane. It does not instruct reading arbitrary local files, environment variables, or exfiltrating data outside Membrane. It does require network access and interactive browser auth for login, which is expected for this integration.
Install Mechanism
No registry-level install spec exists (skill is instruction-only). The doc tells the user to run 'npm install -g @membranehq/cli' (or npx). Installing a public npm CLI is a reasonable approach, but global npm packages can run install scripts — verify the package on npmjs/GitHub before installing or prefer 'npx' to avoid a global install.
Credentials
The skill declares no required env vars or secrets and explicitly instructs not to ask users for API keys, delegating auth to Membrane. That is proportionate: Membrane is expected to handle credentials for the BrightPay connector.
Persistence & Privilege
The skill is not always-enabled and does not request elevated or persistent system privileges. It will allow autonomous invocation (the platform default) but does not attempt to modify other skills or system-wide settings.
Assessment
This skill appears coherent, but before installing or running the CLI: 1) Verify the @membranehq/cli package and its GitHub repo (check publisher, recent activity, and npm page) rather than trusting an unknown registry source. 2) Prefer using 'npx @membranehq/cli@latest' if you don't want a global install. 3) Understand that signing into Membrane grants that service access to BrightPay data — review Membrane's privacy/permissions and revoke connections when no longer needed. 4) Do not paste BrightPay credentials into unrelated prompts; follow the documented connection flow so credentials are handled by Membrane.Like a lobster shell, security has layers — review code before you run it.
latestvk97fkbam2vrdmz6jyhqy9mw4vs8427fe
License
MIT-0
Free to use, modify, and redistribute. No attribution required.