Skill

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.

npx claudepluginhub robinebers/converted-plugins --plugin teams

Invocation

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

Slash command

/teams:teams-channel-summarization

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 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.

SKILL.md

59 lines · ~624 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 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_team and resolve_channel.
If the user gave a time window, call list_channel_messages for 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 fetch for exact wording or a specific message the user points to
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.