Mixpanel
v1.0.0Mixpanel integration. Manage data, records, and automate workflows. Use when the user wants to interact with Mixpanel data.
⭐ 0· 55·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 name/description (Mixpanel integration) matches the instructions: all runtime steps talk to Mixpanel via the Membrane CLI. There are no unrelated credentials, binaries, or config paths requested.
Instruction Scope
SKILL.md instructs installing and using the @membranehq/cli, logging in via browser or a headless flow, creating connections, running pre-built actions, and proxying requests to the Mixpanel API. These actions are within the stated purpose, but they do require installing a CLI and performing interactive auth—the agent or user will run commands that can affect the local environment (global npm install) and open browser-based auth flows.
Install Mechanism
There is no automated install spec in the skill bundle; the doc tells you to run `npm install -g @membranehq/cli`. Installing a package from the public npm registry is a normal choice for a CLI but has moderate risk compared with an instruction-only skill that doesn't require new software. Verify the package and publisher before running global installs.
Credentials
The skill requests no environment variables or secrets and explicitly recommends letting Membrane handle credentials (so you should not be asked for Mixpanel API keys). That is proportional to its purpose given it relies on a Membrane account.
Persistence & Privilege
always is false and the skill does not request persistent system-wide privileges or attempt to modify other skills or system configs. It relies on the Membrane CLI and an interactive login flow for auth, which is typical.
Assessment
This skill looks coherent, but before installing: 1) Verify the @membranehq/cli package and the Membrane service (check npmjs.org, the repository, and the getmembrane.com site) to ensure you trust the publisher; 2) Prefer running installations in a controlled environment (not on critical production hosts) since `npm install -g` modifies the system; 3) Do not share Mixpanel API keys directly—use the Membrane login/connection flow as instructed; 4) Confirm Membrane's privacy and security posture if you will proxy sensitive analytics data through their service.Like a lobster shell, security has layers — review code before you run it.
latestvk97bhhavpk7qrgd8z5adfpqbq5849qp0
License
MIT-0
Free to use, modify, and redistribute. No attribution required.