Skill

teams-notification-triage

Triage recent Microsoft Teams activity into a priority queue or task list for the user.

npx claudepluginhub robinebers/converted-plugins --plugin teams

Invocation

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

Slash command

/teams:teams-notification-triage

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

SKILL.md

65 lines · ~705 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 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.

Related Skills

Workflow	Skill
Turn confirmed follow-ups into Microsoft Planner tasks	../teams-planner-task-management/SKILL.md

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

Resolve the current user with get_profile so you can match message-level mentions to the signed-in user ID when needed.
If the user provided channels, chats, teams, or people, keep the triage inside that scope.
With no explicit scope, prioritize:
- list_chats(unread_only=True) for unread chat signal
- list_recent_threads for recent channel and chat activity
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
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.
Prioritize messages likely needing a reply, creating a follow-up, or changing the user's plan.
If some channel activity is unreadable or artifact-only, say so and keep it out of the main triage buckets.
If the user asks you to track tasks from triage, show the proposed task list first or route to the Planner skill; do not silently create tasks while presenting an attention queue.

Formatting

Format the triage as:

*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.
Make Tasks for you a triage bucket, not proof that a Planner task exists. Say "Planner task" only after reading or writing Planner.
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.