teams-notification-triage
Triage recent Microsoft Teams activity into a priority queue or task list for the user.
Best use case
teams-notification-triage is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Triage recent Microsoft Teams activity into a priority queue or task list for the user.
Teams using teams-notification-triage 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-notification-triage/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How teams-notification-triage Compares
| Feature / Agent | teams-notification-triage | 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?
Triage recent Microsoft Teams activity into a priority queue or task list for the user.
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 Notification Triage Use this skill to produce a priority queue or task list from recent Teams activity. This is a proxy workflow over the available Teams signals, not a native notification-feed view. ## Start Here - If the user provided a time window, use it and anchor it to explicit local dates. - Treat this as best-effort triage over unread chats, recent threads, and recent message-level mentions. - Do not claim access to unread channel markers or a native Teams notification feed. ## Workflow 1. Resolve the current user with `get_profile` so you can match message-level mentions to the signed-in user ID when needed. 2. If the user provided channels, chats, teams, or people, keep the triage inside that scope. 3. With no explicit scope, prioritize: - `list_chats(unread_only=True)` for unread chat signal - `list_recent_threads` for recent channel and chat activity 4. Expand only the containers needed to determine what matters: - unread chats first via `list_chat_messages` - then recent channels or chats via `list_channel_messages` or `list_chat_messages` 5. For mention checks, inspect message-history results and use `TeamsMessageResult.mentions`. Do not use Teams search results as the source of truth for mention detection. 6. Prioritize messages likely needing a reply, creating a follow-up, or changing the user's plan. 7. If some channel activity is unreadable or artifact-only, say so and keep it out of the main triage buckets. ## Formatting Format the triage as: ```md *Teams Attention Triage — YYYY-MM-DD* *Summary:* <1–2 line overview of what most likely needs attention> *Tasks for you* - ... *Worth skimming* - ... *Can ignore for now* - ... *Notes* - <coverage limits, proxy caveats, or unread-channel limitation> ``` - Keep the triage compact; aim for 3–15 bullets total. - Treat *Tasks for you* as the primary section whenever the goal is a personal action list. - Include *Can ignore for now* only when the user explicitly asked to filter noise. - Preserve exact chat, team, and channel names. - Use *Notes* to explain proxy behavior, coverage gaps, or the lack of channel unread markers.
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-messages
Compose, route, draft, or send Microsoft Teams messages with exact destination resolution, real user mentions, and Teams-native DM or channel routing.
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.
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-notification-triage
Triage recent Slack activity into a priority queue or task list for the user.
outlook-email-inbox-triage
Triage an Outlook inbox into actionable buckets such as urgent, needs reply soon, waiting, and FYI using connected Outlook data. Use when the user asks to triage the inbox, rank what needs attention, find what still needs a reply, or separate important mail from noise.
gmail-inbox-triage
Triage a Gmail inbox into actionable buckets such as urgent, needs reply soon, waiting, and FYI using connected Gmail data. Use when the user asks to triage the inbox, rank what needs attention, find what still needs a reply, or separate important mail from noise.
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.