Processout
v1.0.0ProcessOut integration. Manage data, records, and automate workflows. Use when the user wants to interact with ProcessOut data.
⭐ 0· 50·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
Capability signals
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
medium confidencePurpose & Capability
The name and description (ProcessOut integration) match the runtime instructions: the SKILL.md shows how to use the Membrane CLI to discover actions, create a connection, run actions, and proxy requests to ProcessOut. One small inconsistency: the registry metadata lists no required binaries, but the instructions require the 'membrane' CLI (installed via npm). This is explainable (instruction-only skill) but worth noting.
Instruction Scope
Instructions stay on-topic (install Membrane CLI, login, connect to ProcessOut, list/run actions, proxy requests). They do not ask the agent to read unrelated files or environment variables. Important privacy/security note: the guidance explicitly routes API calls and authentication through Membrane, meaning request payloads and ProcessOut credentials are proxied through Membrane's infrastructure—this is expected for this integration but is a material behavioral detail users should be aware of.
Install Mechanism
There is no formal install spec in the registry, but SKILL.md instructs running 'npm install -g @membranehq/cli' (or using npx in examples). Installing a global npm CLI is a moderate-risk action because it runs third-party code on the machine; however, the package is from the npm ecosystem and the instructions point to getmembrane.com and a GitHub repository, which is typical for a CLI integration.
Credentials
The skill declares no required environment variables or secrets and explicitly tells integrators not to ask the user for API keys (Membrane handles credentials). This is proportionate to the stated purpose. Caveat: relying on Membrane means credentials are managed server-side by a third party and proxied requests may contain sensitive payment data.
Persistence & Privilege
The skill does not request permanent 'always' presence and uses default invocation behavior. It does not request access to other skills' configs or system-wide settings.
Assessment
This skill is coherent for ProcessOut work, but before installing: 1) Understand that you will install a third‑party npm CLI (@membranehq/cli). Installing global npm packages runs code on your machine—inspect the package, prefer using npx or a local install if you want to avoid a global binary. 2) Using the skill routes API calls and credentials through Membrane's servers: confirm you trust getmembrane.com and review its privacy/security policies, especially for payment data. 3) The registry metadata did not declare the required 'membrane' binary even though the instructions require it—ensure you follow SKILL.md carefully. 4) For production or sensitive data, consider testing in a sandbox and verify the CLI/package authenticity (check the GitHub repo, npm package publisher, and package version) before granting access or sending real transactions.Like a lobster shell, security has layers — review code before you run it.
latestvk973294h6evw4z6hhazjfsref184aea9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.