Redis Labs
v1.0.2Redis Labs integration. Manage data, records, and automate workflows. Use when the user wants to interact with Redis Labs data.
⭐ 0· 71·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
high confidencePurpose & Capability
Name/description (Redis Labs integration) align with the instructions: the SKILL.md tells the agent to use the @membranehq/cli to discover connectors, create a connection, run actions, and proxy API calls to Redis. Required capabilities (network, Membrane account) are appropriate for the stated purpose.
Instruction Scope
Instructions stay within the Redis Labs integration scope (discover actions, run them, proxy requests). Important privacy/security implication: the SKILL.md relies on Membrane's proxy and auth handling — calls and credentials are sent to Membrane so users must trust that service. The doc does not instruct reading unrelated local files or environment variables.
Install Mechanism
No registry install spec is provided, but the SKILL.md instructs installing @membranehq/cli globally via npm (npm install -g @membranehq/cli). Installing a global npm package is a normal way to get a CLI, but it has moderate risk since it executes third-party code on the host; verify the package and vendor before running.
Credentials
The skill declares no required environment variables or local config paths. It also explicitly recommends not asking users for API keys and instead creating a connection through Membrane — the requested scope of credentials is proportionate.
Persistence & Privilege
Skill is instruction-only, has no install-time effects in the registry, does not request always:true, and does not ask to modify other skill settings. Agent autonomous invocation is allowed by default (normal) and unchanged here.
Assessment
This skill appears coherent, but note two practical risks before installing: (1) it requires installing @membranehq/cli globally (npm install -g), which will run third-party code on your machine — check the package source, version, and vendor reputation; (2) Membrane will proxy API calls and hold auth for your Redis instances, so you should only use it if you trust Membrane (review their privacy/security docs and consider least-privilege Redis credentials or a staging account). If you cannot trust Membrane, avoid installing and instead use official Redis tooling or direct API integration under your control.Like a lobster shell, security has layers — review code before you run it.
latestvk97a391gzdwwc43t2ega5hhrv5843qgk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.