Smooch
AdvisoryAudited by Static analysis on Apr 30, 2026.
Overview
No suspicious patterns detected.
Findings (0)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
An agent could make broad changes to Smooch customer conversation data or configuration if given or inferred the wrong endpoint, method, or request body.
The skill exposes a raw authenticated API escape hatch with mutation and delete methods, but the provided instructions do not visibly bound endpoints, actions, or approval steps.
When the available actions don't cover your use case, you can send requests directly to the Smooch API through Membrane's proxy... HTTP method (GET, POST, PUT, PATCH, DELETE).
Use prebuilt scoped actions when possible, require explicit user confirmation before create/update/delete/bulk operations, and restrict raw proxy use to reviewed endpoints and request bodies.
The connected Membrane/Smooch account may allow the agent to read or change business messaging data according to the granted permissions.
The integration requires delegated account authentication and automatic credential refresh, which is expected but grants ongoing access through Membrane.
Membrane handles authentication and credentials refresh automatically... membrane login --tenant --clientName=<agentType>
Connect only the intended account, prefer least-privileged access where available, and revoke the Membrane/Smooch connection when no longer needed.
Future installs may run a different CLI version than the one expected at review time.
The setup uses a globally installed npm CLI package pinned to the moving @latest tag; this is purpose-aligned but not fully fixed to a reviewed version.
npm install -g @membranehq/cli@latest
Install from the official package source, consider pinning a known-good version, and keep the CLI updated through a trusted process.
Conversation or user data returned from Smooch may be processed through Membrane in addition to the user's agent environment.
Smooch API traffic and authentication handling flow through Membrane as a gateway. This is disclosed and aligned with the skill, but users should understand that customer data may pass through that service.
send requests directly to the Smooch API through Membrane's proxy... injects the correct authentication headers
Use this only if Membrane is an approved intermediary for the data involved, and avoid sending unnecessary sensitive content in requests.