Slack Notification Triage

Use this skill to produce a priority queue or task list for the user from recent Slack messages. It is for surfacing what the user likely needs to read, reply to, or do next.

Start Here

• If the user provided a time window, use it. For requests like "today" or "this morning," resolve the user's timezone with slack_read_user_profile.
• Treat this as best-effort triage over recent Slack activity, not an exact unread or notification-state view.

Workflow

1. Treat this as personal triage for the user. Focus on messages directed at the user, messages likely needing a reply, and messages that create a concrete follow-up or task for the user.
2. Resolve the current user with slack_read_user_profile so you have the user's Slack ID for mention-based searches.
3. If the user provided channel names, DMs, people, or topic keywords, use that scope.
4. Named channels: Resolve IDs through slack_search_channels, then call slack_read_channel with limit at 100 per channel.
5. Named people or DMs: Resolve people through slack_search_users, then use slack_search_public_and_private with several small searches using filters from:<@USER_ID>, to:<@USER_ID>, or in:<@USER_ID> to surface relevant DM or person-specific activity.
6. Named topics: Use slack_search_public_and_private, and if channels were also provided, keep the search inside those channels.
7. No explicit scope: Search in this order:
   • unanswered direct conversations: run slack_search_public_and_private over channel_types="im", paging until you have a reasonable set of unique conversations, then dedupe and expand promising DMs with slack_read_channel