Prompt Library

Post a daily RSS digest to your Slack channel

Every morning, Sai reads the RSS feeds your team follows, drops the reposts and the noise, writes a short digest of what actually matters, and posts it to your Slack channel — one message, not forty.

The PROMPTS
Copy prompt
Every weekday at [8am], read these RSS feeds and post a digest to the Slack channel [#channel]. Feeds: [feed URL 1], [feed URL 2], [feed URL 3]. We care about [topic 1], [topic 2], and anything naming these companies: [competitor 1], [competitor 2], [competitor 3]. Cover items published in the last [24] hours. Structure the message as: one headline item with two lines on why it matters; up to [5] more items worth reading, one line each, grouped by theme rather than by source; a separate section for anything naming a company on our watch list; and a count of what you skimmed and dropped. When several feeds carry the same story, post it once and name the outlet you linked, not all of them. Drop press-release reprints, sponsored posts, and roundups of other people's articles. Summarise from what the item actually says. If a headline promises something the article does not deliver, say so in the one-liner rather than repeating the headline. Keep the channel message under [200] words and put the full item list in a thread reply. If nothing worth reading came through, post one line saying the feeds were quiet — do not pad the digest. Never invent a figure, a date, or a quote that is not in the source.
Run this TaskView Demo

Platforms this prompt works across

Piping RSS straight into Slack has been possible for a decade, and it is still a bad experience — because a feed is a firehose and a channel is a room full of people. Forty raw links a day do not make a team informed; they make a channel that everyone mutes in week two, at which point the one story that mattered arrives with the same weight as a press-release reprint. The problem was never delivery. It is that nothing in between was reading.

What this recurring task does

Sai reads the feeds your team follows, works out which items actually matter to you, and posts one short message to your channel each morning. It collapses the same story reported by four outlets into a single line, drops reprints and sponsored placements, groups what is left by theme, and puts the long tail in a thread reply so the channel stays readable. Nothing is forwarded verbatim.

How the digest is structured

One message, six parts, ordered so that reading only the first line still leaves you informed.

★ HOW THE SLACK POST IS BUILT

SectionWhat goes in itWhy it is separated out
Headline itemThe single most consequential story, with two lines on whyMost people read one item — this decides which one it is
Worth readingUp to [5] items, one line each, grouped by theme not by sourceGrouping by theme shows when three outlets ran the same story
Competitor movesAnything naming a company on your watch listPulled out because it needs a different reader than industry news
SkimmedA count of everything else read and droppedProves the feeds were covered without reprinting them
Nothing todayOne line saying the feeds were quietA digest that pads on slow days stops being read within a month
ThreadFull item list posted as a reply, not in the channel messageKeeps the channel scannable while the detail stays one click away

What it does that a feed integration cannot

A standard RSS integration forwards; it does not read. That means it cannot tell a launch from a listicle, cannot recognise that three of today's items are the same announcement, and cannot flag that a headline oversells what the article says. It also cannot tell a quiet day from a broken feed. Summarising from the body rather than the headline is the whole difference, and it is why the digest is short: most items do not survive being read.

What happens on the second run

Items already covered in an earlier digest are not posted again, including the same story resurfacing from a different outlet, so a story that runs for a week appears once with follow-ups noted rather than five times. A feed that returns nothing for [several days] is reported as possibly broken instead of silently producing a shorter digest. Quiet days get one line, which is what keeps the channel worth reading on loud ones.

Where this fits with your other routines

This is the team-facing half of staying current. The personal half — what is worth saying out loud rather than just knowing — is your daily LinkedIn feed digest, and a competitor move spotted here often belongs in the weekly prospect list before the week is out. Formatting and threading follow Slack's own message guidelines, which is why the digest posts as one message with the detail in a reply rather than as a wall of links.

Stop doing repetitive tasks. Let Sai handle them for you.

Sai is your AI computer use agent — it operates your apps, automates your workflows, and gets work done while you focus on what matters.

Try Sai