Sendloop
v1.0.0Sendloop integration. Manage Subscribers, Lists, Segments, Campaigns, Forms. Use when the user wants to interact with Sendloop data.
⭐ 0· 25·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description match the instructions: the SKILL.md shows how to manage Sendloop via the Membrane CLI. All required capabilities (network access, a Membrane account) are proportional to a Sendloop integration.
Instruction Scope
Instructions tell the agent to run npx @membranehq/cli commands and to create/use credentials at ~/.membrane/credentials.json. Referencing/writing a home-directory credentials file is expected for this connector but the manifest declared no required config paths, so the README and declared metadata are slightly out-of-sync.
Install Mechanism
There is no formal install spec (instruction-only). The runtime uses npx @membranehq/cli@latest which will fetch and execute code from the npm registry on demand — this is common for CLI workflows but means remote code is executed dynamically rather than pre-installed.
Credentials
The skill does not ask for environment variables or unrelated credentials. The only persistent secret handling described is Membrane-managed credentials stored under ~/.membrane (handled by the CLI), which is consistent with the integration purpose.
Persistence & Privilege
The skill does not request always-on/privileged presence. It instructs use of a third-party CLI that will store connection credentials locally and proxies API calls through the Membrane service — this is normal for connector workflows but worth noting for privacy.
Assessment
This skill appears coherent and implements a Sendloop integration by calling the Membrane CLI. Before installing: 1) Confirm you trust the Membrane service/operator because your Sendloop connection and API traffic are proxied through Membrane and credentials are stored under ~/.membrane/credentials.json. 2) Be aware that the skill runs npx @membranehq/cli@latest at runtime, which downloads and executes code from npm; prefer pinning to a specific version if you require reproducibility or review. 3) Expect the login flow to open a browser or print a URL for headless completion. 4) If you have corporate policy restrictions about third-party proxies or storing API credentials locally, verify compliance first.Like a lobster shell, security has layers — review code before you run it.
latestvk97b7xx6bt4x3vwm0h9abn4s25844zjf
License
MIT-0
Free to use, modify, and redistribute. No attribution required.