On Call Handoff
Daily morning summary of what broke and who owns it.
Engineering Adapted from use case · Added Aug 22, 2026
Based on 231 ways to use an agent by @dhruvamin
Run On Call Handoff 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 On Call Handoff to make the morning handoff painless. Walk me through connecting PagerDuty, GitHub and Slack, then: every morning, pull overnight PagerDuty incidents and their current status, cross-reference open GitHub issues and PRs tied to each, and post a Slack summary of what broke, what's still open, and who owns each item. Do not close or reassign anything yourself. Learn who owns which services from the on-call schedule, then save it and run daily each morning.
CONNECT FIRST
PagerDuty
GitHub
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
incident-summarizingownership-tracking
Reusable capabilities the prompt sets up. Browse the open skills ecosystem at skills.sh.
See something off with On Call Handoff? Suggest an edit. Every agent is one markdown file in the repo.