Rapyd
v1.0.0Rapyd integration. Manage data, records, and automate workflows. Use when the user wants to interact with Rapyd data.
⭐ 0· 52·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
medium confidencePurpose & Capability
Name/description (Rapyd integration) match the instructions: the SKILL.md consistently directs the agent/operator to use the Membrane CLI to connect to Rapyd and run actions or proxied API requests.
Instruction Scope
Runtime instructions stay on‑topic: they describe installing/using the Membrane CLI, performing browser‑based login, creating connections, listing actions, running actions, and proxying Rapyd requests. There are no directives to read unrelated system files, environment variables, or to exfiltrate data to unexpected endpoints.
Install Mechanism
The skill is instruction‑only (no install spec), but SKILL.md tells users to install @membranehq/cli from npm (global install or via npx). Installing a third‑party CLI from npm is a reasonable way to achieve the stated purpose, but it carries typical supply‑chain risks — review the package and prefer npx or ephemeral installs if you want to avoid persistent global binaries.
Credentials
No environment variables, credentials, or config paths are requested by the skill. Auth is handled via Membrane's browser flow (server‑side), which aligns with the guidance in the doc to avoid asking users for API keys.
Persistence & Privilege
Skill does not request elevated or persistent platform privileges; always:false and normal autonomous invocation settings. The SKILL.md does not instruct modifying other skills or system‑wide agent settings.
Assessment
This skill appears to do what it says: it uses Membrane to talk to Rapyd and intentionally avoids asking for Rapyd API keys. Before installing/using the CLI, review the @membranehq/cli package (npm page and source repo) because the SKILL.md asks you to install/run third‑party code. If you want lower persistence, use npx @membranehq/cli@latest instead of a global npm install. Use the browser login flow on a trusted machine, and avoid pasting sensitive data into command arguments unless you understand where it will be sent. If you need higher assurance, verify the Membrane project and its privacy/security docs or test in an isolated environment first.Like a lobster shell, security has layers — review code before you run it.
latestvk97726engc7dq3vaj5r40tpb3n84fnpb
License
MIT-0
Free to use, modify, and redistribute. No attribution required.