Inspect Supabase schema and logs via MCP
Connect Supabase MCP and ask for table shapes, RLS notes, and recent error logs.
Data·Easy·0 saves
Setup USE CASEDataModerate
“An hourly brief that says nothing when nothing changed”
From the same Gmail-connected setup, he created standing agents, including an hourly political update on his work topics and a rule to always check with him on key decisions. No posting. Cite sources. Stay quiet if nothing new.
How it runs
5 steps. Do them in order.
- 01In Grok Bot, create a bot named **Brief** and connect Gmail.
- 02Paste the reconstructed prompt below in as its standing instructions, then tell it the one job: hourly monitor.
- 03Give it the context it needs — the accounts, files, and rules specific to your setup — so it can hold the job the way the original build did.
- 04Run it every hour; it acts once you approve each step.
- 05Watch the first few runs, correct anything off, then let it hold the job. Adapt the connected tools to match your own stack.
What you get
Staying quiet is the hard part of a monitoring bot, and this one is built around it: no post, no reply, nothing recycled from the last hour, just a cited brief when something on a named topic actually changed. A 'needs a decision' flag is reserved for the rare case that truly requires you, not every headline.
Prompt
Copy it. Change the names. Keep the job.
Prompt
Role: Hourly political brief. Named topics only. You read. You do not post. Mission: Once an hour, scan for new developments on the work topics I list. Send a short brief. If nothing new since last run, stay quiet. Tools: News sites, official sources, Gmail if a topic has a thread there. No X posting. What good looks like: - A brief: what changed, why it matters for the named topics, 2–4 citations with URLs. Time-stamped. - Quiet if nothing new. Do not recycle the last hour. - A separate “needs a decision” flag only when I must act (not every headline). Never, without asking: post, reply, like, email a reporter, or donate. Never delete mail as part of this job. Cite sources — no unsourced claims. Always check with me on key decisions. Stop if a topic list was never given — ask for 3–7 named topics before the first run.
Use withGrok
via @congressdj
Tips
- ·Reconstructed from @congressdj's published Grok Bot build. Adapt the connected accounts and context to your own stack — the prompt is a Curator reconstruction, not the author's original text.
- ·hourly
- ·acts-with-approval
Related setups
Same category. Different job.
13,425 art prompts, extracted and sorted
Julie McCann had a Grok Bot go through 557 chats across all her projects, extract every art prompt, and sort them by subject into one searchable library — 13,425 in total. When it hit context limits it switched to smaller blocks on its own and finished the ~30-hour job.
Data·Simple·0 saves
Setup Five reasons they left, five things to ship this week
After the win-back emails, Liam's bot analysed overnight why people left and turned that into a 5-step plan. Same tweet as the win-back campaign — this is the research half of the job.
Data·Moderate·0 saves
Setup