Teams Daily Digest
Use this skill to produce a daily digest of important Teams activity from selected chats, channels, or teams.
Related Skills
Start Here
- If the user did not name chats, channels, teams, or topics, ask first before making Teams tool calls.
- Do not guess the user's "main channels."
- For requests like "today" or "this morning," anchor the digest to explicit local dates in the user's timezone.
Workflow
- Confirm the scope: named chats, named channels, named teams, or named topics.
- Resolve the exact containers:
- channels:
resolve_team, resolve_channel
- existing chats:
resolve_chat
- Prefer direct container reads over broad search:
- channels:
list_channel_messages
- chats:
list_chat_messages
- If the user named a team but not a channel, use
list_recent_threads scoped to that team to discover recent channel threads, then expand only the highest-signal channels with direct reads.
- If the user named topics but not exact containers, use
list_recent_threads as a shortlist and expand only chats or channels whose recent activity plausibly matches the topic.
- Prioritize decisions, blockers, asks, ownership changes, timeline shifts, and notable replies.
- Group the digest by channel, chat, or workstream, depending on what makes the summary easiest to scan.
- If the digest identifies follow-ups and the user wants them tracked, route to the Planner skill. Do not create Planner tasks as a side effect of a digest request.
Formatting
Format the digest as:
*Teams Daily Digest — YYYY-MM-DD*
*Scope:* <containers + time window + coverage note>
*Summary:* <1–2 line overview of volume and key signals>
*Details*
*<group 1>*
- ...
- ...
*<group 2>*
- ...
- ...
*Needs attention*
- ...
*Planner candidates*
- <optional follow-ups that could become tasks, only when task tracking is relevant>
*Notes*
- <gaps, sparse results, or caveats>
- Keep the digest compact; aim for 4–10 bullets total across all sections.
- Preserve exact team, channel, and chat names.
- Include Needs attention only for items requiring user action, decisions, or input.
- Include Planner candidates only when the user asked for tasks or the Teams activity contains concrete follow-ups worth turning into tasks.
- Add a coverage note when the scope is broad, partly unreadable, or based on recent-thread discovery rather than exhaustive reads.
1---2name: teams-daily-digest3description: Create a daily Microsoft Teams digest from selected chats, channels, or workstreams. Use when the user asks for a daily Teams recap or summary of today's Teams activity.4---56# Teams Daily Digest78Use this skill to produce a daily digest of important Teams activity from selected chats, channels, or teams.910## Related Skills1112| Workflow | Skill |13| --- | --- |14| Create or update Microsoft Planner tasks from digest follow-ups | [../teams-planner-task-management/SKILL.md](../teams-planner-task-management/SKILL.md) |1516## Start Here1718- If the user did not name chats, channels, teams, or topics, ask first before making Teams tool calls.19- Do not guess the user's "main channels."20- For requests like "today" or "this morning," anchor the digest to explicit local dates in the user's timezone.2122## Workflow23241. Confirm the scope: named chats, named channels, named teams, or named topics.252. Resolve the exact containers:26 - channels: `resolve_team`, `resolve_channel`27 - existing chats: `resolve_chat`283. Prefer direct container reads over broad search:29 - channels: `list_channel_messages`30 - chats: `list_chat_messages`314. If the user named a team but not a channel, use `list_recent_threads` scoped to that team to discover recent channel threads, then expand only the highest-signal channels with direct reads.325. If the user named topics but not exact containers, use `list_recent_threads` as a shortlist and expand only chats or channels whose recent activity plausibly matches the topic.336. Prioritize decisions, blockers, asks, ownership changes, timeline shifts, and notable replies.347. Group the digest by channel, chat, or workstream, depending on what makes the summary easiest to scan.358. If the digest identifies follow-ups and the user wants them tracked, route to the Planner skill. Do not create Planner tasks as a side effect of a digest request.3637## Formatting3839Format the digest as:4041```md42*Teams Daily Digest — YYYY-MM-DD*4344*Scope:* <containers + time window + coverage note>45*Summary:* <1–2 line overview of volume and key signals>4647*Details*48*<group 1>*49- ...50- ...5152*<group 2>*53- ...54- ...5556*Needs attention*57- ...5859*Planner candidates*60- <optional follow-ups that could become tasks, only when task tracking is relevant>6162*Notes*63- <gaps, sparse results, or caveats>64```6566- Keep the digest compact; aim for 4–10 bullets total across all sections.67- Preserve exact team, channel, and chat names.68- Include *Needs attention* only for items requiring user action, decisions, or input.69- Include *Planner candidates* only when the user asked for tasks or the Teams activity contains concrete follow-ups worth turning into tasks.70- Add a coverage note when the scope is broad, partly unreadable, or based on recent-thread discovery rather than exhaustive reads.
ConcertoNotes