Safepay
v1.0.2Safepay integration. Manage data, records, and automate workflows. Use when the user wants to interact with Safepay data.
⭐ 0· 82·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’s name/description (Safepay integration) matches the instructions: it uses Membrane as a proxy/connector to talk to Safepay. No unrelated credentials or tools are requested.
Instruction Scope
SKILL.md only instructs the agent to install/use the Membrane CLI, create/inspect connections, list actions, run actions, or proxy requests to Safepay via Membrane. It does not instruct reading unrelated files, harvesting local secrets, or sending data to unexpected endpoints.
Install Mechanism
There is no install spec embedded in the skill bundle. The instructions recommend installing @membranehq/cli via npm (a standard public package). This is proportionate to the described functionality.
Credentials
The skill declares no required environment variables or credentials. It explicitly relies on Membrane to manage authentication and instructs users to create a connection via browser-based login, which is consistent with its purpose.
Persistence & Privilege
always:false and default invocation settings are used. The skill does not request persistent system privileges or modify other skills' configs.
Assessment
This skill is instruction-only and delegates Safepay access to the Membrane service/CLI. Before installing or using it: (1) verify you trust Membrane as a proxy (it will hold and refresh Safepay credentials on your behalf and will see proxied API traffic); (2) installing the recommended CLI uses npm -g which may require admin rights — prefer using npx or a scoped install if you want to avoid global installs; (3) the workflow requires interactive browser authentication (or a headless URL/code flow) — do not paste secrets into chat; (4) you may review the Membrane CLI package and the referenced GitHub repo/homepage directly to confirm they match your security and privacy requirements.Like a lobster shell, security has layers — review code before you run it.
latestvk979bm41fpm59r2kdqg42bzj1d843hek
License
MIT-0
Free to use, modify, and redistribute. No attribution required.