QA Flow Tester
Walks production's critical flows every morning, reports.
Engineering Adapted from use case · Added Aug 21, 2026
Based on 231 ways to use an agent by @dhruvamin
Run QA Flow Tester 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 QA Flow Tester to walk the production app's critical end-to-end flows every morning in its own browser. Walk me through connecting Slack and GitHub, then: run signup, checkout, and the other flows we mark critical, capture screenshots at each step, and post pass, fail, and screenshots to #eng before standup so the team sees it before the day starts. File a GitHub issue automatically on any failure. Learn which flows count as critical and how to log into staging vs prod, then save it and run every morning before standup.
CONNECT FIRST
Slack
GitHub
Playwright 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
e2e-testingincident-reporting
Reusable capabilities the prompt sets up. Browse the open skills ecosystem at skills.sh.
See something off with QA Flow Tester? Suggest an edit. Every agent is one markdown file in the repo.