Payment Rails
v1.0.2Payment Rails integration. Manage data, records, and automate workflows. Use when the user wants to interact with Payment Rails data.
⭐ 0· 92·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
medium confidencePurpose & Capability
The name/description say this integrates with Payment Rails and all runtime instructions use the Membrane CLI to connect, run actions, and proxy API requests — these requirements are coherent with the stated purpose.
Instruction Scope
SKILL.md stays on-topic (install Membrane CLI, login via browser, create/inspect connections, run actions, proxy requests). It instructs sending requests to Payment Rails via Membrane (expected). One minor inconsistency: the 'Official docs' link points to rapyd.net (a different payments provider), which looks like a copy/paste error and should be verified.
Install Mechanism
The registry contains no automated install spec (instruction-only). The document recommends installing @membranehq/cli globally with npm (-g), which is a normal but higher-impact action than a pure instruction-only skill; prefer npx or audit the package before global install.
Credentials
No environment variables or credentials are requested by the skill. The instructions explicitly state Membrane manages auth server-side and advise against asking users for API keys — this is proportionate.
Persistence & Privilege
Skill is not always-enabled and does not request elevated/persistent system privileges or config changes. It relies on ephemeral CLI usage and browser-based auth flows.
Assessment
This skill appears to be what it says: a set of instructions for using the Membrane CLI to interact with Payment Rails. Before installing or running anything: (1) verify the @membranehq/cli package on the npm registry (review maintainers, versions, and recent activity) or use npx to avoid a global install; (2) confirm the Membrane homepage and GitHub repository links and that they match the CLI package; (3) note the SKILL.md's 'Official docs' link to rapyd.net — verify the correct Payment Rails/Trolley API docs if you need to make direct API calls; (4) be aware that Membrane will proxy requests and therefore will transmit the data you send to Membrane and Payment Rails — do not include secrets or unrelated sensitive data in requests. If you want higher assurance, ask the skill author for the exact npm package URL and a pointer to the Membrane CLI source code or npm package page to inspect before running installs.Like a lobster shell, security has layers — review code before you run it.
latestvk9794dn1xt0jxsk8hzxf7v4ard8430p8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.