Bug Investigator
First-pass investigation when support escalates a bug.
Engineering Adapted from use case · Added Aug 22, 2026
Based on 231 ways to use an agent by @dhruvamin
Run Bug Investigator 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 Bug Investigator to do the first pass on every bug support escalates. Walk me through connecting GitHub, Sentry, Slack and Zendesk, then: when a ticket gets escalated in Zendesk, pull the related Sentry errors and recent GitHub commits, identify the likely offending change, and post a Slack summary with the suspected cause, affected users, and a link to the code. Do not open PRs or change any code. Learn which services and error signatures map to which repos from past escalations, then save it and run on every new escalation.
CONNECT FIRST
GitHub
Sentry
Slack
Zendesk 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
log-triageroot-cause-drafting
Reusable capabilities the prompt sets up. Browse the open skills ecosystem at skills.sh.
See something off with Bug Investigator? Suggest an edit. Every agent is one markdown file in the repo.