Metric Monitor
Tracks one key metric daily, ships fixes on regression.
Engineering Adapted from use case · Added Aug 22, 2026
Based on 231 ways to use an agent by @dhruvamin
Run Metric Monitor 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 Metric Monitor to own one important metric end to end. Walk me through connecting Datadog, GitHub and Slack, then: check the target metric daily against its historical baseline, investigate the likely cause the moment it regresses using recent deploys and logs, and open a fix PR when the cause is a clear code change. Post the metric's status and any regression analysis in Slack. Learn what a normal versus concerning move in this metric looks like from its history, then save it and run daily.
CONNECT FIRST
Datadog
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
regression-detectionroot-cause-drafting
Reusable capabilities the prompt sets up. Browse the open skills ecosystem at skills.sh.
See something off with Metric Monitor? Suggest an edit. Every agent is one markdown file in the repo.