Agent Skills
› openai/plugins
› outlook-email-inbox-triage
outlook-email-inbox-triage
GitHub将 Outlook 收件箱分类为紧急、需回复、等待和仅供参考等可操作类别。基于核心技能，通过列表或搜索获取邮件，利用启发式规则判断优先级，明确区分分类与执行操作，提供包含理由和行动建议的结构化输出。
Trigger Scenarios
用户要求对 Outlook 收件箱进行分类或整理
询问哪些邮件需要立即关注或回复
要求区分重要邮件与垃圾/噪音邮件
Install
npx skills add openai/plugins --skill outlook-email-inbox-triage -g -y
SKILL.md
Frontmatter
{
"name": "outlook-email-inbox-triage",
"description": "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."
}
Outlook Email Inbox Triage
Overview
Use this skill for direct Outlook inbox-triage requests. Build on the core Outlook Email skill at ../outlook-email/SKILL.md, especially its read-first and write-safety guidance.
Relevant Actions
- Use
list_messagesfor recent or unread inbox passes where a bounded mailbox slice is enough. - Use
search_messageswhen the triage request includes lexical search terms, sender filters, attachment constraints, or date scoping. - Use
fetch_messageorfetch_messages_batchonly when snippets are not enough to classify urgency or reply-needed state. - Use
mark_email_read_state,move_email, orset_message_categoriesonly if the user explicitly asks you to act on the triage results.
Workflow
- Default to the inbox and a clear timeframe unless the user asks for a broader audit.
- Build a shortlist with
list_messagesorsearch_messagesbefore reading full bodies. - Exclude obvious noise early if newsletters, calendar churn, or automated alerts dominate the first pass.
- Expand only the messages whose urgency, ownership, or reply-needed status is unclear from the first pass.
- Return explicit buckets such as
Urgent,Needs reply soon,Waiting, andFYI. - If the user asks to clean up the mailbox after triage, keep the classification and the mailbox actions clearly separated.
Bucket Heuristics
Urgent: direct asks with time pressure, blockers, escalation risk, or operational consequences if ignored.Needs reply soon: direct asks without same-day urgency, active threads where the user is likely the next responder, or follow-ups that will go stale soon.Waiting: threads where the user already replied or where the current blocker belongs to someone else.FYI: announcements, newsletters, calendar noise, transactional mail, and items that do not currently require action.
Output
- Include sender, subject, why each item is in its bucket, and the likely next action.
- State timeframe, search scope, and confidence.
- Treat reply-needed as an inference, not a guaranteed state.
- Avoid claiming the inbox is fully triaged if you only checked a narrow slice.
Version History
- 11c74d6 Current 2026-07-19 09:43
