plugins/teams/skills/teams-notification-triage/SKILL.md
Triage recent Microsoft Teams activity into a priority queue or task list for the user.
npx skillsauth add openai/plugins teams-notification-triageInstall 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 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.
| Workflow | Skill | | --- | --- | | Turn confirmed follow-ups into Microsoft Planner tasks | ../teams-planner-task-management/SKILL.md |
get_profile so you can match message-level mentions to the signed-in user ID when needed.list_chats(unread_only=True) for unread chat signallist_recent_threads for recent channel and chat activitylist_chat_messageslist_channel_messages or list_chat_messagesTeamsMessageResult.mentions. Do not use Teams search results as the source of truth for mention detection.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>
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.