an end-of-day digest of the slack channels you choose

the message

every weekday at 5:30pm, read today's messages across #acme-launch, #acme-support and any other channels i explicitly name in this workspace. include relevant thread replies you can access, even when the parent message is older.

combine the channels into one end-of-day digest here with three short groups:
- decisions explicitly agreed in the discussion
- commitments someone explicitly made, with the person and any stated deadline
- questions still unresolved in the messages you read

include the channel and a message link for each item. label suggestions as suggestions, not decisions. don't assign an owner or invent a deadline when neither was stated. skip greetings, repeated announcements and social chatter. check access to every named channel and its relevant threads before deciding the day was quiet. report any failed or incomplete reads here, naming the channel and the missing coverage. only stay quiet when all reads succeeded and there is nothing substantive across the channels.

use only the named channels, not direct messages or other channels. don't post, reply, react, mark anything read or change slack.

when

weekdays at 17:30 in the time zone you choose, covering that day's discussion in your selected channels

needs

slack connected with read access to the selected workspace and channels, including conversation history, thread reads and message links

what comes back

an example, not a real run

today in the selected acme channels

decisions: #acme-launch, priya confirmed that the public demo moves to thursday. source: priya's message at 10:20.
commitments: #acme-support, sam said he will test the corrected import file tomorrow morning. source: sam's thread reply at 15:40.
open questions: #acme-launch, no answer found to whether the old signup page should remain live. source: priya's question at 16:10.
scope: #acme-launch and #acme-support only. both channel reads and relevant thread reads succeeded; no direct messages read.

make it yours

• start with two named channels and add another only when you know what useful information it would contribute
• change the reporting time to fit the team's working day, and say whether a cross-time-zone team needs a wider window
• add a topic filter such as customer escalations, while keeping links so you can inspect what was left out
• cap the digest at five items and ask the bot to group repeated references to the same decision
• if you want a channel post later, grant the specific send action and keep Ask every time selected; sending is separate from reading

when it goes wrong

• a proposal sounds like a final decision. require a message where someone explicitly confirms the choice, and list anything weaker as an open proposal.
• it misses the answer in a thread. ask it to open the thread before calling a question unresolved, and to state when replies were inaccessible.
• it reports yesterday's item again because the discussion continued today. ask it to include only the new decision or changed commitment, with the earlier context kept brief.
• a quiet channel and an inaccessible channel look the same. require the bot to report an access failure instead of treating it as a day with no news.

a useful digest keeps its sources close

the slack connector lists conversation history, thread reads and message permalink retrieval. a summary should use those references so you can open the discussion behind a short line. do not treat the summary as a replacement for reading a sensitive disagreement.

a product manager might choose release and feedback channels; someone else may only need operational handoffs. if the problem is preparing for the morning rather than catching up at night, try a daily briefing. inspect the first digests and remove channels that only add noise. on a local computer, the scheduled run needs the computer awake and dusk bot open.