Postalytics
v1.0.2Postalytics integration. Manage Organizations. Use when the user wants to interact with Postalytics data.
⭐ 0· 109·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
high confidencePurpose & Capability
The skill claims to integrate with Postalytics and its runtime instructions exclusively describe using the Membrane CLI to discover connectors, create connections, run actions, and proxy requests to Postalytics. The only external dependency it instructs users to install is the @membranehq/cli, which is consistent with the stated purpose.
Instruction Scope
SKILL.md only directs the agent/operator to install and use the Membrane CLI, perform login flows, list and run connector actions, and proxy API requests through Membrane. It does not instruct reading unrelated local files, environment variables, or exfiltrating data to third-party endpoints outside Membrane/Postalytics.
Install Mechanism
This is an instruction-only skill (no automated install spec). It tells the user to run a global npm install of @membranehq/cli. That is a reasonable user-side step for this integration but does modify the host environment and depends on the npm package's trustworthiness — consider verifying the package on npm/github before installing globally.
Credentials
The skill declares no required environment variables or credentials. It relies on Membrane's hosted auth flow (browser-based login / connection creation) so it does not request local API keys or unrelated credentials — proportional to its purpose.
Persistence & Privilege
The skill does not request always:true and does not modify other skills or system-wide settings. Autonomous model invocation is allowed (platform default) but there are no extra persistence or privilege escalations in the skill itself.
Assessment
This skill is coherent: it instructs you to use the Membrane CLI to connect to Postalytics and does not ask for unrelated secrets. Before installing: (1) verify the @membranehq/cli npm package and the Membrane service (website/repo, maintainers) to ensure you trust the publisher; (2) be aware that a global npm install changes your system tooling; (3) understand that Membrane will proxy API calls and hold connection credentials server-side—only proceed if you trust Membrane to handle your Postalytics data; (4) in headless or CI environments, plan how you'll complete the Membrane auth flow. If any of these trust assumptions are unacceptable, do not install or use the skill.Like a lobster shell, security has layers — review code before you run it.
latestvk97e5x4tfgted639hn8sbz87e5842t3q
License
MIT-0
Free to use, modify, and redistribute. No attribution required.