Esputnik

v1.0.2

ESputnik integration. Manage Contacts, Templates, Campaigns, Events, Reports. Use when the user wants to interact with ESputnik data.

0· 95·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
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the instructions: the skill directs use of the Membrane CLI to manage ESputnik resources. No unrelated credentials, binaries, or paths are requested.
Instruction Scope
SKILL.md only instructs installing and using the Membrane CLI, creating/using a connection, running actions, and proxying requests to ESputnik. It does not ask the agent to read unrelated files, environment variables, or external endpoints beyond membrane/esputnik.
Install Mechanism
No install spec in the skill bundle (instruction-only). The document recommends installing @membranehq/cli via npm (-g). This is a traceable public npm package (moderate-risk install recommendation) rather than a raw download; verify the package/publisher before installing in sensitive environments.
Credentials
The skill declares no required environment variables or credentials and explicitly tells the user to create a connection so Membrane handles auth. No disproportionate credential requests are present.
Persistence & Privilege
The skill is not always-on and doesn't request elevated or system-wide persistence. It is user-invocable and allows normal autonomous invocation (platform default), which is expected for integration skills.
Assessment
This skill is an instruction-only integration that relies on the Membrane CLI to talk to ESputnik. Before installing/using: (1) verify the @membranehq/cli npm package and publisher (check npmjs.org and the GitHub repo) to ensure you're installing the official CLI; (2) be aware that Membrane will act as the auth broker — you are trusting their service to store/manage ESputnik credentials; (3) in sensitive environments, avoid installing global npm packages system-wide or run installations in an isolated environment; (4) when using the proxy feature, double-check request paths and bodies you send through Membrane to avoid unintentionally exposing data. If the skill asked for API keys, local secret files, or unrelated system access, the assessment would change to suspicious; none of those are present here.

Like a lobster shell, security has layers — review code before you run it.

latestvk973c7cst1hxyk1yhqd5pp6da1842e4z

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments