Getresponse
v1.0.0GetResponse integration. Manage data, records, and automate workflows. Use when the user wants to interact with GetResponse data.
⭐ 0· 32·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 skill description (GetResponse integration) matches the instructions: it tells the agent to use the Membrane CLI to connect, run actions, and proxy API requests. Nothing requested (no env vars, no config paths) is out of scope for a connector-based integration.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, performing connector discovery, creating connections, running actions, and proxying GetResponse API calls. It does not instruct reading unrelated files, exfiltrating data, or accessing unrelated credentials. The proxy capability allows arbitrary GetResponse API paths which is expected for a connector.
Install Mechanism
There is no formal install spec in the registry (it's instruction-only). The doc recommends running `npm install -g @membranehq/cli`, which is a normal but privileged global npm install; installing third‑party CLIs has moderate supply‑chain risk — verify the npm package and maintainer before running.
Credentials
No environment variables, credentials, or config paths are requested by the skill; it explicitly delegates credential management to Membrane and warns not to ask users for API keys, which is proportionate to the stated purpose.
Persistence & Privilege
The skill does not request always: true or any special persistent privileges. It is user-invocable and allows normal autonomous invocation (platform default). It does not modify other skills or system-wide configs.
Assessment
This skill appears coherent: it uses the Membrane CLI to integrate with GetResponse and asks for no local secrets. Before installing or running it, verify the Membrane project and the @membranehq/cli package on npm (publisher, recent release, repository contents). Confirm the homepage/repository (the SKILL.md references membranedev and GetResponse docs) and ensure you trust the service that will manage your GetResponse credentials. When authenticating, review the OAuth consent and permissions shown in the browser and prefer using a least-privilege/limited GetResponse account for testing. If you cannot verify the CLI source, avoid installing a global npm package in a production environment — run it in a disposable container or VM first.Like a lobster shell, security has layers — review code before you run it.
latestvk97btzpkrj7e883xkecz334ez18454hp
License
MIT-0
Free to use, modify, and redistribute. No attribution required.