Getresponse

PassAudited by ClawScan on Apr 3, 2026.

Overview

The skill is internally consistent: it delegates GetResponse access to the Membrane CLI and requires no additional credentials or unusual system access, but the package is third‑party and the source/homepage should be verified before installing the CLI globally.

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.