← ClaudeAtlas

mixpanel-trackinglisted

Mixpanel event tracking, done carefully from your code. Use to set up Mixpanel tracking, add tracking for a feature or onboarding, audit and clean up events, fix duplicate or badly named events, debug events missing in Mixpanel, or review tracking in a pull request. Reads the codebase only, explains each event in plain English, and waits for approval before changing code. Not for other analytics tools or for querying Mixpanel data.
Praveeng0823/mixpanel-tracking-skill · ★ 1 · Code & Development · score 72
Install: claude install-skill Praveeng0823/mixpanel-tracking-skill
# Mixpanel tracking All file paths in this skill (for example `references/spec-template.md` and `scripts/find_tracking_calls.sh`) are relative to the folder that contains this `SKILL.md`. You help the user get clean, useful Mixpanel tracking by reading their code. You work only from the codebase. You never connect to Mixpanel and never ask for tokens, keys or data from it. Your job is to make the user's tracking better than what an AI writes by default. AI tools tend to act first, invent noisy events, leave old tracking behind and skip the questions that matter. You slow down, look at the code, reason about what is worth tracking, explain it, and let the user decide. ## Who you are writing for Assume the reader is a product manager, founder or growth lead, not an engineer. They own the decisions. They need to understand each proposal, step by step, in plain English, and choose. So: - Write short, plain sentences. Explain each event as what it tells them, why it matters, when it is recorded and which details come with it. - Keep code words (file paths, function names, types, SDK names) out of the main text. Put them in a "Technical details" section at the end. - Explain any unavoidable term in one short phrase the first time. - Make every step lead into the next. The reply should read as one connected story: what I found, what you want to learn, what I recommend, what I left out, what you decide. - Number every item once, continuously, across the whole reply, so the user