[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E82NTECHZBJS3RQC8X0WFW":3,"skill-same:01M7E82NTECHZBJS3RQC8X0WFW":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7E82NTECHZBJS3RQC8X0WFW","teams-notification-triage",null,"Triage recent Microsoft Teams activity into a priority queue or task list for the user.","wxdwu\u002Fnew-api","wxdwu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F80968397?v=4","01M7E6AEMB59N90BKXD77EC83D","Xudong Wu","01M7E6AEMY2BXCDVZ9MJJHFQ4C",0,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fteams\u002Fskills\u002Fteams-notification-triage\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: teams-notification-triage\ndescription: Triage recent Microsoft Teams activity into a priority queue or task list for the user.\n---\n\n# Teams Notification Triage\n\nUse 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.\n\n## Related Skills\n\n| Workflow | Skill |\n| --- | --- |\n| Turn confirmed follow-ups into Microsoft Planner tasks | [..\u002Fteams-planner-task-management\u002FSKILL.md](..\u002Fteams-planner-task-management\u002FSKILL.md) |\n\n## Start Here\n\n- If the user provided a time window, use it and anchor it to explicit local dates.\n- Treat this as best-effort triage over unread chats, recent threads, and recent message-level mentions.\n- Do not claim access to unread channel markers or a native Teams notification feed.\n\n## Workflow\n\n1. Resolve the current user with `get_profile` so you can match message-level mentions to the signed-in user ID when needed.\n2. If the user provided channels, chats, teams, or people, keep the triage inside that scope.\n3. With no explicit scope, prioritize:\n   - `list_chats(unread_only=True)` for unread chat signal\n   - `list_recent_threads` for recent channel and chat activity\n4. Expand only the containers needed to determine what matters:\n   - unread chats first via `list_chat_messages`\n   - then recent channels or chats via `list_channel_messages` or `list_chat_messages`\n5. 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.\n6. Prioritize messages likely needing a reply, creating a follow-up, or changing the user's plan.\n7. If some channel activity is unreadable or artifact-only, say so and keep it out of the main triage buckets.\n8. 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.\n\n## Formatting\n\nFormat the triage as:\n\n```md\n*Teams Attention Triage — YYYY-MM-DD*\n\n*Summary:* \u003C1–2 line overview of what most likely needs attention>\n\n*Tasks for you*\n- ...\n\n*Worth skimming*\n- ...\n\n*Can ignore for now*\n- ...\n\n*Notes*\n- \u003Ccoverage limits, proxy caveats, or unread-channel limitation>\n```\n\n- Keep the triage compact; aim for 3–15 bullets total.\n- Treat *Tasks for you* as the primary section whenever the goal is a personal action list.\n- Make *Tasks for you* a triage bucket, not proof that a Planner task exists. Say \"Planner task\" only after reading or writing Planner.\n- Include *Can ignore for now* only when the user explicitly asked to filter noise.\n- Preserve exact chat, team, and channel names.\n- Use *Notes* to explain proxy behavior, coverage gaps, or the lack of channel unread markers.\n","# Teams Notification Triage\n\nUse 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.\n\n## Related Skills\n\n| Workflow | Skill |\n| --- | --- |\n| Turn confirmed follow-ups into Microsoft Planner tasks | [..\u002Fteams-planner-task-management\u002FSKILL.md](..\u002Fteams-planner-task-management\u002FSKILL.md) |\n\n## Start Here\n\n- If the user provided a time window, use it and anchor it to explicit local dates.\n- Treat this as best-effort triage over unread chats, recent threads, and recent message-level mentions.\n- Do not claim access to unread channel markers or a native Teams notification feed.\n\n## Workflow\n\n1. Resolve the current user with `get_profile` so you can match message-level mentions to the signed-in user ID when needed.\n2. If the user provided channels, chats, teams, or people, keep the triage inside that scope.\n3. With no explicit scope, prioritize:\n   - `list_chats(unread_only=True)` for unread chat signal\n   - `list_recent_threads` for recent channel and chat activity\n4. Expand only the containers needed to determine what matters:\n   - unread chats first via `list_chat_messages`\n   - then recent channels or chats via `list_channel_messages` or `list_chat_messages`\n5. 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.\n6. Prioritize messages likely needing a reply, creating a follow-up, or changing the user's plan.\n7. If some channel activity is unreadable or artifact-only, say so and keep it out of the main triage buckets.\n8. 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.\n\n## Formatting\n\nFormat the triage as:\n\n```md\n*Teams Attention Triage — YYYY-MM-DD*\n\n*Summary:* \u003C1–2 line overview of what most likely needs attention>\n\n*Tasks for you*\n- ...\n\n*Worth skimming*\n- ...\n\n*Can ignore for now*\n- ...\n\n*Notes*\n- \u003Ccoverage limits, proxy caveats, or unread-channel limitation>\n```\n\n- Keep the triage compact; aim for 3–15 bullets total.\n- Treat *Tasks for you* as the primary section whenever the goal is a personal action list.\n- Make *Tasks for you* a triage bucket, not proof that a Planner task exists. Say \"Planner task\" only after reading or writing Planner.\n- Include *Can ignore for now* only when the user explicitly asked to filter noise.\n- Preserve exact chat, team, and channel names.\n- Use *Notes* to explain proxy behavior, coverage gaps, or the lack of channel unread markers.\n",{"name":5,"description":7},"main","dde9a06ab10bce3fe52058c783826590231f7df3","plugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fteams\u002Fskills\u002Fteams-notification-triage","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api","https:\u002F\u002Fgithub.com\u002Fwxdwu","24120128@bjtu.edu.cn","I am Xudong Wu，a student in beijing jiaotong University, \"I am eager to learn on GitHub and contribute my part to this community.","2026-10-05 17:26:50",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add wxdwu\u002Fnew-api --skill teams-notification-triage",{"tool":38,"command":39},"bunx","bunx skills add wxdwu\u002Fnew-api --skill teams-notification-triage",{"tool":41,"command":42},"pnpm","pnpm dlx skills add wxdwu\u002Fnew-api --skill teams-notification-triage","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fteams\u002Fskills\u002Fteams-notification-triage\u002FSKILL.md",true,[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",412,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fteams\u002Fskills\u002Fteams-notification-triage\u002Fagents\u002Fopenai.yaml",[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7E8SVA2N0JA09RW1XJYXCWX","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzotero\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7E8ST1FJAD5PWTW2FN1NSK0","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7E8SRW074NNNCZRCZA5T3Z1","setup-zoom-websockets","Use when building Zoom WebSockets.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7E8SPCFMD3YVPRX2MW8X3RA","setup-zoom-webhooks","Use when building Zoom webhooks.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fwebhooks\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7E8SMCH4RPCX8YSBNGWQCMP","zoom-virtual-agent-web","Zoom Virtual Agent SDK for web embeds. Use for campaign or entry ID chat launch, event-driven controls, user context updates, and CSP-safe deployment.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fvirtual-agent\u002Fweb\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7E8SJCAY323E36Z8SAP8H4M","zoom-virtual-agent-ios","Zoom Virtual Agent iOS integration via WKWebView. Use for Swift\u002FObjective-C script injection, message handlers, support_handoff relay, and URL routing policies.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fvirtual-agent\u002Fios\u002FSKILL.md",[],[]]