Skip to content
MCP Servers
Skill

/channel-digest

Summarize activity across multiple Teams channels into a single consolidated digest — key discussions, decisions, mentions, and action items.

BOOST
From plugin
work-iq
1k19 skills2 MCP
Install
$ npx -y skills add microsoft/work-iq --skill channel-digest --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/channel-digest

Context preview

The summary Claude sees to decide when to auto-load this skill.

Summarize activity across multiple Teams channels into a single consolidated digest — key discussions, decisions, mentions, and action items.

SKILL.md

channel-digest.SKILL.md
name: channel-digest
description: Summarize activity across multiple Teams channels into a single consolidated digest — key discussions, decisions, mentions, and action items.

Channel Digest

Produce a consolidated summary of activity across multiple Microsoft Teams channels. Scans recent messages from each channel, identifies key discussions, decisions made, action items, and @‑mentions — then presents everything in a single, scannable digest. Ideal for managers, leads, or anyone tracking multiple project channels.

When to Use

  • "What happened in my channels today?"
  • "Summarize the last 3 days across all my project channels"
  • "Give me a digest of Engineering and Product channels"
  • "Any decisions made in the team channels this week?"
  • "Channel digest for the sprint channels"
  • "What did I miss in the channels while I was out?"

Instructions

Step 1: Identify the User

workiq-ask (
  question: "What is my profile information including display name, email, and time zone?"
)

Extract **displayName**, **email**, and **timeZone**.

Step 2: Discover Teams and Channels

List all teams and their channels:

workiq-ask (
  question: "List all Microsoft Teams teams I belong to and their channels."
)

If the user specified particular channels (e.g., "Engineering #general and #design-reviews"), filter to only those. Otherwise, include all non‑archived channels across relevant teams.

Build a channel inventory:

  • **Team name** → **Channel name**
  • Skip channels named "General" in low‑priority teams unless the user explicitly includes them.

Step 3: Pull Recent Messages from Each Channel

For each target channel, fetch recent messages within the lookback window:

workiq-ask (
  question: "Show me the last 30 messages in the '<channel name>' channel of the '<team name>' team including replies. For each message include the sender name, date and time, message content, reply count, any @mentions, reactions count, and any attachments or shared links."
)

For each message, capture:

  • **Sender** display name
  • **Timestamp**
  • **Content** (text body for analysis)
  • **Reply count** — indicates discussion depth
  • **Mentions** — anyone @‑mentioned, especially the current user
  • **Reactions** — high reaction count signals importance
  • **Attachments** — files or links shared

Step 4: Analyze and Categorize Messages

For each channel, classify the messages into categories:

**🔑 Key Decisions** — messages containing:

  • Decision language: "decided", "approved", "agreed", "going with", "finalized", "confirmed"
  • Follow‑up with context about what was decided

**💬 Active Discussions** — threads with:

  • 3+ replies indicating substantive conversation
  • Multiple participants contributing
  • Ongoing debate or open questions

**📌 Action Items** — messages containing:

  • Task language: "action item", "TODO", "follow up", "need to", "can you", "please"
  • Assignments: "@person please…", "owned by…"
  • Deadlines: "by Friday", "due date", "EOD"

**📢 Announcements** — messages that are:

  • From team owners or managers
  • Posted with high importance
  • Information‑sharing without expecting discussion

**📎 Shared Resources** — messages with:

  • File attachments (documents, spreadsheets)
  • Links to external resources, PRs, or documents

**👤 Your Mentions** — messages where the current user was @‑mentioned or referenced by name.

Step 5: Search for User Mentions Across Channels

Cast a wider net for the user's mentions:

workiq-ask (
  question: "Find all Teams channel messages that mention me or are directed at me in the last <lookback period>. Include the team name, channel name, sender, date, and message content for each."
)

Cross‑reference with messages already captured to avoid duplicates. Add any new mentions to the **Your Mentions** category.

Step 6: Compile the Consolidated Digest

Organize findings by channel, then surface cross‑channel themes at the top.

Output Format

📰 CHANNEL DIGEST
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📅 Period: {start date} → {end date}
🔍 Channels scanned: {N}  ·  💬 Messages analyzed: {N}

🎯 CROSS‑CHANNEL HIGHLIGHTS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🔑 {N} decisions made  ·  📌 {N} action items  ·  👤 {N} times you were mentioned

Top Decisions:
  1. {Team} › #{Channel}: "{decision summary}" — {Person}, {date}
  2. {Team} › #{Channel}: "{decision summary}" — {Person}, {date}

Action Items Needing You:
  • {Person} in #{Channel}: "{action item}" — due {date}
  • {Person} in #{Channel}: "{action item}"

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📢 {Team Name} › #{Channel Name}
   💬 {N} messages  ·  🧵 {N} threads  ·  👥 {N} participants
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

   🔑 DECISIONS
   • "{Decision summary}" — {Person}, {date}

   💬 KEY DISCUSSIONS
   • "{Topic summary}" — {N} replies, {participants}
     └─ Status: {resolved / ongoing / needs input}

   📌 ACTION ITEMS
   • {Person}: "{task description}" — {due date or "no deadline"}

   📢 ANNOUNCEMENTS
   • {Person}: "{announcement summary}" — {date}

   📎 SHARED FILES
   • {filename} — shared by {Person}, {date}

   👤 YOUR MENTIONS
   • {Person}: "@you {message preview}" — {date}

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
📢 {Team Name} › #{Channel Name}
   💬 {N} messages  ·  ⏸️ Low activity
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   • {brief summary of the few messages}

🔇 QUIET CHANNELS (no messages in period)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
   • {Team} › #{Channel}
   • {Team} › #{Channel}

Parameters

| Parameter | Required | Default | Description | |-----------|----------|---------|-------------| | Lookback | No | 24 hours | Time window to scan (e.g., "3 days", "this week") | | Teams | No | All user's teams | Specific teams to include | | Channels | No | All channels | Specific channels to include | | Focus | No | All categories | Filter to "decisions", "action-items", or "mentions" | | Include

Read more
Ships withwork-iq

The official Microsoft Work IQ plugin collection for GitHub Copilot ✨ Extend the power of GitHub Copilot with Work IQ plugins — MCP servers, skills, and tools that connect AI assistants to your Microsoft 365 data.

Get the whole plugin

Other skills on work-iq.