Rudderstack Http
v1.0.2RudderStack HTTP integration. Manage data, records, and automate workflows. Use when the user wants to interact with RudderStack HTTP data.
⭐ 0· 123·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 and description describe RudderStack HTTP integration and the SKILL.md instructs the agent to use the Membrane CLI to discover and run RudderStack-related actions — this matches expectations.
Instruction Scope
Instructions are limited to installing and using the Membrane CLI, authenticating, listing/searching connections and actions, and running those actions. They do not instruct reading unrelated files, harvesting environment variables, or exfiltrating data to unexpected endpoints.
Install Mechanism
There is no install spec in the manifest (instruction-only), but the SKILL.md tells users to run `npm install -g @membranehq/cli` or use `npx`. Relying on npm/global install is expected for a CLI integration but is a moderately privileged action — verify the package and registry before installing.
Credentials
The skill declares no required env vars or credentials; it explicitly relies on Membrane's interactive authentication. This is proportionate to the described functionality.
Persistence & Privilege
The skill is not forced always-on (always:false) and does not request elevated platform privileges or modify other skills' configurations. Autonomous invocation is allowed by default but does not combine with other red flags here.
Assessment
This skill is instruction-only and coherent: it expects you to install and use the Membrane CLI to manage RudderStack HTTP integrations. Before installing or running anything: (1) verify the npm package name and publisher (@membranehq/cli) and prefer using npx or a scoped/local install if you want to avoid a global package; (2) confirm the Membrane site/repository and package integrity (checksums/signing) if possible; (3) ensure the Membrane account you authenticate with has only the permissions you intend to grant, since the CLI will act on your behalf and can interact with your RudderStack connections and data; (4) review action input/output carefully before running actions that modify or export data. If you do not trust the Membrane provider or the npm package, do not install the CLI.Like a lobster shell, security has layers — review code before you run it.
latestvk97fta4m4vgvb3pqahnka78psn842hwt
License
MIT-0
Free to use, modify, and redistribute. No attribution required.