slack-debrief

Summarize unread Slack mentions, direct messages, and thread updates into a daily debrief.

Updated Jul 6, 2020
One-click install
npx skills add https://github.com/guifry/devconfig --skill slack-debrief
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slack-debrief
Source: https://github.com/guifry/devconfig/tree/main/claude/skills/slack-debrief
Command: npx skills add https://github.com/guifry/devconfig --skill slack-debrief

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unread Slack activity from mentions, DMs, and threads can overwhelm your day; this Skill provides a concise debrief to surface priorities.

Core Features & Use Cases

  • Summarizes unread Slack mentions, direct messages, and channel/thread activity into a compact daily briefing.
  • Use Case: Standup prep, daily catchups, and response prioritization for teams with high Slack activity.
  • Output: Actionable summary with highlights and suggested follow-ups.

Quick Start

Summarize unread Slack mentions, direct messages, and thread activity from the last 24 hours.

Frequently Asked Questions about slack-debrief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I summarize unread Slack mentions and threads for a daily debrief?

To get a daily debrief of unread Slack activity, this Skill processes mentions, direct messages, and thread updates from the last 24 hours into a concise, action-oriented summary. It requires configuring the Slack MCP with your SLACK_BOT_TOKEN and SLACK_TEAM_ID.

What is the best way to prepare a standup from unread Slack messages?

The best way to prepare a standup from unread Slack messages is to generate a structured daily catchup summary. This Skill surfaces priorities and highlights from recent mentions and channel activity, providing suggested follow-ups for quick review.

Do I need a Slack bot token to summarize direct messages and mentions?

Yes, you need a Slack bot token to summarize direct messages and mentions. The Skill requires the Slack MCP configured with valid SLACK_BOT_TOKEN and SLACK_TEAM_ID environment variables to access your workspace and retrieve unread activity.

Can I use this to summarize Slack activity across multiple workspaces?

Summarizing Slack activity requires a configured SLACK_TEAM_ID, meaning it processes one workspace at a time. To summarize multiple workspaces, you would need to configure the Slack MCP separately for each team's bot token and run the debrief individually.

What time range does the Slack daily debrief cover for unread threads?

The Slack daily debrief covers unread thread activity from the last 24 hours. It applies to Slack workspaces with recent unread activity, capturing mentions, direct messages, and channel updates to produce a structured summary.

Does this summarizer work with Slack standup check-ins and team threads?

Yes, this summarizer works with Slack standup check-ins and team threads. It captures unread channel and thread updates, summarizing them into an actionable briefing suitable for daily catchups and response prioritization in high-activity teams.