plugins/teams/skills/teams-channel-summarization/SKILL.md
Summarize activity from one Microsoft Teams channel or one scoped Teams conversation and return a concise recap or post-ready follow-up.
npx skillsauth add openai/plugins teams-channel-summarizationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
| Workflow | Skill | | --- | --- | | Draft or send the final Teams follow-up | ../teams-messages/SKILL.md |
resolve_team and resolve_channel.list_channel_messages for that window.list_channel_messages(top=50) and top-level messages only.list_channel_messages(... include_replies=True) for a small bounded pass when thread outcomes matterfetch for exact wording or a specific message the user points toFormat 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>
development
Use when the user wants to spin up / create / launch / provision a DigitalOcean droplet (or "a remote dev box on DO") and connect to it from Codex as a remote SSH workspace.
data-ai
Search through Microsoft Teams chats or channels, triage unread or recent activity, draft follow-ups, and manage Planner tasks through connected Teams data.
tools
Motion / animation context for the `use_figma` MCP tool — animating Figma nodes via manual keyframes, animation styles, easing, and timeline duration. Load alongside figma-use whenever a task involves adding, editing, or inspecting animation on a node.
development
SwiftUI ↔ Figma translation. Use whenever the user mentions Swift, SwiftUI, iOS, iPhone, or iPad — in EITHER direction — translating a Figma design into SwiftUI (design → code), or pushing SwiftUI views / screens / tokens back into a Figma file (code → design). Triggers on phrases like 'implement this Figma design in SwiftUI', 'build this screen in Swift', 'push this SwiftUI view to Figma', 'mirror my Swift code in a Figma file', or whenever a Figma URL appears alongside `.swift` files / an `.xcodeproj`. Routes to a direction-specific reference doc; loads alongside `figma-use` for the code → design path.