Rapidapi
v1.0.2RapidAPI integration. Manage data, records, and automate workflows. Use when the user wants to interact with RapidAPI data.
⭐ 0· 96·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 (RapidAPI integration) matches the SKILL.md instructions (use Membrane to connect and proxy to RapidAPI). However the registry metadata lists no required binaries while the instructions explicitly require the 'membrane' CLI (npm global). The skill should declare that binary dependency.
Instruction Scope
Runtime instructions are narrowly scoped to installing and using the Membrane CLI to authenticate, list connections, run actions, and proxy requests to RapidAPI. They do not ask to read unrelated local files or unset environment variables, and they explicitly advise against asking users for API keys.
Install Mechanism
This is an instruction-only skill with no install spec, but it tells users to run 'npm install -g @membranehq/cli' (global npm install). Installing a global package is a moderate risk vector if you don't verify the publisher and version. The skill does not pin a version or provide an alternative vetted install method.
Credentials
The skill declares no required environment variables or credentials. It relies on Membrane to manage credentials server-side, which is appropriate for its stated purpose.
Persistence & Privilege
The skill is not always-enabled, does not request extra system-wide privileges, and contains no instructions to modify other skills or system configuration.
Assessment
This skill appears to do what it says: it uses the Membrane CLI to connect to RapidAPI and proxy requests. Before using it: (1) verify you trust the Membrane project (check getmembrane.com and the GitHub repo) and confirm the npm package identity; (2) prefer a pinned package version or install via a vetted release method rather than an unpinned global npm install; (3) be aware the skill will operate via your Membrane account—when you run 'membrane login' a browser-based auth will grant it access to connections and APIs, so review the permissions in that flow; (4) consider asking the skill author to declare the 'membrane' binary in the skill metadata and to include an install spec or explicit version to reduce supply-chain risk.Like a lobster shell, security has layers — review code before you run it.
latestvk97cfptd9byefgrbty0ac1f1b58437x2
License
MIT-0
Free to use, modify, and redistribute. No attribution required.