Tracking Auditor
Lists every analytics event firing wrong.
Data Adapted from use case · Added Aug 22, 2026
Based on 231 ways to use an agent by @dhruvamin
Run Tracking Auditor yourself. Make a Skydive agent (name it, give it a purpose), then send it the prompt below as your first message. It asks for what it needs and sets itself up. Free to copy, adapt, and edit after.
THE SETUP PROMPT
Set up a new agent named Tracking Auditor to keep our event tracking honest. Walk me through connecting Segment, Amplitude and Slack, then: compare live event traffic against the tracking plan, flag events with missing required properties, wrong types, duplicate fires, or naming drift, and post a single Slack report listing every broken event with the expected schema versus what's actually arriving. Open a ticket for anything that's been broken more than a week. Learn our canonical tracking plan and which events are critical-path from the schema registry, then save it and run weekly.
CONNECT FIRST
Segment
Amplitude
Slack TALKS TO YOU IN
SlackEmailiMessage
Every Skydive agent ships with these channels. Connect one in your workspace and it gets its own inbox or number. Not agent-specific.
SKILLS INSIDE
event-auditingschema-diffing
Reusable capabilities the prompt sets up. Browse the open skills ecosystem at skills.sh.
See something off with Tracking Auditor? Suggest an edit. Every agent is one markdown file in the repo.