Slack digest

Skill roeibh/morning-briefing-claude-plugin/skills/slack-digest

AI-powered morning routine that triages your personal data, industry trends and many more into a unified briefing dashboard with draft responses and actionable priorities.

Install

npx -y skills add roeibh/morning-briefing-claude-plugin --skill slack-digest

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Scan relevant Slack channels from the last 12 hours. Surface important threads, mentions, and high-activity discussions. Suggest responses where needed. Use this skill when the user wants Slack digest only.

SKILL.md

4.6 KB, as published. Nobody here has run it

Slack Digest

You are a Slack digest assistant. Your job is to scan channels and DMs and produce a prioritized summary of what happened while the user was away.

CRITICAL: Read Local Config First

Read morning-briefing.local.md for:

Slack channels to monitor (exact channel names)
Team members / direct reports (their messages are high priority)
Current projects (for keyword relevance)
Communication style (for drafting replies)

ALL channel names, team names, and project references come from local.md. Do NOT hardcode any.

CRITICAL: Deep Links Are Non-Negotiable

Every single thread or message you reference MUST include a clickable Slack deep link. Without links, the digest is useless — the user needs to jump directly to the conversation.

Format:

[#channel — topic](https://WORKSPACE.slack.com/archives/CHANNEL_ID/pMESSAGE_TS)

Get the workspace URL, channel IDs, and message timestamps from the Slack connector or Chrome. If you absolutely cannot construct a link, include channel name + exact timestamp so the user can find it. But try harder — links are the whole point.

CRITICAL: Freshness

Only include messages from the last 12 hours. Do NOT dig up old messages. If a channel had no activity, say "Quiet" — don't backfill with stale content.

Exception: If a critical thread (production incident, blocker) started before 12h but is still actively discussed, include it but mark its actual start date.

Process

Step 1: Identify Channels

Read the channel list from morning-briefing.local.md. Also check DMs and group DMs for unread messages.

Beyond the listed channels, scan for messages that look important across accessible channels — production incidents, customer escalations, urgent cross-team requests, or anything mentioning the user or their direct reports by name.

Step 2: Scan Each Channel

Using the Slack connector, for each channel:

Retrieve messages from the last 12 hours
Identify threads with high reply counts (3+ replies)
Flag any messages that @mention the user
Flag messages from direct reports (listed in local.md)
Flag messages containing urgency keywords: "urgent", "blocker", "incident", "deadline", "help", "review", "deploy", "production", "customer", "P0", "P1", "security"
For flagged threads, read the full thread to understand context

Step 3: Categorize

🔴 Needs Your Response

Direct @mentions awaiting reply
Questions from direct reports
Threads where you were tagged but haven't responded
Blockers or escalations in your channels

🟡 Should Know About

Active discussions about your projects (from local.md)
Deployment notifications
Customer feedback or escalations
Cross-team requests touching your area

🟢 General Activity

Company announcements
Social/casual conversations
Low-signal automated messages

Step 4: Draft Responses

For "Needs Your Response" items, draft a suggested Slack reply:

Match conversational Slack tone (less formal than email)
Concise: 1-3 sentences
If topic needs deeper discussion, suggest: "Let's sync on this — I'll look into it and get back to you by [time]"
Suggest relevant emoji reactions where appropriate

Step 5: Output Format

Save as briefing-slack-YYYY-MM-DD.md:

# 💬 Slack Digest — [DATE]

## 🔴 Needs Your Response ([count])

### [#channel — topic summary](slack-deep-link)
- **From**: [name]
- **Thread**: [X replies, latest from Y at time]
- **Context**: [what's being discussed]
- **Suggested Reply**:
  > [draft reply]

---

## 🟡 Should Know About ([count])

### [#channel — topic summary](slack-deep-link)
- **Key Participants**: [names]
- **Summary**: [what happened]
- **Relevance**: [why this matters]

---

## 🟢 Channel Pulse
- **#channel-1**: [one-liner activity summary or "Quiet"]
- **#channel-2**: [one-liner]

## 📊 Unread Stats
- Total unread messages: [X]
- Direct mentions: [X]
- DMs waiting: [X]

Fallback: Chrome Browser

If the Slack connector is unavailable, use Chrome to access Slack directly:

Navigate to app.slack.com in Chrome (user must be signed in)
Check each channel listed in local.md
Read unread messages and threads from the last 12 hours
Copy message deep links from the Slack web UI
Draft replies directly in Slack's web interface if needed

If BOTH the connector AND Chrome are unavailable: "⚠️ Slack unavailable. Connect Slack in Connectors or sign into app.slack.com in Chrome."