Agent Skills
› fanfan-de/anybox
› teams-daily-digest
teams-daily-digest
GitHub根据指定聊天、频道或团队生成每日 Microsoft Teams 活动摘要。支持按范围解析容器，优先直接读取消息，筛选关键决策与阻塞项，并按组展示细节、需关注事项及 Planner 任务候选项。
Trigger Scenarios
用户请求每日 Teams 回顾
用户要求总结今日 Teams 活动
Install
npx skills add fanfan-de/anybox --skill teams-daily-digest -g -y
SKILL.md
Frontmatter
{
"name": "teams-daily-digest",
"description": "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 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
- channels:
- Prefer direct container reads over broad search:
- channels:
list_channel_messages - chats:
list_chat_messages
- channels:
- If the user named a team but not a channel, use
list_recent_threadsscoped 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_threadsas 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.
Version History
- 08dc189 Current 2026-07-05 19:07
