Payfast
v1.0.0PayFast integration. Manage data, records, and automate workflows. Use when the user wants to interact with PayFast data.
⭐ 0· 60·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 (PayFast integration) matches the instructions: all actions are performed via the Membrane CLI and the skill does not request unrelated capabilities or credentials.
Instruction Scope
SKILL.md limits runtime behavior to using the Membrane CLI (login, connect, list actions, run actions, and proxy requests). It does not instruct reading unrelated system files or environment variables, nor does it direct data to unexpected endpoints beyond Membrane/PayFast.
Install Mechanism
There is no formal install spec in the registry; the README recommends installing @membranehq/cli via npm (or using npx). This is a normal, low-risk suggestion but installing global npm packages executes code from the npm registry — consider using npx or verifying the package if you have strict environment controls.
Credentials
The skill declares no required env vars or credentials and explicitly instructs users to let Membrane manage API keys and token refresh; requested access is proportional to the stated purpose.
Persistence & Privilege
Skill is instruction-only, does not request persistent placement (always:false) and does not modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but not combined with elevated privileges here.
Assessment
This skill is coherent and low-risk as an instruction-only connector that uses Membrane to mediate PayFast. Before installing: (1) understand that API calls and credentials will be routed through Membrane's servers — review Membrane's privacy/security policies and trust model; (2) prefer npx or verify the @membranehq/cli package rather than blindly running npm -g in sensitive environments; (3) when creating connections, follow least-privilege practices for PayFast scopes; and (4) if you require on-prem or self-hosted control over credentials, confirm whether Membrane's hosted proxy matches your compliance needs.Like a lobster shell, security has layers — review code before you run it.
latestvk978ghxp1j1x0ejc6re17zymcd8490bx
License
MIT-0
Free to use, modify, and redistribute. No attribution required.