Onboard users to the Mixpanel MCP server through guided, interactive modules. Use when the user asks "how do I use MCP", "what can I ask", "what should I try first", "show me what MCP can do", or is figuring out where to start (e.g. "what now?"). Always invoke this skill when the user asks about MCP capabilities, even if the question seems simple. Do NOT use for: creating reports or dashboards, running queries, tracking setup, experiment analysis, or Lexicon management — use the dedicated skills for those tasks.
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 Mixpanel MCP.
Full lifecycle dashboard management for Mixpanel — create, template, clone, clean up, inventory, and update dashboards across projects and teams. ALWAYS use when a user asks to: create a dashboard, build a board, template or clone a dashboard, clean up stale dashboards, audit dashboards, list all dashboards, inventory boards, update or rename a dashboard, delete a dashboard, or standardize boards across projects. Also trigger on "duplicate board", "stale dashboards", "empty boards", "board management", or when dashboards are mentioned with "governance", "cleanup", "template", "onboarding", or "standardize". Do NOT use for A/B experiments (use `manage-experiment`), feature-flag rollouts (use `manage-feature-flags`), or Lexicon/event-and-property metadata cleanup (use `manage-lexicon`). Requires Mixpanel MCP.
Monitor and diagnose a Mixpanel metric for anomalies, drift, and root cause. Use whenever the user asks to investigate, debug, monitor, or explain a change in a metric tracked in Mixpanel — a saved Metric, KPI, conversion rate, retention, event count, funnel step, or anything tracked in a saved report or dashboard. Trigger phrases: "monitor [metric]", "what's going on with [metric]", "why did [metric] drop/spike", "diagnose this metric", "check for anomalies", "has [metric] drifted", "what's driving the drop", "where is the movement coming from", "run RCA on this metric". Also trigger when the user shares a Mixpanel report/dashboard/metric link and asks what's happening, or describes a metric in prose and wants to know if the movement is real. Do NOT trigger for portfolio health checks (use `weekly-pulse`) or adoption reports (use `gtm-customer-intelligence`). Requires this plugin's Mixpanel MCP connector.
Read and explain a Mixpanel report or chart — what it shows, what's notable, and what's worth a closer look. Use whenever the user asks to interpret, explain, summarize, review, or break down an existing chart, report, or saved query in Mixpanel. Trigger phrases: "what does this chart show", "explain this report", "interpret this chart", "summarize this for me", "what's notable here", "anything weird in this chart", "tell me what's happening", "review this insight", "walk me through this report", "what's the takeaway from this". Also trigger when the user pastes a Mixpanel chart or report URL and asks anything about it. Lean by default — surfaces what the report shows and flags notable patterns, but does not chase root causes. Do NOT trigger for building new charts, reviewing entire dashboards, or full root-cause diagnostic workflows (for "why did this change" questions, use monitor-metrics). Requires Mixpanel MCP.
Coach the user through any phase of a Mixpanel experiment — design (hypothesis framing, metric selection, sizing, statistical-model choice, advanced features like CUPED / Winsorization / multiple-testing correction), launch (pre-launch readiness check and the irreversible launch), monitor (mid-flight safety: SRM, sample pace, guardrail peeks, terminate-early calls), and interpret (read results, decide ship / iterate / kill / wait, read health checks like SRM and Retro A/A, break down by segment, use session replays). Use when the user mentions an experiment or A/B test, a ship/kill decision, MDE, sample ratio mismatch, CUPED, or statistical significance, or asks things like "set up an experiment", "is my experiment SRM-ing", "should we ship", "what's my MDE", or "audit my experiment". Do NOT use for plain feature-flag rollouts with no measurement criterion — that belongs to the `manage-feature-flags` skill.
Coach the user through Mixpanel feature-flag work — picking the right flag-shaped product (Feature Gate vs Dynamic Config vs Experiment), naming and keying, staged rollouts, the kill switch, exposure debugging, and archive/restore. Use when the user wants to create, configure, ramp, kill, archive, restore, debug, or clean up a Mixpanel feature flag, or asks why exposures are zero, why a rollout-percentage change had no effect, whether to use a flag or an experiment, or how to clean up stale flags. Trigger on phrasings like 'create a feature flag', 'roll out X to 10%', 'kill the flag', 'why doesn't my flag work', 'archive these stale flags', or 'is this a feature flag or an experiment'. Do NOT use for experiment design ('how should I size this A/B test?', 'what MDE can I detect?'), launch, mid-flight monitoring, or results interpretation ('should we ship?', 'what does this SRM failure mean?') — those belong to the `manage-experiment` skill.
Reviews project documentation (README, CLAUDE.md, docs/, guides, references/) against a strict, weighted quality rubric and produces a score (0-100%) with actionable issues — checking that docs are accurate against the code, current (no changelog phrasing), concise, and well structured. Use when asked to review, audit, score, or quality-check documentation, or to verify the docs still match the code. Triggers on: "review the docs", "audit the README", "is this doc still accurate", "check the docs against the code", "score the documentation". Do NOT use for: reviewing Agent Skills (use review-skill), reviewing application code or pull-request diffs (use code-review / simplify), or writing new documentation from scratch.