Skill

teams-daily-digest

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.

npx claudepluginhub robinebers/converted-plugins --plugin teams

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/teams:teams-daily-digest

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Use this skill to produce a daily digest of important Teams activity from selected chats, channels, or teams.

SKILL.md

71 lines · ~709 tokens

Similar Skills

cache-components

139.5k

Guides Next.js Cache Components and Partial Prerendering (PPR): 'use cache' directives, cacheLife(), cacheTag(), revalidateTag() for caching, invalidation, static/dynamic optimization. Auto-activates on cacheComponents: true.

cache-components

docx

135.8k

Creates, reads, edits, and analyzes .docx files using docx-js for new documents, pandoc for text extraction, Python scripts for XML unpacking/validation/changes, and LibreOffice for conversions.

20 files

document-skills

Stats

LanguagePython

Parent stars0

MaintenanceGood

Last CommitMay 17, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Teams Daily Digest

Use this skill to produce a daily digest of important Teams activity from selected chats, channels, or teams.

Related Skills

Workflow	Skill
Create or update Microsoft Planner tasks from digest follow-ups	../teams-planner-task-management/SKILL.md

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.