Agent Skills
› fanfan-de/anybox
› teams-channel-summarization
teams-channel-summarization
GitHub用于总结指定 Microsoft Teams 频道或对话的活动。支持按时间窗口查询，将消息整合为按主题、决策或阻塞点分类的简洁摘要，并可生成适用于 Teams 发布的后续跟进内容。
Trigger Scenarios
用户请求总结特定 Teams 频道的近期活动
用户要求基于特定时间段（如本周）回顾频道讨论
用户希望将频道讨论结果整理为可发布的摘要
Install
npx skills add fanfan-de/anybox --skill teams-channel-summarization -g -y
SKILL.md
Frontmatter
{
"name": "teams-channel-summarization",
"description": "Summarize activity from one Microsoft Teams channel or one scoped Teams conversation and return a concise recap or post-ready follow-up."
}
Teams Channel Summarization
Use this skill to summarize one Teams channel, using a requested time window when provided or a safe recent read otherwise, and optionally turn the result into a Teams-ready follow-up.
Related Skills
| Workflow | Skill |
|---|---|
| Draft or send the final Teams follow-up | ../teams-messages/SKILL.md |
Start Here
- If the user did not name a team or channel, ask which team and channel to review.
- If the user provided a relative window such as "today" or "this week," anchor it to explicit local dates in the user's timezone.
- If the user did not provide a window, default to a recent bounded read rather than silently claiming full-history coverage.
Workflow
- Resolve the team and channel with
resolve_teamandresolve_channel. - If the user gave a time window, call
list_channel_messagesfor that window. - If the user did not give a window, start with
list_channel_messages(top=50)and top-level messages only. - Expand replies only when they materially affect the summary:
- use
list_channel_messages(... include_replies=True)for a small bounded pass when thread outcomes matter - use
fetchfor exact wording or a specific message the user points to
- use
- Consolidate the activity into a concise summary grouped by topic, decision, blocker, or workstream.
- If the user wants the result delivered in Teams, return a post-ready channel summary and post it when delivery into Teams is the requested action.
Formatting
Format a concise summary as:
*Teams Channel Summary — <team> / <channel>*
*Window:* <explicit date range or recent snapshot>
*Overview:* <1–2 sentence summary of the main themes and biggest updates>
*Topic: <topic 1>*
- ...
- ...
*Topic: <topic 2>*
- ...
- ...
*Notes*
- <gaps, unresolved threads, or coverage caveats>
- Group the summary into 2–4 topics when possible.
- Keep each topic to 1–5 bullets.
- Start each bullet with the main update. Add an owner or next step only when it is clear from the channel.
- If the user asked for a recent snapshot rather than full history, label it explicitly as a snapshot.
- If the channel contains only unreadable placeholders or artifacts, say that directly instead of presenting it as confirmed human activity.
Version History
- 08dc189 Current 2026-07-05 19:07
