Agent Skills
› openai/plugins
› outlook-email-task-extraction
outlook-email-task-extraction
GitHub从Outlook邮件线程或邮箱中提取行动项、截止日期、承诺和责任人，生成结构化任务清单。适用于需要明确任务归属、状态及证据的场景。
Trigger Scenarios
用户要求从邮件中提取待办事项
需要整理邮件中的责任人和截止日期
分析邮件线程中的阻塞点和确认项
Install
npx skills add openai/plugins --skill outlook-email-task-extraction -g -y
SKILL.md
Frontmatter
{
"name": "outlook-email-task-extraction",
"description": "Extract action items, deadlines, commitments, and owners from Outlook email threads and mailbox searches. Use when the user wants a task list from one thread, several related messages, or a mailbox slice, including who owes what and when."
}
Outlook Email Task Extraction
Overview
Use this skill when the user wants work pulled out of email rather than a general summary. Focus on who owns the next move, what the due date is, what is blocked, and what still needs confirmation.
Relevant Actions
- Use
search_messagesorlist_messagesto define the message set in scope. - Use
fetch_messageorfetch_messages_batchwhen body text is needed to resolve owners, due dates, or cross-message dependencies. - Use
list_attachmentsorfetch_attachmentwhen the ask or deadline lives in an attached file rather than the email body. - Use
set_message_categoriesonly if the user explicitly wants tasks or commitments tagged back into Outlook after extraction.
Workflow
- Define the scope clearly: one thread, one sender, one topic, unread mail, or a bounded date window.
- Extract explicit asks, commitments, deadlines, blockers, approvals, and follow-ups from the messages in scope.
- Separate user-owned tasks from tasks owned by other people.
- Distinguish explicit deadlines from inferred urgency.
- When several messages refer to the same task, merge them into one task record with the freshest status.
- If the user wants follow-up help after extraction, keep that as a second step so the task list stays auditable.
Output
- Use a task-oriented format with
Task,Owner,Due,Status, andEvidencewhen possible. - Quote or paraphrase the message that establishes the task owner or due date.
- Call out ambiguity explicitly when ownership or due date is implied rather than stated.
- If there are no concrete tasks, say that clearly instead of forcing a weak extraction.
Version History
- 11c74d6 Current 2026-07-19 09:43
