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.
Best use case
teams-daily-digest is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using teams-daily-digest should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/teams-daily-digest/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How teams-daily-digest Compares
| Feature / Agent | teams-daily-digest | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Teams Daily Digest Use this skill to produce a daily digest of important Teams activity from selected chats, channels, or teams. ## 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 1. Confirm the scope: named chats, named channels, named teams, or named topics. 2. Resolve the exact containers: - channels: `resolve_team`, `resolve_channel` - existing chats: `resolve_chat` 3. Prefer direct container reads over broad search: - channels: `list_channel_messages` - chats: `list_chat_messages` 4. 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. 5. 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. 6. Prioritize decisions, blockers, asks, ownership changes, timeline shifts, and notable replies. 7. Group the digest by channel, chat, or workstream, depending on what makes the summary easiest to scan. ## Formatting Format the digest as: ```md *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* - ... *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. - Add a coverage note when the scope is broad, partly unreadable, or based on recent-thread discovery rather than exhaustive reads.
Related Skills
teams
Summarize Microsoft Teams conversations, triage unread or recent activity, draft follow-ups, and manage Planner tasks through connected Teams data. Use when the user wants to review chats or channels, identify owners and next steps, prepare a safe reply or post, or turn follow-ups into Teams-native tasks.
teams-reply-drafting
Draft Microsoft Teams replies from available context. Use when the user wants help finding messages that likely need a response and preparing reply drafts.
teams-planner-task-management
Review and manage Microsoft Teams Planner tasks. Use when the user wants to inspect plans or buckets, create tasks from follow-ups, update task fields, or safely delete a Planner task.
teams-notification-triage
Triage recent Microsoft Teams activity into a priority queue or task list for the user.
teams-messages
Compose, route, draft, or send Microsoft Teams messages with exact destination resolution, real user mentions, and Teams-native DM or channel routing.
teams-channel-summarization
Summarize activity from one Microsoft Teams channel or one scoped Teams conversation and return a concise recap or post-ready follow-up.
slack-daily-digest
Create a daily Slack digest from selected channels or topics. Use when the user asks for a daily Slack recap or summary of today's Slack activity.
outlook-calendar-daily-brief
Build polished one-day Outlook Calendar briefs. Use when the user asks for today, tomorrow, or a specific date summary with an agenda, conflict flags, free windows, remaining-meeting readouts, or a calendar brief, and Outlook Calendar is available.
google-calendar-daily-brief
Build polished one-day Google Calendar briefs. Use when the user asks for today, tomorrow, or a specific date summary with an agenda, conflict flags, free windows, remaining-meeting readouts, or a calendar brief, and the Google Calendar connector is available.
workflow
Vercel Workflow DevKit (WDK) expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause/resume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.
verification
Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.
vercel-storage
Vercel storage expert guidance — Blob, Edge Config, and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.