Subprocessor Tracker
Notices when engineering adds a vendor touching your data.
Legal Adapted from use case · Added Aug 22, 2026
Based on 231 ways to use an agent by @dhruvamin
Run Subprocessor Tracker 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 Subprocessor Tracker to catch new subprocessors before customers ask why they weren't disclosed. Walk me through connecting GitHub, Slack and Google Drive, then: scan new dependencies, integrations, and infra changes for vendors that could touch customer data, and check each one against our published subprocessor list. Flag anything new in Slack with what data it would touch and who added it, and keep the tracked list updated in Drive. Learn which vendor categories count as subprocessors from our existing list, then save it and run daily.
CONNECT FIRST
GitHub
Slack
Google Drive 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
vendor-detectiondata-flow-mapping
Reusable capabilities the prompt sets up. Browse the open skills ecosystem at skills.sh.
See something off with Subprocessor Tracker? Suggest an edit. Every agent is one markdown file in the repo.