← Back to library

Run a fast watcher and a slow watcher, and allow silence

Matt Palmer (@mattyp) runs two Slack watchers at different speeds, as his Intro to Grok Bot article explains: a Content bot checks engineering and product channels hourly for small launches and suggests social copy, and a Product bot reads announcement channels once a day. We found it via Carnage (@0xCarnagee), who adds a 'nothing today' rule for empty days.

  • OutcomeSet an hourly narrow-signal watcher and a daily theme summary watcher, both allowed to report nothing instead of inventing updates.
  • SetupUnder an hour
  • LevelIntermediate
  • CreditMatt Palmer (@mattyp)
View original
Works with
Grok BotChatGPT agentClaudeClaude Cowork

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You miss small ships in busy channels
  • Daily digests are noisy because the bot invents filler
  • You want schedule triggers without a visual workflow builder

Not for: Broad listeners that fire on every message; Forcing a daily update when nothing happened; Auto-posting to public social without a draft gate

What do you need, and what do you get?

You need

  • Fast-lane channels and the narrow signal to catch
  • Slow-lane announcement sources and delivery time
  • Draft destination (private note, draft queue) for fast alerts

You get

  • Fast-lane routine: hourly scan, alert with draft, or silence
  • Slow-lane routine: one daily themed summary with links
  • A nothing-today rule both routines must obey

How does it work, step by step?

  1. Split speedsHourly for decaying signals; daily for announcements.
  2. Narrow the signalShips, releases, complaints — not every message.
  3. Allow silenceIf nothing matches, reply empty-day and halt.
  4. Draft, do not postFast lane suggests language; you send or publish.

The prompt

Our own prompt, inspired by Matt Palmer (@mattyp) and written to work in Grok Bot, ChatGPT agent, Claude and others. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt5 variables
Configure two watcher routines.
Fast lane channels: {fast_channels}. Narrow signal: {fast_signal}.
Slow lane sources: {slow_sources}. Daily time/timezone: {daily_time}.
Draft destination: {draft_destination}.

Fast lane: each hour, look only for the narrow signal. If found, open a note covering the event, its importance, and a draft. If none, stay silent.
Slow lane: daily, one themed rollup with every source linked.
Shared rule: if there is nothing, reply empty-day and halt. Never invent filler just to occupy the slot.
Do not publish or send externally without my approval.

Inspired by Matt Palmer (@mattyp): Intro to Grok Bot (X Article). The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Greedy listeners burn usage overnight and train you to ignore alerts.
  • Manufactured updates are how people wake up to false reports.
  • Ask the bot to set its own trigger, then tighten it after misfires.
  • Keep public posts behind your approval even when the draft is good.

Our take

Response bots are easy; notice bots are useful. Palmer's fast and slow lanes, plus Carnage's quiet-empty-day rule, are the parts to keep. We forbid filler updates because manufactured digests train you to ignore alerts. Greedy listeners that fire on every message burn usage overnight. In our dry run with fictional engineering Slack and a daily announce channel, the hourly watcher found one ship and drafted a private note, then reported silence on the next two hours; the daily bot returned one themed summary with links and answered empty-day when we cleared the channel. Drafts stayed in a queue you review; nothing posted publicly. Use narrow signals only. Retune the trigger after the first week of misfires instead of broadening the filter. Credit goes to Matt Palmer's own article; Carnage's write-up is where we found it. Palmer also skips the settings screen: he asks the bot in chat to create its trigger and tweaks the timing after a misfire, which keeps each watcher cheap to change.

Where the time goes back: You catch time-sensitive ships without opening channels all day, and daily digests stay honest because empty days stay empty.

FAQ

Why two bots instead of one?
Different decay times. Hourly noise and daily themes fight each other in one routine.
Is silence really OK?
Yes. The article treats nothing today as the correct output when there is no signal.
Where should drafts go?
A private chat or draft queue you already review, not straight to customers.

Source and credit

Inspired by Matt Palmer (@mattyp). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Intro to Grok Bot (X Article)
Creator
Matt Palmer (@mattyp)
Published on
X
Original date
Aug 11, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Grok Bot
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. Silence allowed; no filler update.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Also see: The Grok Bot Team's Own Workflow (X Article, where we found this) by Carnage (@0xCarnagee). A related version of the same idea; credited and linked only, nothing from it is reproduced here.

Are you the creator? Claim or correct this page.

More in Operations & Admin

All 203 Operations & Admin playbooks →

Related playbooks

Operations & AdminRoutine✓ AI dry run

Publish the sprint changelog from completed tickets

On a schedule, pull completed tickets, decide which are user-facing, draft the changelog from ticket context, and wait for your review before publishing or emailing users.

Credit: u/Senseifc on r/ClaudeAI

Under an hour
Operations & AdminPrompt✓ AI dry run

Rewrite a task prompt to go deeper, not bigger

Before handing an AI an important piece of work, have it explain how a leading practitioner would approach the job, which raw inputs and methods they would use, and what independent check would prove the answer right, then rewrite your request around those answers before any work starts.

Credit: Felix Rieseberg

Minutes
Operations & AdminPrompt✓ AI dry run

Run each project from one page your agents keep current

Have your lead agent give every active project its own living page (goal, status, owners, deadlines, decisions, blockers and a change log), keep a master list of all projects, require every agent to read the page before working and update it afterward, and run a weekday check that only pings you about blocked, late or decision items.

Credit: Michael Fenech (@Michael_Fenech_)

Under an hour
Operations & AdminSkill✓ AI dry run

Keep your coding agent on current web platform features

Add Google Chrome's modern-web-guidance skill to Claude Code, Codex, Cursor or another coding agent so that before it writes front-end code it looks up a vetted guide for the pattern at hand, uses built-in browser features such as native dialogs instead of old JavaScript workarounds, applies fallbacks only where browser support requires them, and tells you which guides shaped the change.

Credit: GoogleChrome

Minutes
Operations & AdminWorkflow✓ AI dry run

Build and launch a hobby web app with a hosted coding agent

Go from a feature list to a live web app with storage, analytics, sign-up email integration and a landing page, without writing the code yourself.

Credit: Günter Richter

An afternoon+