| name | slack-daily-digest |
| description | Build a cross-channel daily digest of what matters across the user's Slack. Use for 'give me my Slack digest', 'what happened across my channels today', or a standing daily/standup recap. |
| emoji | 🗞️ |
Slack daily digest
A single roll-up across the channels the user cares about — the "what happened
while I was away" brief. Faithful only; never invent activity.
Steps
- Scope the channels. Use the ones the user names; otherwise the channels
they're a member of / most active in (list channels, prefer non-archived).
If there are many, focus on the highest-signal ones and say which you covered
(never silently truncate).
- Resolve the window. Default: since yesterday's digest / last 24h. Honor an
explicit range.
- Scan each channel over the window (read bucket; back off on 429). Skip
quiet channels. Open only threads with real substance.
- Rank by importance: direct mentions and DMs to the user > decisions /
blockers / incidents > launches / announcements > general chatter.
- Capture action items with
todo_add (source: "slack", sourceRef = ts),
direction mine/theirs.
Output format
- Slack Digest — <date/range>
- Needs you — mentions/DMs/asks directed at the user (owner + link/where).
- Per channel —
#channel: 1–3 bullets of the notable items; omit quiet ones.
- Coverage — which channels were scanned (and any skipped for volume).
Delivery
Answer in chat by default. Post to Slack or write a canvas only on an explicit
"post"/"send" (an immediate write — apply the slack skill's write-safety rules).
For a recurring digest, offer to enable the daemon loop
(nomos cron enable slack-digest) and run it yourself when asked.
