install
/install
Set up Mixpanel for this project — set up an engine for the other Mixpanel skills to use (Mixpanel MCP server, mixpanel-headless Python SDK, or the user's own integration). Use whenever the user asks to set up, install, configure, or connect Mixpanel, switch Mixpanel engine or region, or when any Mixpanel skill finds no engine set up. Trigger phrases: "set up mixpanel", "configure mixpanel", "connect mixpanel", "install mixpanel", "switch mixpanel region", "use mixpanel headless", "change mixpanel engine", "add another engine". Do NOT use for adding Mixpanel tracking code to an application (us
- Author
- mixpanel ↗
- Repository
- ai-plugins ↗
- Licence
- Apache-2.0
- Last repository change
- 22.10.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Set up Mixpanel for this project — set up an engine for the other Mixpanel skills to use (Mixpanel MCP server, mixpanel-headless Python SDK, or the user's own integration). Use whenever the user asks to set up, install, configure, or connect Mixpanel, switch Mixpanel engine or region, or when any Mixpanel skill finds no engine set up. Trigger phrases: "set up mixpanel", "configure mixpanel", "connect mixpanel", "install mixpanel", "switch mixpanel region", "use mixpanel headless", "change mixpanel engine", "add another engine". Do NOT use for adding Mixpanel tracking code to an application (us
Triggers from the description
Original author description
Set up Mixpanel for this project — set up an engine for the other Mixpanel skills to use (Mixpanel MCP server, mixpanel-headless Python SDK, or the user's own integration). Use whenever the user asks to set up, install, configure, or connect Mixpanel, switch Mixpanel engine or region, or when any Mixpanel skill finds no engine set up. Trigger phrases: "set up mixpanel", "configure mixpanel", "connect mixpanel", "install mixpanel", "switch mixpanel region", "use mixpanel headless", "change mixpanel engine", "add another engine". Do NOT use for adding Mixpanel tracking code to an application (us
How it works
- Step 0 — Detect existing state
- Step 1 — Pick an engine to set up
- Step 2a — MCP path
- Step 2b — Headless path
- Step 2c — Own-integration path
- Step 3 — Confirm and wrap up
SKILL.md preview
--- name: install description: > Set up Mixpanel for this project — set up an engine for the other Mixpanel skills to use (Mixpanel MCP server, mixpanel-headless Python SDK, or the user's own integration). Use whenever the user asks to set up, install, configure, or connect Mixpanel, switch Mixpanel engine or region, or when any Mixpanel skill finds no engine set up. Trigger phrases: "set up mixpanel", "configure mixpanel", "connect mixpanel", "install mixpanel", "switch mixpanel region", "use mixpanel headless", "change mixpanel engine", "add another engine". Do NOT use for adding Mixpanel tracking code to an application (use tracking-implementation) or for running analytics queries. Interactive — asks the user to choose; do not run in non-interactive sessions. compatibility: "Works in any project. Sets up an engine for the other Mixpanel skills to use." metadata: engine: none --- # Mixpanel Install > **No engine required** — this skill is what _sets engines up_. Set up how this project talks to Mixpanel. Engines can coexist — a project may have more than one; this skill adds one and can record which to prefer. How the other skills resolve an engine (the precedence ladder, preference locations) lives in [`../../ENGINE.md`](../../ENGINE.md) — read it before starting. This skill is **interactive**: it asks the user to choose. If the session can't ask questions (non-interactive/CI run), stop and tell the user to run `/mixpanel:install` in an interactive session instead. The bundled references defer to the live Mixpanel docs they cite — on any conflict, trust the live page. --- ## Step 0 — Detect existing state 1. Mixpanel MCP tools listed in this session → tell the user the MCP engine is already set up (name the region if the server URL is visible) and ask: keep it, switch, or add another engine alongside it. Keep → stop here. Add another → Step 1, skipping the MCP option. 2. Otherwise run `mp --version` (one command). Success → the headless SDK is installed: ask **"MCP is not available — how should we proceed?"** with two options: (a) install MCP, (b) use headless. Installing MCP → Step 2a. Using headless → verify auth (Step 2b's verify) and jump to Step 3, including the preference note. 3. Neither → continue to Step 1. ## Step 1 — Pick an engine to set up Ask with the client's multiple-choice question UI (one question, three options): 1. **Mixpanel MCP server** _(recommended for interactive analytics)_ — a remote server exposing Mixpanel tools; OAuth login; best when a person is in the loop. 2. **Headless SDK** — the [`mixpanel-headless`](https://docs.mixpanel.com/docs/mixpanel-headless) Python package; the full Mixpanel platform as a Python object; best for scripted, CI, or coding-agent workflows. 3. **I have my own integration** — the user already has their own way to reach Mixpanel. ## Step 2a — MCP path 1. Ask the **region**: US / EU / India (URL map in [`references/mcp-setup.md`](references/mcp-setup.md)). If the user is unsure, their Mixpanel URL tells them (`eu.mixpanel.com` → EU, `in.mixpanel.com` → India; otherwise US). 2. Register the server with the current client following [`references/mcp-setup.md`](references/mcp-setup.md) — the standard recipe per client, plus the fallback transport. No further questions; just run the standard installation. 3. **Verify**: list the server's tools. If authentication is pending, have the user complete the client's OAuth flow (per the reference), then re-check. ## Step 2b — Headless path 1. Run the one-line availability check from [`references/headless-setup.md`](references/headless-setup.md); install the SDK if it's missing. 2. Authenticate per the reference: run `mp login` yourself — it picks the right flow from the environment (opens the user's browser for OAuth, or uses service-account / bearer-token env vars when set). Don't ask the user to run it; just tell them to complete the login in the browser. Credentials never go in tracked files. 3. **Verify** with `mp account test`. On failure, surface the exact error and fix auth before wrapping up. ## Step 2c — Own-integration path Nothing to install and nothing to interrogate — assume the user provides the context needed to act (in the conversation, or in the project's agent instructions like `CLAUDE.md`). Acknowledge, skip Step 3's verification, but do offer Step 3's preference note so future sessions pick the integration up. ## Step 3 — Confirm and wrap up Always complete all three points — even when this skill was triggered mid-task by another skill, finish them **before** resuming the original request. 1. Re-run the verification for the chosen path and summarize what is now available — the engine just set up (engine, region, where it lives — e.g. the repo's `.mcp.json` or the Python environment) plus any engine the project already had. 2. **Preference note** — if the user ended on an engine other than MCP, or more than one engine is now available, ask: "Want me to leave a note of this preference so you don't have to specify it each time?" If yes, ask where — project level or user level — and append one plain line (e.g. `For Mixpanel, use the headless SDK.`) to the matching file per [`../../ENGINE.md`](../../ENGINE.md): project → the project's `CLAUDE.md` (or `AGENTS.md` in Cursor); user → `~/.claude/CLAUDE.md` (in Cursor, point them to Settings → Rules). Never write without asking. A note is only needed to prefer something other than MCP. 3. Suggest a next step: try a skill like `analyze-report`, `deep-research`, or `tracking-implementation`. If the headless engine was installed, also mention the SDK's companion plugin (see [`references/headless-setup.md`](references/headless-setup.md)).
Files in this package (3)
- SKILL.md 6 KB
- references/headless-setup.md 4 KB
- references/mcp-setup.md 3 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · mixpanel/ai-plugins | 90 | Apache-2.0 |
| rossoctl/context-guru | 100 | Apache-2.0 |
| jeremylongshore/tons-of-skills-marketplace | 100 | MIT |
| codifydoo/gatehand | 100 | MIT |
| terrylica/cc-skills | 100 | MIT |
| agile-4/opem-agent-plugin | 100 | MIT |
| artk0de/tearags-mcp | 100 | MIT |
| artk0de/tearags-mcp | 100 | MIT |
| brainweb/payload-mcp-oauth | 100 | MIT |
Database snapshot: 13.11.2026 · package version a2f2e4c161d6 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100gx-mixpanel-expert
Implement Mixpanel tracking plans, funnels, retention, and Boards. Use when the user asks for mixpanel product analytics expert work, or mentions gx, mixpanel, expert. - 100prepare-ai-readiness
Gets a Mixpanel org or project ready for its AI assistants — business context and Lexicon metadata. Use to set up or import context, fill gaps, or check AI-readiness: "set us up for Mixpanel AI", "how ready are we for the agent". Not for dashboards or metrics. Requires a… - 100tracking-implementation
Guides a coding agent through helping a Mixpanel customer implement analytics correctly. Covers Quick Start (first events in one session), Full Implementation (complete production-ready setup), Add Tracking (extend existing implementation), and Implementation Audit. Use when a… - 100mixpanel-login
Log into Mixpanel EU project via magic link. Uses slavochek-gmail MCP to fetch the link automatically. NOTE — prefer Mixpanel MCP for queries (no login needed). Use this skill only when Chrome-based Mixpanel access is required (e.g., creating alerts, visual board inspection). - 100mixpanel
Mixpanel is a product analytics service for tracking events, building funnels and retention reports, and segmenting users. Use when a user asks to add Mixpanel tracking to a web app, send server-side events from Node.js or Python, identify users, set up company-level group… - 90code-review
Procedure to review a pull request in mixpanel-headless and check each finding before it is posted. Use for every pull request review in this repository.