Securionpay
v1.0.0SecurionPay integration. Manage data, records, and automate workflows. Use when the user wants to interact with SecurionPay data.
⭐ 0· 46·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
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
Name/description (SecurionPay integration) align with the instructions: the SKILL.md shows how to use the Membrane CLI to connect to SecurionPay, list actions, run actions, and proxy API requests. Required capabilities (network + Membrane account) are appropriate for the stated goal.
Instruction Scope
All runtime instructions are limited to installing/using the Membrane CLI, performing a Membrane login flow, creating connections, listing actions, running actions, and proxying requests through Membrane. The instructions do not ask the agent to read unrelated files, access unrelated environment variables, or send data to endpoints outside Membrane/SecurionPay.
Install Mechanism
This is instruction-only (no install spec), but the SKILL.md directs installing @membranehq/cli globally via npm (npm install -g). Installing a global npm package is a common step for CLI tools but does write code to disk and runs code from the npm registry — a moderate-risk action that is nevertheless expected for this integration.
Credentials
The skill declares no required environment variables or credentials. SKILL.md explicitly directs users to create a Membrane connection rather than providing API keys locally, which is proportionate for a service that delegates auth to Membrane.
Persistence & Privilege
The skill does not request always:true or any special persistent privileges. It is user-invocable and relies on the Membrane CLI; there is no evidence it attempts to modify other skills or system-wide settings.
Assessment
This skill is instruction-only and appears to be what it claims: a Membrane-backed SecurionPay integration. Before installing or using it, verify you trust Membrane (@membranehq) and the npm package: check the package and repository on npm/GitHub, confirm the package name and publisher, and review recent package versions/maintainer activity. Installing a global npm CLI will put third-party code on your system — install only if you trust the source. Also be aware that using Membrane's proxy hands SecurionPay requests and credentials to Membrane's service, so you should be comfortable with Membrane handling auth and request data. If you need on-premises control of secrets or do not want a third party to proxy payment data, do not use this skill.Like a lobster shell, security has layers — review code before you run it.
latestvk978rdgqfwrxq4reb715hmd86n84d97j
License
MIT-0
Free to use, modify, and redistribute. No attribution required.