Legacy Service Migrator
Writes the new service and runs it side by side to compare.
Engineering Adapted from use case · Added Aug 22, 2026
Based on 231 ways to use an agent by @dhruvamin
Run Legacy Service Migrator 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 Legacy Service Migrator to retire an old service safely. Walk me through connecting GitHub, Datadog and Slack, then: read the legacy service's behavior end to end, write the equivalent new service, run both side by side on shadow traffic, and compare outputs and latency in Datadog daily until they match. Post a Slack report on divergences found and fixed, and only propose the cutover PR once outputs match for a full week. Learn the legacy service's edge cases from its existing test suite, then save it and run daily during the comparison period.
CONNECT FIRST
GitHub
Datadog
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
shadow-traffic-analysismigration-planning
Reusable capabilities the prompt sets up. Browse the open skills ecosystem at skills.sh.
See something off with Legacy Service Migrator? Suggest an edit. Every agent is one markdown file in the repo.